Evaluation version
Contents
Evaluation version per module / feature
The trial version is available per module / feature separately. It starts, when the prepareAndActivate or validate command is used.
Typical start screen for evaluation version.
Example
There are 2 modules. Each module has a trial version set to 30 days.
| • | User starts program for module A (validate is used). The trial period starts today |
| • | 2 weeks later, user starts program for module B. The trial period starts then and is valid for 30 days even if module A has already expired |
The trial version is configured in the project template using Days (recommended) or ValidUntilDay
Prolong a trial version
It is not possible to prolong a trial version. The only way is to reset the installation. Then the trial starts again.
To allow a new installation or make a new test from scratch, the following steps are required
| • | You need the System ID of the MAC or name of the computer |
| • | Delete the license file |
| • | On the Activation Server 4, search for this System ID of the MAC or name of the computer (TAB Home) |
| • | Click on the System ID and change the field: Maximum Key / ID Usage |
 |
| Change Maximum Key / ID usage |
If you do want to allow a reinstallation, you can change the default value 1 on the Activation Server 4 (Administration / Setup, Product Configuration).to a higher number.
After a license file download, the evaluation version starts again
No evaluation version (Serial Number needed to start the application)
If you do not want to offer an evaluation version, you have to change the value ValidUntilDay in the project template and set it to 1900-01-01. The first application start displays the screen, that a Serial Number is required.