|
|
Validate modules |
|
|
|
||
|
Validate modules |
|
|
|
|
Validate modules
|
|
|
Validate modules |
|
|
|
||
|
Validate modules |
|
|
|
|
Find below a summary of commands which allow to validate modules.
To use the following commands, the license file needs to be opened first with one of the Prepare commands. See - open a license file.
You can test a module using ValidateEX (recommended), Validate or ValidateAndDecrease. Additional options are:
| • | Retrieve the module type - GetVal, Token LTY. Module type is also delivered with GetModuleList |
| • | Retrieve module name - ModuleName. Module name is also delivered with GetModuleList |
| • | Retrieve status Demo version of a module (ValidateEx) |
| • | Retrieve time limitation of a module RemainingDays and/or ExpiredOn |
| • | Retrieve the number of days which have been set for the trial period - NoOfDays |
| • | Retrieve Activation Status of a module - GetWebActivation |
For modules which are from type user, PC, concurrent, Item counter you can
| • | Retrieve number of licenses and available licenses of a network module - TotalLicences and RemainingLicences. If the module is from type counter then you get the value of the counter with TotalLicences |
| • | Retrieve all entries / user / computer - GetEntriesOfModule |
| • | Deactivate an entry / user / computer - DeactivateEntry |
| • | Activate an entry / user / computer again - ActivateEntry |
| • | Delete all entries / users / computers - RemoveAllItems |
| • | Delete all deactivated entries / user / computer - RemoveDeactivated |
| • | Check if a specified entry / user / computer exists - ExistsEntry |
| • | Check if an entry / user / computer is in use or deactivated - IsEntryActivated |
Some other useful commands are:
| • | Retrieve the customer name (name typed in during registration) - GetCustomer |
| • | Save an Activation Key in the license file - ApplyActivationKey or ApplyInvisibleKey |
| • | In case you have a large number of modules a cache mode is available to read all modules |
You can also use EasyGo to test multiple modules. In this case you should use the module name in the Product Name to make it transparent for the user, e.g. CTI Data Connector – Module Database Profiles. This allows testing each module with time limitation and use Activation Keys per module.
If you have more than 5 modules you could deliver a customer specific license file - see license File with EasyGo