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 Problem with Notifications
Steps to reproduce the problem Step 1 - Create a notification based on the following rule . Active/Inactive Is Equal To Active AND Secondary Owner Added Current User
CMS-XML Problems with notifications - date-testing routines can cause issues and kill NS processes
There is a possibility that a rule which checks datetime values in fields can cause Notification Server processing to stop without any visible warning.
CMS-XML Rules associated with notifications can be deleted
See ' Problem ' above. See 'Problem' above. See 'Problem' above.
CMS-XML Snapshot promotion loses Multi-user field rule comparison value for notification rules that compare multi-user field with
When a mashup is promoted that contains notification rules a problem can occur if the rule has a comparison of a Multi-user field in form of "field-name" contains (Current User). The rule on the target environment appears as "field-name" contains (None).
CMS-XML Problem: #1064 Users stop receiving In Tray or E-mail notifications
1. The users notifications rules are not setup as expected. Ensure that the user or the user group in question has the appropriate notification options set before troubleshooting further. For example, setup a notification rule so that the user is notified via the In Tray if any SCR is submitted (make sure that Ignore is Author is set to No).
CMS-XML Sub-Relational field lost in rule notification configuration when promoting to a new environment.
It seem there is a problem with the sub relational field in the rule notification , because when you promote a process app to an another environment,all is good but in the notification rule you notice that the value specified in the column value is lost (only the sub-relational field) in the notification rule . You have to manually fix it for each promote.
CMS-XML Notification or rule fails to move to target environment during promotion
In checking the database, there was no UUID for the new notification or rule. After testing, the problem could not be reproduced.
CMS-XML Notification rule "Changes To" does not work when used with single relational field
This is a known problem . The workaround (for pre-10.1 systems only) at the moment is to use this instead of "Changes To": CHANGES
CMS-XML Impossible to create a notification rule with sub-relational date field in case of 2 process apps
If you attempt to create a rule using a sub-relational date field from another application, you will get "error #1009" and the rule will not be saved. The original problem , reported in DEF131117 was fixed only when the sub-relational field is in a table in the same ProcessApp.
CMS-XML TT65: Notification rule for date field not gives error: "A Value is missing"
This is a known problem at TT65, fixed in patch 65018 and TT66.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs