Product Resolution

When FlexNet Manager for Engineering Applications is finished adding feature events to a product event, it must determine what product this event is for. In the simplest case, there would only be one possible product that included all the features that contributed feature events to the product event, and there is then no choice that needs to be made. However, if there is more than one possible product—due to multiple products including the same features—then the aggregation must resolve this list of possible products to a single product.

The product resolution is dictated by four rules of comparison, which are considered in the order listed:

1.

The product with the lowest net cost is selected. If this still results in more than one possible product, then the next rule is evaluated.

2.

From products identified by rule 1, the product with the least number of features is selected. If this still results in more than one possible product, then the next rule is evaluated.

3.

From products identified by rule 2, the product with the largest number of licenses is selected. If this still results in more than one possible product, then the next rule is evaluated.

4.

The first product created (with the lowest ID in the database) is selected.

Before these comparison rules are applied, the aggregation will first check to see that all products have valid licenses. If some do, and others do not, then only the products with valid licenses are considered. However, if none of the possible products have valid licenses, then all products will be considered; however, without product licenses, only rules 2 and 4 will have any affect on the product-resolution process.

When these rules are applied, product choice objects are created, and these product choices are displayed on the Product Choices page in the FlexNet Manager for Engineering Applications interface. There, you can override the product choice with another product, and the override you enter will be applied in future product aggregations.