-
Question
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
You can use more than one licensing model in your product, to define licensing configuration tailored to your product and business model. Validation result for the given customer will return details for all configured models. <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:netlicensing xmlns="http://www.w3.org/2000/09/xmldsig#" xmlns:ns2="http://netlicensing.labs64.com/schema/context" ttl="2021-05-11T11:07:41.381Z">
<ns2:infos/>
<ns2:items>
<ns2:item type="ProductModuleValidation">
<ns2:property name="productModuleNumber">MYJXCMWZA</ns2:property>
<ns2:property name="valid">true</ns2:property>
<ns2:property name="expires">2021-05-16T00:00:00Z</ns2:property>
<ns2:property name="productModuleName">ABO</ns2:property>
<ns2:property name="licensingModel">Subscription</ns2:property>
</ns2:item>
<ns2:item type="ProductModuleValidation">
<ns2:property name="productModuleNumber">MG4YWDFEW</ns2:property>
<ns2:property name="productModuleName">Features</ns2:property>
<ns2:property name="licensingModel">MultiFeature</ns2:property>
<ns2:list name="FEAT-02">
<ns2:property name="valid">true</ns2:property>
<ns2:property name="featureName">Feature Two</ns2:property>
</ns2:list>
<ns2:list name="FEAT-01">
<ns2:property name="valid">false</ns2:property>
<ns2:property name="featureName">Feature One</ns2:property>
</ns2:list>
</ns2:item>
</ns2:items>
</ns2:netlicensing> |
Beta Was this translation helpful? Give feedback.
You can use more than one licensing model in your product, to define licensing configuration tailored to your product and business model.
To do so you need to add different modules to your product, each of them will be configured using a specific licensing model, e.g. Subscription or Multi-Feature.
Validation result for the given customer will return details for all configured models.