Custom License Fields
The metadata which can be added to products, licenses and users has following three properties:
Name of the metadata key.
Value of the metadata key.
Determines whether the metadata key/value is accessible in the app after trial or license activation.
This metadata can be added to products and can be accessed in your application once a trial or license is activated.
It can be used for storing some product-level information that you want to access in your app and this information can change over time.
This metadata can be added to your licenses at the time of creating a license. You can store additional data like
order_id, customer_id , feature1, feature2 etc. with the license.This can be accessed in your application once a license is activated. Its common use case is feature detection, i.e. if you wish to restrict the features in your application based on the value of metadata fields.
In order to require licenses to have specific metadata properties, set them in license policy requiredMetadataKeys field.
You can enforce the schema for metadata fields in the license policy too, so you don't have to manually create the fields every time you create a license. Just provide the field names as comma- separated strings e.g.
order_id, customer_id , feature1, feature2 etc. in the required metadata keys property of the license policy.This metadata can be added to your license users at the time of creating a user. You can store additional data like
phone_number, address etc. in the user metadata.This metadata can be added by your application at the time of activating the license.
It can be used to collect additional details from the machine on which license is activated, e.g. number of cpu cores, any custom data provided by user etc.
This metadata can be added by your application at the time of activating the trial.
It can be used to collect additional details from the machine on which trial is activated, e.g. number of cpu cores, any custom data provided by user etc.
Last modified 1yr ago