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 Roles added to a new mashup restrict all transitions by role by default
Roles added to a new mashup restrict all transitions by role by default
CMS-XML Restrict by Rule on a transition does not have correct logic
Restrict by Rule on a transition does not have correct logic
CMS-XML Process app does not list incident type values for restricting a transition by type
Process app does not list incident type values for restricting a transition by type
CMS-XML Composer deploys transition restrictions for update transitions
Composer deploys transition restrictions for update transitions
CMS-XML Transition Group Restrictions and User Field Selections check-box not enabled by default after upgrade
Transition Group Restrictions and User Field Selections check-box not enabled by default after upgrade
CMS-XML Dim CM 2009 R2.02: Removing state from lifecycle does not clean up old transitions and causes unique constraint violations
An off-normal transition was also defined from A to D. In the Admin Console delete state C. The operation works. Then delete state B. No error is reported, but when you attempt to create an object using the lifecycle, for example a Request, an Oracle error is generated indicating a unique constraint violation on PENDING_ACTIONS_K1. Dimensions has correctly added the new normal transition from A=>D, but it has not deleted the original off-normal transition.
CMS-XML Item Type not checked before running a transition
Steps to reproduce 1. In SBM Composer, go to Workflow Design > select a transition (e.g. Assign) and click the “ Restrict by Type” tab in the Properties editor. 2. Allow the transition to be available for Item Type A only
CMS-XML Restrict by Item Type does not work for mass update
A transition that is restricted by item type. The transition should not be available for ItemType "MASTER".
CMS-XML Role transition gives additional privileges under certain conditions
" Transition 1" on "State A" is restricted to Role 1 only. ("Transition 1" has only "Role 1" selected in "Restrict by Role" tab).
CMS-XML Incorrect invocation of "A repeat of the same transition for the same item has been detected"
For the moment, AE workflow engine has no such built-in constructs as loops or cycles, and trying to emulate looping behavior with decision steps and transition actions leads to runtime errors. This limitation is based on transition actions internal design, which is rather static as relies on stack size ( stack memory size cannot be changed at runtime ).
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs