Status Life Cycles

A status life cycle is a collection of object states, policies, and transition rules that are defined for a specific object type. You can define a status life cycle for user, device, subscription, group, and offer objects to customize the behavior of MATRIXX for your business processes. For example, a device life cycle can begin with a provisioned status, transition to an active status, and finally transition to an inactive status.

Important: If a device is not associated with a subscriber, no maintenance processing, such as any automatic life cycle action, is performed on it.

Figure 1 lists the elements that make up a status life cycle.

Figure 1. Status Life Cycle Elements
  • Statuses — Defines the statuses available within a status life cycle. The status determines the behavior allowed (through policies) when the status object (that is, users, groups, subscriptions, and devices) is in that status. A life cycle status also defines the transitions to other statuses.
  • Status Policies — Defines specific behavior that can be executed in this status for specific status object types. For example, when the Add Member policy is selected for a group, if that group is in the selected status, a member can be added.
  • Status Transitions — Defines the possible statuses to which this status can transition. Transitions can be performed manually (for example, through a Modify Status SubMan API call) or automatically (for example, using conditions). A status transition can optionally define the following:
    • Transition Conditions — Defines a set of expressions that are evaluated for defined business actions. If a transition has a condition defined, this can result in an automatic transition when the condition is met. If any of the conditions evaluates to true, the transition to the next status occurs. Any condition can trigger a transition as long as all the filters also pass.
    • Transition Actions — Defines a set of actions that are performed on the transition (for example, canceling an offer when transitioning to an inactive status). Status actions are executed after the status object has transitioned to the new status.
    Important: Status conditions and actions can each include MtxFilter objects that must all pass for the status condition to be met or the status action to occur. For status conditions, the filters are applied before the object has transitioned to the new status. For status actions, the filters are applied after the object has transitioned to the new status.
Note: Status life cycles are similar to offer life cycle profiles in their use of statuses, policies, conditions, and transitions. However, status life cycles only apply to users, devices, subscriptions, and groups and use their own policies, conditions, and transitions. For information about offer life cycles, see the discussions about offer life cycle profiles and offer life cycle status codes.