Configure the release process
The release process combines user/groups, ACLs, and states to produce patterns for data flow from creation to manufacturing. Whenever someone tries to access data, Creo Elements/Direct Model Manager checks the ACL to see what tasks the user has permission to perform on the data while in its current state. The figure below shows the default process:
There are three different ways to implement a release process:
1. If <ChangeStateAction> does not exist in your custom xml file, by default,
◦ You can change a parent assembly's state regardless of a child's state.
◦ You can multi-select objects to change state. You can move to any state that all of the objects share in common.
The default stateflow shown above is defined in the DT_STATEFLOW database class.
2. If you include <ChangeStateAction> in your custom xml file, but do no customization of the release process,
◦ Creo Elements/Direct Model Manager uses the <ReleaseProcess> definitions from wmconf.xml that define states and their precedence (as shown in the above figure - see DMReleaseProcess and DTReleaseProcess). The <Index> tag value (in the <StateOrders> definitions) defines the precedence of states.
◦ A parent assembly's state cannot advance unless its children already exist at the advanced state or higher.
3. If you include <ChangeStateAction> in your custom xml file you can use the following tags to customize the <ReleaseProcess>,
◦ <AutoReleaseDrawing>
◦ <CheckDrawing>
◦ <ReleaseLevel>
◦ <StateAfterRelease>
◦ <StateOrders>
▪ <Index>
▪ <Type>
To add or remove states, you must make the appropriate changes to the DT_STATEFLOW database class and in your custom xml file.