This feature allows storing encrypted data in the license file. The license file acts like a small database.
The data area could be used to store:
• | Program configuration parameters |
• | Usage of the application - like number of program starts or last online validation |
• | Additional customer information |
• | Other custom values you do not want to save in a configuration file or a database |
It works in the way that you use an ID and assign a text to this ID, e.g. ID = LastOnlineValidation, Text = 09/09/201.
There is a complete set of API commands to read and modify the data.
Command SetConfig. If the ID already exists, the existing value is updated with the new value.
Command GetConfig
Command DeleteConfig
Command ExistsConfig
Values can be preconfigured in the project template. They are added automatically to the license file
Example
<Configs>
<Config name="CustomerID" visible="no">D83726</Config>
<Config name="BasicConfiguration" visible="yes">This is a text</Config>
</Configs>
Do not store large data e.g. MIME-encoded binary data like images or movies as this would significantly slow down the access to the license file.