Summary

What's the FlexNet Publisher design rationalization behind OPTIONS=SUITE?

Question

What's the business value of OPTIONS=SUITE for FlexNet Publisher (FNP)?

Answer

Package license is linked with set of different components. Package licenses are for the consumption of Publisher and not for End User. In other words, with package licenses Publisher can organize that how components licenses to be consumed. Package with OPTIONS=SUITE, is specialized variant of package licenses. Server checkouts package licenses also with component licenses. As a result, it can introduce component license consumption conditional and can make whole package more productive. Component licenses can be consumed in different valuable permutations as per requirement. Let us consider some use cases to understand well:

1. PACKAGE pkg_lic flexera 1.0 COMPONENTS="comp1 comp2 comp3" OPTIONS=SUITE SIGN=
INCREMENT pkg_lic flexera 1.0 28-mar-2019 3 SIGN=
   Package pkg_lic contains 3 licenses and 3 components. Publisher has provided 3 licenses for package. End user can use any 3 component licenses. It can be all 3 licenses of comp1 or 1 each license of comp1, comp2, comp3. Publisher able to diversify the usage of product as per end user need of the time.
2. PACKAGE pkg_lic flexera 1.0 COMPONENTS="comp1 comp2 comp3" OPTIONS=SUITE SIGN=
INCREMENT pkg_lic flexera 1.0 28-mar-2019 2 DUP_GROUP=U SIGN=
   Package pkg_lic contains 2 licenses and 3 components. Publisher can make package more cost effective by enabling two components and disabling one. End user can use any 2 components. It can be either comp1,comp2 or comp2,comp3 or comp1,comp3. As it DUP_GROUP=U, end user can check out already checked out component unlimited times. Publisher can change package configuration in license file anytime by adding one more package license, if wants to enable third component also.
3. PACKAGE pkg_lic flexera 1.0 COMPONENTS="comp1 comp2 comp3" OPTIONS=SUITE SIGN=
INCREMENT pkg_lic flexera 1.0 28-mar-2019 1 DUP_GROUP=U SIGN=
   Package pkg_lic contains 1 license and 3 components. It is a good alternative where Publisher wants comp1, comp2, comp3 should be used exclusively. End user can use any of them with exclusivity.

These are some of the basic use cases which can be easily achieved with OPTION=SUITE. With this provided solution, Publisher can package the product in different permutations. Product monetization will be streamlined as per requirements.