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 KM-Dim10: Reported Defect DEF80502: rpcp with transitions from and to same state fails for "/DETAIL /SECTION=all"
When running rpcp against the product using section= pcat,cdoc,role, rule When attempting to use section=item or section=all dmcli terminates inmediately with session expired.
CMS-XML Incorrect invocation of "A repeat of the same transition for the same item has been detected"
A repeat of the same transition for the same item has been detected. The state/transition actions chain has been terminated to prevent the possibility of an endless loop. The above error message is not always adequate as it appears even then when there is a workflow Rule which should prevent the loop becoming endless.
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 If you have a notification rule with a transition value and promote then it is incorrect or none in targe
If you have a notification rule with a transition value and promote then it is incorrect or none in targe
CMS-XML SBM: Rule is removed from Restrict by Rule when transition is moved
When a transition's "From" state is changed, the Rule that is selected as the "Restrict by Rule" is removed. The "Restrict by Rule " option is still checked, but the rule is no longer selected.
CMS-XML KM-Dim10: Reported Defect DEF108253: Issue Fixed in Dimensions 10.1.1: Attribute rules may function incorrectly under certain conditions
Transitions may define multiple rules for the same attribute. In Dimensions 10.1.0.2 if one of these rules has no defined "TO" state and is not mandatory it can override a mandatory rule with the same "FROM" state.
CMS-XML Possible reason for the Composer validation error "The decision 'decision_name' must have a transition with the Otherwise rule"
When you use the decision rule in a Workflow in Composer it is a requirement that one transition MUST be mapped to the "Otherwise". This is a special rule type and it is not sufficient to just have an alternate transition rule .
CMS-XML Decision: Items are incorrectly routed to the "otherwise" rule
2. In the child workflow, you have another transition using that same rule which appears below the parent transition rule . 3.
CMS-XML Copied decision rule keeps original rules even when a transition is not assigned
Copied decision rule keeps original rules even when a transition is not assigned
CMS-XML Notification Rules containing Fields with same name not displaying correctly
Two fields share the same field name (DB Field Name is different, of course). One is a text field and the other is a single selection field. When creating notification rules , the fields are listed in the following order:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs