Assets and Subscriptions in Multiplay Subscription Management (Managed Package)

Multiplay Subscription Management lets you enable or disable the use of subscriptions to track assets. Subscription tracking determines whether you use assets or subscriptions to show information and drive workflows. You can enable or disable subscription tracking on products in the product catalog.

This feature is part of the Communications Cloud managed package.

Here's how assets and subscriptions are used in Multiplay Subscription Management:

• A subscription is intended to track the lifecycle of a user's services. A user can have multiple subscriptions. For example, a user who has two mobile services has two subscriptions, one for each service.

• Each subscription has its own set of balances, which enables you to track usage on a subscription.

• The subscription number that's generated for each subscription is used to associate the subscription with a subscriber on the online charging system (for example, the Matrixx instance).

• In Multiplay Subscription Management, by default, assets – not subscriptions – are used to identify services, drive workflows, and display information. The root asset ID is a key parameter in many workflows to pass input to underlying Integration Procedures and Data Mappers.

• If you enable subscription tracking on a product, whenever that product is ordered, a subscription is created and associated with the root asset. The start date of the asset is associated with the subscription, enabling you to track the start of the service. If you don't enable subscription tracking on a product, no subscription is created.

• If you enable subscription tracking on a product, the asset ID is used to find the subscription number of the associated subscription. This subscription number is used in workflows that require integration with the online charging system (for example, Matrixx).

If you want to enable subscription tracking in your org, here are some recommendations:

• Decide if you want to enable subscription tracking on a product before you start to use the product in orders. If you change subscription tracking on a product after that product is used, it leads to inconsistent behavior in workflows.

• For standalone plans, such as the prepaid plan, enable subscription tracking to track each product as a separate subscription.

• You can enable subscription tracking for plans, such as the mobile plan. However, products such as handsets usually don't require subscription tracking and we recommend that you don't enable subscription tracking for products that don't have an associated service.

• In general, use subscription tracking for products that require the plan or service continuity to be tracked while assets could change. For example, you can use subscription tracking if you implement a custom change of plan workflow, in which new assets can be associated with the existing subscription.

To enable or disable subscription tracking, see Enable or Disable Subscription Tracking on Products.