Life Cycles

Each class may have several life cycles. A life cycle is something that assigns a state to every class instance and permits the instance to change its state via state transitions. For example, an Incident class may have Resolution life cycle that has states like Open, In Progress, and Closed.

Despite most classes will have either no life cycles or just one, it's possible to set up multiple life cycles for each class. They remain totally independent from each other.

Life cycle configuration parameters are described in life cycle properties section. Each life cycle is defined by States table and State Transitions table. The minimal life cycle configuration assumes:

• Adding at least two states
• Adding allowed transitions between those states

Once a life cycle was configured, it's possible to extend class instance dashboard with a special component that displays a set of buttons that switch the instance to the new state. This component will show a dedicated button for each transition that's currently allowed according to current state, transitions table, as well as exit and entrance conditions for the current and new states.

To add a set of state transition buttons to a class instance dashboard, open dashboard elements and add a Data Table element. In element properties, set expression to

callFunction({env/storageContext}, "currentTransitions", "class1", "cycle1", {data}, dc(), {env/storageInstanceId})

where

class1 is the name of the class which state transitions will be shown

cycle1 is the name of the life cycle

Was this page helpful?

Tell us more

Send

Thank you!