Offer Life Cycle Profile Configuration

Offer life cycle profiles, their status definitions, and offer life cycle codes are configured in My MATRIXX. A default offer life cycle profile named MTX is provided and used if no profile is defined for an offer or bundle. If the offer life cycle profile defined for the offer is different than the offer life cycle profile defined for its bundle, the bundle's profile is used. The status of the bundle applies to the entire purchased item.

Important: Do not make any changes to the default offer life cycle profile if there are pre-5200 purchased offers in the database. Changes may prevent the environment from upgrading properly.
Normalization on an offer life cycle profile state enables use cases such as the following:
  • Charge based on an offer life cycle profile state.
  • Deny service based on an offer life cycle profile state.
For example, pricing can be set up to do the following:
  • Offers with an active life cycle state — Charge a discounted rate.
  • Offers with an inactive life cycle state — Charge a regular rate.
For more information, see the discussion about normalization.
The general procedure for defining an offer life cycle profile is:
  1. Create and define the offer life cycle status codes in My MATRIXX. These codes link to the offer status definitions within the profile. Default codes are provided and are used in the default MTX offer life cycle profile.
  2. Create a new offer life cycle profile in My MATRIXX.
  3. Edit the offer life cycle profile properties, including defining if this offer life cycle profile is used as the default.
  4. Edit the profile's list of status definitions. Each definition that is provided by default is listed and linked to an offer life cycle status code. Add and delete the status definitions as needed.
  5. For each status definition:
    • Edit the status definition's properties.
    • Select the policies that apply to the status definition. The polices define the actions that occur because of a transition (such as on inactivity, suspend all offers).
    • Add transitions to determine which status an offer can transition to. Transitions from one status to another can be triggered through automatic transactions (for example, an automatic activation on usage) or explicitly through SubMan API calls.
  6. If new offer life cycle status codes have been added after the offer life cycle profile was created, you can add a new status definition that links to the new status code.
The following components and settings can impact offer life cycle profiles:
  • The grace period profile is used to specify information about a grace or recoverable period after recurring failure, such as the duration of the grace or recoverable period, the policy for determining the new cycle time on successful recovery, and whether to create a notification when transitioning. The grace period profile is specified in the cycle data of the offer or bundle. For more information, see the discussion about grace period profiles.
  • Notification settings for product offers and balances.
    Note: Notifications for purchased item status changes are generated automatically if the notifications are enabled. For more information about notification fields for offer life cycle profiles, see the discussion about the MtxPurchasedItemStatusChangeNotification, MtxOfferPurchaseNotification, and MtxBundlePurchaseNotification MDCs in MATRIXX Integration.
  • Suspend settings for product offers.
  • You can use the StatusValue, StatusClass, and LifecycleProfileId fields in a normalizer. For more information, see the discussion about normalization.