Behavior of Inactive or Obsolete Line Items

This section describes the behavior that occurs if you change the state of a line item to Inactive or Obsolete and the line item is provisioned to a Cloud License Server (CLS) or Dynamic Monetization instance.

Note:The status Obsolete is only available if the configuration option Allow state change of entities to obsolete (under System > Configure > FlexNet Operations > General Options) is unselected.

Behavior of Inactive or Obsolete Line Items on CLS Instances

Note the following limitation for line items that are provisioned to a Cloud License Server (CLS) instance. When an entitlement line item is marked as Inactive, it is not automatically removed from its CLS instance. As a result, the CLS instance will continue to serve any inactive or obsolete line items as long as they have not reached their expiration date.

You can change this behavior using the system configuration Remove licenses from CLS when line item state is changed to Inactive/Obsolete (under System > Configuration > FlexNet Operations > General Options). If this setting is enabled and a line item that is mapped to a CLS instance is made Inactive or Obsolete, the respective line item is removed from the CLS instance irrespective of whether the features in that line item are consumed or not.

When the inactive line item is changed back to a Deployed state, and the CLS instance is provisioned with this line item—either through auto provision or by manually mapping the line item—the full line item quantity will be available. The following example illustrates the behavior:

•

The configuration setting Remove licenses from CLS when line item state is changed to Inactive/Obsolete is enabled.

•

The active LineItemA is mapped to a CLS instance and has a total quantity of 100 licenses.

•

Clients consume 30 licenses of LineItemA.

•

LineItemA is made Inactive and therefore removed from the CLS.

•

After some time LineItemA is redeployed to a CLS instance.

•

The CLS instance can now serve 100 licenses (not 70).

Behavior of Inactive, Obsolete, or Deleted Line Items on Dynamic Monetization Instances

Note the following behavior when changing the state of a line item that is deployed to a Dynamic Monetization instance.

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.

Therefore obsolete or deleted line items may eventually have tokens refunded to them which it is not possible to consume. 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.

Note:For detailed information about Dynamic Monetization, see the Dynamic Monetization User Guide that is available on the Revenera Product Documentation site.