Entitlement Management
This section describes the enhancements introduced in 2020 R1 for managing entitlements:
| • | Support for Multiple Values as Search Criteria in Advanced Search Dialog |
| • | Account ID Added to Screens |
| • | Support for Removing Users |
| • | Entitlement Transaction History |
| • | Configuration for Displaying Custom Attributes |
| • | New Variable for Vendor String |
| • | Ability to Link User/Entitlements from Self-Registered Account to Customer Accounts |
| • | Specifying Email Template During Entitlement Creation |
Support for Multiple Values as Search Criteria in Advanced Search Dialog
Text-entry fields on the Advanced Search dialog now permit multiple-string values. Each entered string is separated with a comma. The OR operator is used to process multiple strings entered for a given field. This feature is available on only the Advanced Search dialog invoked from List of Entitlements by Order page.
The Account ID is now displayed along with the Account Name on Entitlement screens, making it easier to identify the correct account when multiple accounts have the same name. Also, the account Name (account ID) entries on drop-down lists are shown in alphabetical order to further help in locating an account.
Previously in FlexNet Operations, producers could permanently remove a user (customer or partner) if the user had no dependencies—such as line items, entitlements, fulfillment records, import jobs, shipment records, alerts, subscriptions, and so forth.
With this release of FlexNet Operations, if the user has such dependencies, a force delete option is now available. The force delete will ensure that the user record and its dependencies are retained but placed in an inactive state. In this state, all fields in the user record are rendered obsolete, login-credential resets for the user are prohibited, and no further access to the user record is allowed.
Note that this option applies only to the forced deletion of non-producer users with dependencies.
For more information about deleting users, see the Producer Portal help system.
Entitlement Transaction History
Entitlements have been added to the list of entities viewable in the transaction history. The entitlements can be accessed either by searching for the transaction history (click System Transaction History) or by clicking the View Transaction link on the Create an Entitlement page (click on Entitlements > List Entitlements by Order then click on an entitlement). The transaction history of an entitlement includes a summary section listing the entity type, entity ID, user ID, event timestamp, and event type. The transaction details also include two tabs—Show all fields, which displays all the information about the entitlement, and Show only differences, which displays only the before and after values of the changed fields.
Configuration for Displaying Custom Attributes
A new configuration setting Show maintenance line items custom attributes in Entitlements Page has been added to the Producer Portal. The setting is located in System Configuration > FlexNet Operations > General Options.
The setting controls whether custom attributes for maintenance lines are visible in the Producer Portal and End-User Portal at the following locations:
| • | On the List Entitlements and List Entitlements By Order pages |
| • | On the Maintenance Line Item Details panel |
By default, this setting is not enabled, nor are custom attributes for maintenance lines visible.
New Variable for Vendor String
A new variable {Feature.version} has been introduced for the Vendor String field. If this variable is defined on the Create a License Model page, the FlexNet Publisher license generated with the specified license model will contain the feature versions.
The format of the feature version specified using the {Feature.version} variable depends on its location:
| • | The Vendor String field outside of the FlexNet Publisher license lists all the feature versions available in the product as comma-separated values. |
Example
5.0, 1.0, 2.0
| • | Within the FlexNet Publisher license, each individual INCREMENT line displays the VENDOR_STRING keyword with a specific feature version. |
Example
SERVER this_host ANY
VENDOR demo
USE_SERVER
INCREMENT F5 demo 5.0 permanent 1 VENDOR_STRING=5.0 \
PLATFORMS="alpha_n alpha_l amd64_s" DUP_GROUP=SITE \
ISSUER=UNKNOWN_ORG_UNIT ISSUED=24-oct-2018 \
NOTICE=UNKNOWN_ORG_UNIT SN=UNKNOWN_ORG_UNIT START=22-oct-2018 \
SIGN=”003E 53DI 42ID 56ZN 9568 EI41 NM3B 397R 307A 4B4T 9568 \
EI41 NM3B IE35 33ER"
INCREMENT F1 demo 1.0 permanent 1 VENDOR_STRING=1.0 \
PLATFORMS="alpha_n alpha_l amd64_s" DUP_GROUP=SITE \
ISSUER=UNKNOWN_ORG_UNIT ISSUED=24-oct-2018 \
NOTICE=UNKNOWN_ORG_UNIT SN=UNKNOWN_ORG_UNIT START=22-oct-2018 \
SIGN=”TZ3E 540I 4ILD 90HN ZN95 68EI 41NM 3B39 7R30 7A4B 4568 \
IE55 IL51 NMIE 3533 K3ER"
INCREMENT F2 demo 2.0 permanent 1 VENDOR_STRING=2.0 \
PLATFORMS="alpha_n alpha_l amd64_s" DUP_GROUP=SITE \
ISSUER=UNKNOWN_ORG_UNIT ISSUED=24-oct-2018 \
NOTICE=UNKNOWN_ORG_UNIT SN=UNKNOWN_ORG_UNIT START=22-oct-2018 \
SIGN=”3E54 0I4I LD90 HNZN 9568 EI41 NM3B 397R 307A 4B45 69UE \
ILK8 5NMI E353 3K3E LP9R"
Ability to Link User/Entitlements from Self-Registered Account to Customer Accounts
On the Entitlements > Merge page, user roles assigned the Merge Entitlements from Self-Registered Account to Customer Account permission have the option of selecting a self-registered account for the Source Account. In this way, a user and entitlements from a self-registered account to be linked to a customer account. A user from the customer account logging into the End-User Portal is then able to see the entitlements and users of the self-registered account.
Specifying Email Template During Entitlement Creation
User can now select an email template from the Email Template variation drop-down when creating an entitlement. If no template is specified, then the template specified by the license technology is used. If an email template is not configured for the license technology, then the default email template is used.