Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Email added as a note is truncated under Notes in default SSM Incidents project.
Notes added via email will get truncated when viewed in the note section.
CMS-XML Attachments via email submit do not get created
When the attachments directory is on a network share, and proper credentials are supplied on the Attachments tab of the Admin's Options | Settings, users are able to upload attachments OK from the user interface, but the email submit will not be able to. The log file will show access denied errors as it seems the Mail Client service uses Local System and not the credentials provided in the attachment settings.
CMS-XML Emails created using the "Preferred E-Mail Client" do not use the default template
Emails created using the "Preferred E- Mail Client" do not use the default template
CMS-XML When adding description to e-mail template, no line breaks will be created
If you add a text field such as description to an e-mail template, when the end user gets this message, the text field may appear to run on to the left. This is because we are not honoring the line breaks appropriately.
CMS-XML Creating users through the import (spreadsheet) sends out email
Creating users through the import (spreadsheet) sends out email
CMS-XML App Admin should allow to create/validate users with single quote in e-mail address
App Admin should allow to create /validate users with single quote in e- mail address
CMS-XML Mail client does not send failure email
If an email submission fails to create an item, possibly because the email address it is coming from is not associated to an SBM user, the failure email using the error template does not get sent out and an error appears in the ns.log. The error will look like the following:
CMS-XML Large emails may be rejected by Mail Client without proper explanation
As long as that value was not exceeded all was well. It was also possible to use an appscript on the email submit transition to notify the submitter if the email body was larger than expected or desired. It was possible, however, for the field mapping to cause issues when creating the item and DEF259225 was raised to cater for this.
CMS-XML Event manager log file growing constantly - JMS mail listener issues
2014-02-17 11:36:26,601 ERROR [mailto-Worker-16] [org.apache.axis2.transport.mail.MailTransportListenerEx] [::] -- Error connecting to mail server for address : SBMEventUser@localhost :: Connect failed This has been logged as a defect and a fix will be produced .
CMS-XML Entry incorrectly created in TS_STRINGIDENTIFIERS every time deploy global app containing custom form. This can also lead to errors in notification server
That alone is not a problem (other than duplicates) but if you try to use $STRING() tag in notification template and choose, for example, $STRING(Prefix.View Form.FirstName_Label) - where "Prefix.View Form.FirstName_Label" is label for the First Name field - you get error in notification server log and mail is not sent.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs