The License Code Prefix feature of software_DNA provides an easy way to indicate to which product,
options or variant, a license code applies to. For example:
You offer multiple products (i.e. executables) and use a different PREFIX for each product as a convenient identifier for your
License Codes.
You offer multiple "versions" of functionality (ex: "Standard" version and
"Pro" version), offered at different
prices on your store-front, yet running from the same
executable.
You offer different License schemes such as Multi-Computers of 1, 2 and 3 on your store-front, at different
prices, yet still running from the same executable.
You have "Resellers" to which you each assign a PREFIX, and provide them with "Restricted Access"
to your DNA Control Panel to view / manage licenses with the assigned PREFIX
See Restricted User Permissions
When offering multiple product options / variants that use the same executable, the License Code Prefix will allow your application to identify which version to run and which features to turn
on or off.
When using the PREFIX feature, the License Activation Code (or Evaluation Code)
takes on the following format:
<Prefix><random_code>
<Prefix> |
1-4 alphanumeric label that you define
|
<Random Code> |
a 12 to 20 numeric or alphanumeric random series of digits
that identifies a specific licence. It is important that this be a random series of digits, and the longer
alphanumeric sequence is recommended
|
Setting the PREFIX
You can set the value of the PREFIX in the following ways:
| Product Configuration |
You can set a DEFAULT setting for the PREFIX that will be used by
default when a License Code is generated by software_DNA
See How to Generate Codes
for details on how License Codes can be created / generated
|
| eCommerce Connector |
In the eCommerce Connector configuration, you can override this DEFAULT setting for specific SKU’s
received via eCommerce transactions.
See eCommerce Connectors
|
| License Code Generator |
When generating License Codes using the software_DNA Code Generator, you can override this DEFAULT setting
for a specific batch of License Codes.
See Generating License Codes
|
You define the PREFIX as required. Some examples:
- "P" = Pro Version
- "S" = Standard Version
- "PA3-" = 3 permitted activations
- "P3" = Pro Version with 3 permitted activations
- "OFL" = Version that will be activated using the Offline Activation process
- "P1-" = a License Code for my Product P1
NOTE
If you are using the RAPID or CLASSIC Activation approaches, make sure that the PREFIX used by the different
products are of the same length as you will need to extract the PREFIX from the License Code in your App.
Using the PREFIX or the <License_Data> Custom Field
The <License_Data> Custom Field, with up to 2,048 characters, can provide more detailed
information to your Application than the PREFIX, and, contrary to the PREFIX, it can be udpated over the lifetime of the License Code.
This allows you to offer feature / option upgrades to your customers by updating the <License_Data>
field. Your Application can then use this information to offer the features / options purchased by your customer.
If you offer simple variants to your products, the PREFIX feature is likely appropriate for your products. For complex,
feature-based Licensing scenarios, using the <License_Data> field may be appropriate.
You can use both the PREFIX and the <license_data> Custom Field for more complex licensing schemes.
Contact our Tech Support for guidance and recommendations.
When to use multiple DNA Products and PREFIX
You would use multiple DNA Products with different PREFIX if each PREFIX corresponds to a different licensing strategy
(i.e. different DNA Product configuration). Some examples to illustrate this:
One(1) DNA Product
Multiple PREFIX |
You offer a "Standard" and a "PRO" version with different features, but all Licenses
are Single-User / 2-Computer licenses.
|
Two(2) DNA Product
Multiple PREFIX |
You offer two variants of your Application (priced differently):
- a Single-User / 1-Computer License with PREFIX "SU"
- a Single-User / 2-Computer License with PREFIX "SU2"
Because the License settings are different, you would need two DNA Products, each with its respective
PREFIX setting.
|
Two(2) DNA Product
Multiple PREFIX |
You offer two variants of your Application:
- a Single-User / 2-Computer License with PREFIX "SU2"
- a Multi-User License (which can support "x" seats)
with PREFIX "MU"
Because the License settings are different, you would need two DNA Products, each with its respective
PREFIX setting.
|
In situations where you need multiple DNA Products, you will have a distinct <Product Key> and
distinct lists of License Activation and Evaluation Code for each DNA Product.
In your Application, you will need to include the different <Product Key>’s of each version you
want to support, and your Application can decide which <Product Key> to use based on the PREFIX
of the License Activation Code.
See Implementing PREFIX option in code
for more information.