Specifying a Product and License Model when Creating a Line Item or Bulk Entitlement
To deploy an entitlement line item or bulk entitlement, at least one product and one primary license model must be defined. The contents of Web Service requests that create entitlements may or may not specify product and license model data explicitly, but between the request contents and the product data in FlexNet Operations, there must be enough information provided to uniquely define at least one product and one primary license model on the line item or bulk entitlement. You can define what is necessary in several ways, depending on the following factors:
| • | The number of license models linked to a product |
| • | The mapping of part numbers to products |
| • | Are part numbers mapped to products? |
| • | How many part numbers are mapped to each product—one to one or many to one? |
A part number can be mapped either to a particular product-license model pair or just to a product. Each part number can be mapped to only one product, but one product can have many part numbers mapped to it.
There are two primary ways to specify a product and license model:
| 1. | Use the product element (preserved for backward compatibility) or no element to specify a single product. |
| 2. | Use the entitledProducts element to specify one or more products. |
The entitledProducts element includes one or more entitledProduct elements, and each entitledProduct element contains a product element and a quantity. In the request, it is possible to use either a single product element without entitledProducts or to use an entitledProducts element that contains one or more products, each encapsulated in an entitledProduct. Use either the product element or the entitledProducts element in the request, not both.
Tip:For update operations with multiple products, use updatedEntitledProducts instead of entitledProducts.