Object Life Cycle
introduction
Components
FLOW
A life cycle flow defines the complete life cycle of an object within AVIX. It is composed of a number of statuses and transitions that connect them.
configuration
Handler
Prio
Active
Any Life Cycle Flow not set as active will not be available for use by its applicable objects.
Automatic
If a Life Cycle Flow is marked as automatic and has the highest priority off all the applicable flows then any new objects created will automatically start in that flow.
Applies to
A list of AVIX object types that can use this flow. If a parent in the tree structure is selected then the flow will apply to all children of that parent.
Default Status
This is the status a new execution of this flow will start in.
End Status
The statuses that can be chosen as "goals" in the Status editor page. The actual statuses that are selectable will depend on the flows accessible from the object's current status.
Default Path
The path that will be shown in the Status editor page for objects in this flow. After the object has started its flow the path can then be modified by the user to reach another goal status.
Hidden Transitions
A list of transitions that should be hidden and not shown in path. This can be useful when transitions should not be selectable by the user but still executable by for instance a trigger in another flow.
Post Triggers
This is a list of triggers that will run for every status in the flow. See the heading about triggers for more information on triggers.
Status
Statuses are descriptions of the life cycle state an object is currently in. Configuration wise it is composed of all its outgoing transitions and configured triggers.
A status can set its security context and any object in that status is also in that security context. Permissions set by the access control system can belong to different contexts. Therefore an object can have different permission depending on what status it is in currently. If this behaviour is not desired then the context should be left as default.
Transition
Transitions are ways for objects to move from one status to another. They can be configured to only be executable if certain conditions are met or to trigger actions when executed.
Configured Condition
A condition is a pre-defined set of prerequisite that can be created as a configured condition for transitions. A transition with one or more conditions attached will not be executable before all of its conditions' prerequisites are fulfilled.
The conditions active for the current transition are shown below the text box in the Status editor page.
Configured trigger
A trigger is a pre-defined action and can be created as a configured trigger for either a transition or a status. Configured Triggers attached to transitions will only execute its trigger when that transition is executed, configured triggers attached to statuses however will always execute their trigger when the object reached that status.
Triggers attached statuses are always executable but those attached to transitions might have prerequisites that need to be fulfilled before the transition can execute. If the triggers for a transition are executable is displayed below the text box in the Status editor page.
Configured Trigger & Configured Condition
The configuration options of a configured trigger or configured condition are tied to what trigger or condition is selected. As such the configuration options for different triggers or conditions are in most cases specific to the selected trigger or condition.
Keys
Flows, statuses and transitions all have a key to identify them. It is important that this key is completely unique.
scripts
TBA