Common stage actions taking precedent over user stage actions
I thought that user actions from a common stage would always show AFTER the stage actions but that doesn't seem to be the case. I can't make the priority on the action larger than the number of actions coming from the common stage but I really don't want the "Cancel" to be the first action available to the user.
Am I missing a setting or am I just stuck?
Thanks!
Tagged:
0
Comments
-
Go to the properties on the Process itself and set the stage order for this. If the Common Stage comes before the process stage then the actions associated with the common stage will come before the process stage. The priority of the actions comes in to play next for each stage
0 -
Perfect! Thank you.
0
Categories
- All Categories
- 123 Developer Announcements
- 54 Articles
- 155 General Questions
- 148 Thrust Services
- 57 Developer Hackathon
- 37 Thrust Studio
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 918 Core Messaging
- 84 Digital Asset Management
- 9.4K Documentum
- 32 eDOCS
- 190 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 9 XM Fax
- Follow Categories