Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
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 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 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 New fields are missing from notification emails
After a deploy of a process app, values for newly created fields do not appear or appear may appear as asterisks (*) in notification emails .
CMS-XML Unable To Unselect "To" Name In Email
When creating the "To" list for an e-mail : If you have multiple names in your "To:" list and you decide to 'unselect' a name, it will not allow you to unselect a name, unless that name is in the list that is displayed.
CMS-XML Randomly missing field content in notification emails, which may lead to confusion
The current design of the Notification Server is such that different threads handle different parts of the process - reading the Change Actions and creating Notification Events; handling the Notification Events and generating emails ; sending those emails . In some circumstances, but especially when Submit, modification and triggering of notifications all happen close together in time, it is possible that a later step in the process reads (and caches) the value of a field that has already been superceded, but using an entry cached by a previous thread.
CMS-XML Notification email templates do not get applied if not within first 200
There is an unintended limit of 200 notification email templates so all templates that were created after the first 200 will not get applied to notification emails even if they are selected to be used, resulting in notification emails that use the default template rather than the intended template.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs