State transition default action requirements for record types
Record
types can include numerous state definitions. However, UCM-enabled record
types must have at least one path of transitions among state types as follows:
Waiting to Ready to Active to Complete. The transition from one state to the
next must be made by a default action.
For example, the following figure
shows the actions and default actions between the states defined in the UCM-enabled BaseCMActivity
record type included in the predefined UCM schema. The states are Submitted, Ready,
Active, and Complete. The corresponding state types appear to the right of the states.
Figure 1. State transitions of UCM-enabled BaseCMActivity record type
In addition to this single path requirement, states must adhere to the
following rules:
All Waiting type states must have a default action that transitions to
another Waiting type state or to either a Ready or Active type state.
If a Ready type state has an action that transitions directly to a Waiting
type state, that Waiting type state must have a default action that transitions
directly to that Ready type state.
All Ready type states must have a default action that transitions to another
Ready type state or to an Active type state.
All Ready type states must have at least one action that transitions directly
to a Waiting type state.
For the BaseCMActivity record type, its initial state must be a Waiting
type.
Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.