Certain combinations of time limitations are not permitted when creating a license e.g. it does not make sense to set an Expiration Date and an Expiration Period at the same time. The former is set explicitly irrespective of when the license is actually activated, whereas the latter is used to calculate the Expiration Date based on an offset from the actual date of activation.
The Software Potential Portal guards against users setting incorrect combinations but when creating licenses using the Web Services API, the Software Potential service will throw an exception if invalid combinations are submitted in a license management CreateLicense or UpdateLicense request.
The following table indicates how to set the different combinations of the
License.LicenseInfo.Limitations.ExpirationPeriod properties when creating different types of time-limited licenses as well as perpetual/unlimited licenses. (All datetimes should be UTC.)
|Max Value / A Date||NULL (+)||Error (*)|
|Null (+)||Max Value /Number Of Days||Error (*)|
|A Date||Max Value /Number Of Days||Error (*)|
|A Date||-1||OK (Expiration Date Set)|
|Max Value||Number Of Days (e.g. 30)||OK (Expiration Days Set)|
|Max Value||Max Value||Unlimited Expiration|
(+) Null: if don’t populate the field with a value.
(*) Error: “LicenseInfo.Limitations.ExpirationDate and LicenseInfo.Limitations.ExpirationPeriod cannot both be set” will be returned as an error in Exception