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 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 Include Serena Work Center item link along with User Workspace item link in notification email template
Notifications field again, it is applied to all notifications , including those that were overridden. Therefore, use caution when applying the global link type.
CMS-XML Multi-Group fields not working correctly in notification rules
Steps to reproduce Create a notification based on the following rule. - Any Incident Is Submitted
CMS-XML Multi-group fields are not working in Notifications rules
Steps to reproduce Create a notification based on the following rule. - Any Incident Is Submitted
CMS-XML Delayed notifications stop working and do not send
Notifications with delays can stop working and not send if there is a delay notification that has a delay condition that uses a field that does not have a value on items. This causes those notification events to not get processed for the delay and they will build up in the database. The default setting for the Notification Server is to process 600 delay notification events per cycle and if there are more than 600 of those stuck delay notification events, the working delay notifications will not get processed and all delay notifications will not be sent.
CMS-XML Creating or modifying notification rule that includes a user field with many users is slow
User fields that have many users as available selections can cause modifying or creating a notification rule that includes one or more of those user fields to slow down the Application Administrator, making it difficult to work with the notification rule because the system attempts to load the entire list of users in the field .
CMS-XML Search for field name on Fields tab for notifications in Application Administrator does not filter like other searches
The search for field name on the Fields tab of a notification in Application Administrator does not filter the list of fields in the same way that all the other searches work in Application Administrator. It only highlights the search string in the field names and does not filter the list at all. If there are no fields with the search string in the first part of the list, the user can't tell that anything happened at all so it appears to them that it didn't work.
CMS-XML Notification emails do not include MAILTO links to users in multi-user fields
For HTML email templates, the $FIELDVALUE(USER_FIELD_NAME) tag is supposed to include the name of the user(s) in the field AND make each name a clickable MAILTO link. This only works for single user fields when it should work for both single user and multi-user fields .
CMS-XML Notification rule "Changes To" does not work when used with single relational field
A notification rule that is supposed to be triggered when: a user field is EQUAL TO (Current User) AND a single relational field CHANGES TO "somestring" is not triggered.
CMS-XML Notification web service mapping does not work properly in some cases
Given a process app that has a field called "UniqueID".
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs