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 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 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 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 web service mapping does not work properly in some cases
Given a process app that has a field called "UniqueID".
CMS-XML Notication Rule: "Binary field is Equal to Checked" is not working as expected
The following rule is not firing the notification when the "Update" transition is used. It does fire as expected upon Submit and when the item is transitioned to a different state.
CMS-XML The $FIELDVALUE parameter for displaying the last x journal field entries is not always working
On SBM 11.2 one can stipulate how many of the last Journal field entries will be sent out in a notification . Below is an excerpt from documentation : (JOURNAL_FIELD_NAME, 1) - For Journal fields, this displays the last comment in the specified Journal field.
CMS-XML When the Notification Server uses (Exchange web service) the option "Default from address" doesn't work.
When the notification is sent with the user account that is configured with "Login" from SMTP - (Exchange - web services), if the option "Default From address" is set with a different address, the option "from" is not replaced by "Default from address" user account. So, this field "Default from address" doesn't work when the notification server is set to use "Exchange - web services" in the STMP.
CMS-XML Append-only journal field omitted from $CHANGES() in Notification
If you use $CHANGES() in a notification template, then the notification will not contain the content of any append-only journal fields. You may work round this problem by specifically adding the field to the list of fields sent in the notification , when it will appear correctly, provided that the recipient has permissions to view the field .
CMS-XML Search filter for object value in notification rule does not show any results for some field types
Search filter for object value in notification rule does not show any results for some field type. Specifically it does not work with Sub-Relational field based on User, Single-Selection and Multi-Selection field types.
CMS-XML "View Item if Secondary Owner" permission does not work for notifications
Subscribe the group to this notification. Add the "Secondary Owner" field to the submit form (and deselect "(Auto)" in secondary owner list). Submit an issue and select the user as the Secondary Owner.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs