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 Changing the Notification link from User Workspace to Work Center for the whole of SBM in the Application Administrator
field again, it is applied to all notifications , including those that were overridden. Therefore, use caution when applying the global link
CMS-XML Notifications stop working due to UUU (Unicode Upgrade Utility) accidentally being performed on 6.6.x database.
This leaves all text and varchar fields in the 6.6.x database as ntext and nvarchar. The database may still work correctly, however the notification server will be unable to read the e-mail addresses in the TS_NOTIFICATIONMESSAGES table, and fail to send messages. No errors will be logged in the ttmail.log,
CMS-XML View hidden fields in notification
View hidden fields in notification
CMS-XML Notification rules that check if there is text in a field or not
Some users want the ability to have a field not be required, but would like to be notified if a field is not filled. Or, perhaps to have a field that holds special notes, and be alerted
CMS-XML Creating Delayed Notifications
field rather than on a specific change in an item. These notifications can serve as reminders for users to act on items.
CMS-XML TS_Notification records and values of TS_Type field
Each record in the TS_NOTIFICATION table has a designated type used to classify the notification . Here is a list of those field values.
CMS-XML Dim10: Cannot shutdown email communication / notifications on unix systems
On Unix systems, disabling the following value field in dm.cfg is not sufficient to stop email notifications from going to users. #DM_DMEMAIL #DM_MAIL
CMS-XML How to get logging from a Notification that calls a web service.
When you create a notification you can have it call a web service as its action and map return fields from the web service to your sbm item. These can be tricky to troubleshoot because there isn't a lot of logging that takes place. The log for these events should show in the ns.log file.
CMS-XML Problem: Notify is sending duplicate messages and is not sending all of the messages.
Notify stops scanning a project when it finds a user who needs more messages sent than what the settings specify in SEND AT MOST in the Notify Options. Notify also does not increase the NFYTID field in the trkusr table for that user so that when it scans the database again the next time it sends out the same messages and then quits again. (i.e.
CMS-XML TT: From: address in notifications does not populate
If the System field "Last Modifier" has been deleted (that is it's now currently in the Deleted Fields section of the Workflow's Default Field List), the "From:" on the email will not populate correctly.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs