Creating a Product
SLASCONE provides a solid framework allowing you to define your licenses requirements, regardless of your business model. When creating a product you can use the following properties:
- Goodwill Devices
- Software Release Limitations
- Expiration Types
In most cases, you are going to use only a subset of these properties. As your products and/or your business models evolves adjustments might be necessary.
Features enable the activation/deactivation of product functionality. A feature can be either on or off.
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.
SLASCONE provides 2 types of license keys:
- Master license key: when you create 1 license with n devices, SLASCONE generates 1 master license key and n device license keys. The master license key can be used n times for activation.
- Device license key: a device license key can be used only once for activation.
Let’s assume a scenario in which the end-customer has to installations: a development and a production system. In this case, a license with 2 devices is necessary. The end-customer can use the master license key for both installations or one device license key for every installation.
Let’s assume a video or music streaming service, whose vendor wants to avoid shared accounts. With SLASCONE the vendor can set the number of allowed devices to 3, preventing a 4th device from using the service.
In order to avoid a poor customer experience resulting from such a ‘hard-cut’, SLASCONE introduces ‘soft’ limits with Goodwill devices. In our example, the vendor can switch from 3 to 3 + 1 (Goodwill) devices. Goodwill devices constitute a ‘yellow zone’, in which the client is under-licensed but can still use the software. SLASCONE provides a quick overview/analysis of activated Goodwill devices, enabling vendors to react e.g., by issuing a warning after the activation of a Goodwill device or by emailing affected customers.
In a typical scenario, vendors use the expiration date to prevent a perpetual usage of the software. However there are cases in which the customer is allowed to perpetually use software Version X, but not Version X+1. In order to address such scenarios, SLASCONE licenses carry an optional maximum software release information, which indicates the latest purchased version. Once an installation is upgraded to a not purchased version, SLASCONE returns a corresponding warning/error.
SLASCONE’s algorithms consider major versions, minor versions and revisions. If for example the license has a software release limitation 22.1, then the following applies:
- 21.0 compliant (can be activated)
- 21.3 compliant (can be activated)
- 22.0 compliant (can be activated)
- 22.1 compliant (can be activated)
- 22.1.5 compliant (can be activated)
- 22.2 non compliant (can not be activated)
- 23.0 non compliant (can not be activated)
- 23.1.5 non compliant (can not be activated)
- Custom Date
- Days after activation