Assuming you have already set up a product edition, you can now create a license. By now it should be clear, that the license's edition properties, heavily influence what you can (not) configure within the license itself.
CUSTOMER AND EDITION
A license is always mapped to a customer and an edition. It is possible to transfer a license from a customer to another customer. It is also possible to change a license's edition, however only as long as the new edition has the same fundamental properties (provisioning mode and client type).
Types act as filters in most SLASCONE views. You can define types in the administration area (see CUSTOM TYPES AND TAGS)
When you create a license, you can specify the legacy (old) license key and thus create a license assignment to the (old) license system (see MIGRATING FROM LEGACY LICENSING SYSTEMS).
FEATURES, LIMITATIONS AND VARIABLES
Depending on the edition's adjustable properties, you may (not) set the values for features, limitations and variables.
CUSTOM RULES (FOR FEATURES)
Custom rules enable you to define a custom expiration date for a specific feature, which allows you to:
- temporarily (e.g., for a month) turn on a feature, without creating a new license.
- set a different expiration date per feature
Custom rules are deactivated by default, and need to be explicitly activated at the product level.
Limitations or quotas are numerical values used in order to restrict the scale of some operations, e.g., maximum number of users or jobs. Limitations can be used/interpreted by the client application either statically or in consumption-based mode.
Variables are generic fields that enable the passing of custom license information. Variables are used to transfer licensing properties that can not be represented as features or limitations. Example: a custom date.
Constrained variables are, as their name implies, variables with predefined values (populated from a custom list).
The license settings vary depending on the selected edition. You can make the following settings for the expiration date:
- Custom Date
- Subscription/Perpetual - if there is no expiration date use this setting
- Days after activation
Each license contains a log of all sent alerts. Alerts are defined as an edition (not a product) property.
The audit log ensures that every license change is archived. You can read more about the audit log here.
MANAGING USERS OF A NAMED USER LICENSE
Named user licenses allows you to create/edit/delete users. For further information see NAMED USER LICENSES.