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 File system filling up quickly on NS server when there are many attachments on Mail-Client or Mail Recorder emails
The JBoss server \default\tmp\ns-attachments directory can fill up rapidly if your users send many or large attachments on email replies or when submitting items via email . ... This temporary directory holds copies of the attachments while they are being processed and it is possible that they are not deleted correctly .
CMS-XML Email submit fails with error "Failed to receive greetings from IMAP server"
12/07/2011 10:54:15: Begin Mailbox Processing, Number of Mailboxes: 1, Server Type: IMAP, Server Name: imap.gmail.com, Port : 993
CMS-XML More Actions button shows duplicate entries for "Printable View", "Click to Send Email" and "Copy URL to Clipboard"
Replace the wizard.js file attached below with the one in the following directory on the SBM server .
CMS-XML Can't submit item via email when using gmail server
INFO 15-10-2015 02:40:03 [MailClient] -- System field [Owner] is empty when Email submit transition. INFO 15-10-2015 02:40:22 [MailClient] -- Item "Plain text email submit" was successfully email submitted at project "Notifications Project" Issue appears only when we use Gmail server and send html email .
CMS-XML HTML tags not rendered correctly when emailing a report
If you use the " email report" functionality, then under some circumstances, the resulting email may contain unrendered HTML tags, because it was sent by the Notification Server as a plain text email rather than HTML.
CMS-XML Using HSSO with notifications can sometimes not send the correct link
When setting up notification server with HSSO, an e-mail directly from the item still appends the incorrect syntax, meaning the item link on that e-mail will not take you to the item.
CMS-XML Default from address for notification server always used for emails from items
The email address entered for the "Default from address" setting in Configurator for SBM 10.1 and newer was always used for emails sent from items even when the "From last modifier" checkbox was checked and the user sending the email from the item had an email address. If the "Default from address" setting is left blank, the "From last modifier" setting will work properly.
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 .
CMS-XML Escalation notifications not sent if Notification Server not running
* Has an escalation rule that sends an email with subject line "Item has been in New state too long", that starts after 5 minutes. b) Submit a new item, and make sure you get 1 email from the notification. c) Stop the Notification server (using Configurator)
CMS-XML "From user who runs transition" option should not make default address fields inactive
There are cases when we don't have user who runs transition, for instance when we are sending reply message in case of failed email submit .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs