Behavior When Line Item Status Changes in the Back Office

When a line item’s status changes in the back office to Inactive or Obsolete, or when a line item is deleted in the back office, client applications can no longer consume tokens from such line items. While Dynamic Monetization allows refunds to be made to such line items, deleted or obsolete line items cannot consume those refunded tokens. Action should be taken to account for these, either by means of a refund to end customers or by adding them to a newly created line item. Inactive line items can have their status returned to Deployed, which will allow them to consume tokens.

This section details the behavior for each line item status.

If a line item is made inactive in FlexNet Operations, Dynamic Monetization does the following:

•

No longer allows tokens to be consumed from the line item.

•

Allows refunds to be made to the line item (for example, when a second access request is received).

•

Continues to allow tokens to be consumed from the line item when its state is returned to Deployed.

If a line item is made obsolete in FlexNet Operations, Dynamic Monetization does the following:

•

No longer allows tokens to be consumed from the line item.

•

Allows refunds to be made to the line item.

If a line item is deleted in FlexNet Operations, Dynamic Monetization does the following:

•

No longer allows tokens to be consumed from the line item.

•

Allows refunds to be made to the line item.

•

When no sessions are using it, deletes the line item.

Note:Call /provisioning/api/v1.0/instances/{instanceId}/line-items using GET to retrieve the line item status: DEPLOYED, INACTIVE, or OBSOLETE.