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 The highest number of minutes/hours/days an escalation or repeat of notification can be set to is ten
The highest number of minutes/hours/days an escalation or repeat of notification can be set to is ten
CMS-XML Creating Repeating Notifications
Select the Escalations tab. In the Termination Rule
CMS-XML Escalation notifications not sent if Notification Server not running
* Sends an email with subject line "Item is in the New state" * Repeats every 1 minute until the item is no long in the New state (The repeat is not necessary but makes it easier to see the problem.) * Has an escalation rule that sends an email with subject line "Item has been in New state too long", that starts after 5 minutes.
CMS-XML Change for Notification and Escalation rule name saves incorrectly
Steps to reproduce : 1. Go to Application Administrator->Notification. 2. Select any Notification and press Details.
CMS-XML Copying Notifications
All properties are copied to the new notification. Escalation tab All properties are copied except for the following:
CMS-XML Duplicate escalations
An escalation may run multiple times instead of just once if the escalation has a rule associated with it and the "Attempt to send all notifications for an item" option is checked on the Performance tab of the Configurator in SBM 10.1.1.4. To work around the issue, the "Attempt to send all notifications for an item" option should be unchecked in the Configurator or the "ns-default-config.xml"
CMS-XML Notification Server leaving orphans in TS_NotificationEvents on Notification deletion.
This immediately caused warnings to be generated that the notification server was trying to process entries in the TS_NotificationEvents table that didn't have an associated Notification. Even though the notification had been deleted, users were still receiving emails. These were associated with escalations / repeats .
CMS-XML Notification Server Cycles and Troubleshooting (TeamTrack through SBM 2009 R4)
If the email is set to repeat (e.g., email every day until owner changes) or to escalate (e.g., email in seven days if the item hasn't been updated) then the event will not be deleted after the initial send: the system will hang on to the event record and will create another email when that repeat or escalation time period is reached
CMS-XML Notification Server Cycles and Troubleshooting (SBM 10.1 and above)
If the e-mail is set to repeat (e.g., e-mail every day until owner changes) or to escalate (e.g., e-mail in seven days if the item hasn't been updated) then the event will not be deleted after the initial send: the system preserves the event record and creates another e-mail when that repeat or escalation time period is reached.
CMS-XML Notification history uses event date instead of message date
Notification history appears to have duplicate recipient entries for repeat or escalated notifications . The notification date and time is shown with a list of recipients that is duplicated.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Delivering changes from a work area to a stream (demonstration)
This demonstration shows you how to deliver changes from a work area to a stream in Dimensions CM, restrict the deliver to specific folders in the work area, and relate a new item to the correct design part.
Dimensions CM: Updating a work area from a stream (demonstration)
This Dimensions CM demonstration shows you how to update a work area from a stream, restrict the update to specific folders in the stream, and exclude files from the update.
Dimensions CM: Working with Items, Part 2 (demonstration)
This Dimensions CM demonstration shows you how to copy item revisions to a work area using the Get and Update commands, deliver a modified file from a work area to a stream using the Deliver command, and action an item revision
Dimensions CM: Introduction to streams (demonstration)
This demonstration introduces Dimensions CM streams.

Additional Assistance

  • Submit a Case Online
  • FAQs