Status Life Cycle Configuration
The general procedure for defining a status is:
- Create a new status for a specific object type (user, group, subscription, or device).
- Select the policies that can occur in the new status (such as modify a subscription).
- (Optionally) Add transitions from the new status to existing statuses.
- For each transition, you can optionally
add the following:
- Conditions that can cause a transition to another status.
- Actions that occur because of a transition (such as on inactivity, suspend all offers).
- Once all your statuses have been created, specify the status assigned to a newly-created object by clicking Set Default. The object is given this status if a status is not directly specified upon creation.
Status life cycles are configured in My MATRIXX.
The following components and settings can impact status life cycles.
- Notification settings for product
offers and balances. Note: Notifications for object status changes for users, devices, subscriptions, and groups are generated automatically. For a complete list of possible notifications, see the discussion about notifications in MATRIXX Integration.
- Suspend settings for product offers.
- Normalization on a life cycle state enables use cases such as the following:
- Charge differently based on a life cycle status. For example, pricing can be set up to charge subscriptions with an active life cycle status a discounted rate and subscriptions with an inactive life cycle status a regular rate. For more information, see the discussion about normalization in My MATRIXX Help.
- Deny service based on a life cycle status. For example, use normalizers
to deny offer purchases when a subscription is in an incorrect life
cycle status. To deny catalog item purchases, normalize on the object
StatusValue
field in the charge component and deny for the incorrect status. Denial codes in this situation are not returned.
For information about object status notification fields and status life cycles, see MATRIXX Subscriber Management API.