A Reset Expire Period Authorization Definition resets the used time for an expiring license to zero and the execution count to zero.

Once activated, the remaining time will be reset to the full expire period specified in the license (if any) and the execution count is set to zero. For example: If you define an expiring license that uses an expire period of 60 days as well as an execution limit of 100 times, and the user uses the program for 50 days, executing it 80 times, the remaining time left for your application before it expires is 10 days and 20 executions. If you then issue a Reset Expire Period Activation Code to that customer, as soon as they enter it and the ClientProtector processes it as valid - the remaining time left for the license will be reset to 60 days and the execution count will be reset to zero.

Note that all three types of expiration can be active at the same time (Hard Date, Expire Period, Execution Limit). A license expires whichever comes soonest. Be careful that you only use the type(s) of expiration you need, or else you will find that your licenses expire when you do not expect them to.

The Activation Code that is generated for a Reset Expire Period Authorization Definition does give you the option of using a Shelf-Life. The resulting Activation Code must be used within the shelf-life after the date it has been issued, or the code itself will expire and will cease to work. Note you can override the shelf-life you defined when you created the license at the time you generate an Activation Code with the Manual-Activator.

The Activation Code that is generated for a Reset Expire Period Authorization Definition is a "single-use" code by default. If single-use is enabled, generated Activation Codes can only be used once. However, note that you may reissue it to the same customer on another day, and the code will be different (due to the embedded shelf-life date) and therefore may be used by the customer. You have the option of turning off single-use when you define your license, but do not have the option of overriding it later.

Reset Expire Period Authorization Definitions do not require a parameter to be sent (explicitly or implicitly).

Reset Expire Period Authorization Definitions can be used as a payload for both types of Composite Authorization Definitions.

When To Use A Reset Expire Period Authorization Definition

Create a Reset Expire Period Authorization Definition if you have a license that you want to repeatedly expire. This is an excellent way to ensure that the customer stays up-to-date if they are required to pay you a periodic fee (monthly for example). Their license could be set to an expire period of 30 days. Every month, if they have paid their bill, you issue them a new Reset Expire Period Activation Code and their expire period is reset.

Create a Reset Expire Period Authorization Definition if you have a license that you want to repeatedly execute a limited number of times. This is an excellent way to implement pay-per-execution schemes. Their license could be set to an execution limit of 100 and every time they run out of executions, they pay for another 100, you issue them a new Reset Expire Period Activation Code and their execution count is reset to zero, allowing them to execute it another 100 times. Note that if you wish to implement pay-per-use of a specific feature (as opposed to pay-per-execution of the program) then you should instead use a General Use Authorization Definition.

More Information

For help in understanding expiring license features, see Expiring Licenses in this feature reference.

For help in actually creating a Reset Expire Period Authorization Definition, please see Authorization Definition Dialog in the SoftwareShield License Manager Reference.

For help in actually setting expiration in your licenses, see Expiration Tab in the SoftwareShield License Manager Reference.