Upgrade, Upsell or Renew a Fulfillment

FlexNet Operations 2018

You can upgrade, upsell or renew one or more seats in a fulfillment using capability in the Support Licenses area of Operations. The new license will be created for the currently defined server host.

This process is similar to the process of activating an upgrade, upsell, or renew entitlement line item in the Activate Licenses area of FlexNet Operations. The difference is that this process allows you to control which fulfillments are upgraded, upsold or renewed.

Important • Before upgrading or upselling a fulfillment, you must upgrade, upsell, or renew the customer’s entitlement line item for the product that this fulfillment references.

Important • Some conflicts can prevent the successful activation of upgrade line items. See Avoiding the Creation of Upgrade Line Items with Incompatible License Models for details.

Tip • FlexNet Operations can automatically upgrade line items for qualifying products and line items with the Product Version Upgrade job. See FlexNet Operations Alert Types.

When you upgrade, upsell, or renew a fulfillment, the status of the original fulfillment is changed to Obsolete and the Support Type is changed to either UPGRADE, UPSELL or RENEW accordingly. A new fulfillment is created and the Support Type is MASTER. If you upgrade or upsell only a portion of the total Count in a fulfillment, then two fulfillments are created. The status of the original fulfillment is changed to Obsolete and the Support Type is changed to either UPGRADE, UPSELL or RENEW accordingly.

For example, F1-P1 is a fulfillment for ten seats of product P1 (the Count property equals 10). You upgrade only two seats from that fulfillment to product P2. The status of fulfillment F1-P1 is changed to Obsolete and the Support Type is changed to UPGRADE. Two new fulfillments are created:

If you are upgrading or upselling a product with a floating counted, floating uncounted and node-locked counted license model and the entitlement line item for the new product specifies a node-locked uncounted license model, then the user will be prompted to define either the server host ID or the node-locked host ID (see the following table for details).

For example, in case 3 of the following table the license model changes from floating counted to node-locked counted, the new fulfillment record requires that node-locked host IDs be defined. The server host ID is obtained from the original fulfillment record, but the user is prompted to define the node-locked host IDs. If there is no change in the license model type, then all the information is retained from the original entitlement line item.

Upgrade Process

The following steps describe the upgrade process:

If there are multiple products (or entitlement line items) that this product can be upgraded or upsold to, you are presented with a list of entitlement line items that you can choose from. If there is only one entitlement line item that meets this requirement, you will not be prompted to select anything.

Important • FlexNet Operations does not evaluate the count of available copies when an upgrade is created. Therefore it is possible to create an upgrade count that exceeds the number of available copies; however, the count is evaluated at fulfillment time. On fulfillment, upgrades that exceed the available count are rejected. To avoid errors at fulfillment time, users may invoke the method getExactAvailableCount(), which returns exact number of copies available for upgrade fulfillment. This method is available as a webservice call and also as part of public API.

Avoiding the Creation of Upgrade Line Items with Incompatible License Models

Some license technology and license model conflicts can prevent the successful activation of upgrade line items. (FlexNet Operations does not prevent the creation of these upgrade line items, but the resulting line items cannot be successfully activated.) The following upgrade paths result in upgrade line items that cannot be activated:

Open topic with navigation