An Add Allowable Executions Authorization Definition adds a specific number of executions to the execution limit of an expiring license that uses execution limits.

Once activated, the Execution Limit of the license is changed to be equal to the old limit plus the number passed as a parameter.

The Activation Code that is generated for a Add Allowable Executions 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 Add Allowable Executions Authorization Definition is a "single-use" code by default. If single-use is enabled, they 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.

Add Allowable Executions Authorization Definitions do require a parameter to be sent (implicitly). The parameter will be the number of executions to add to the licenses Execution Limit. You may add between 1 and 65536 executions.

Add Allowable Executions Authorization Definitions can be used only as a payload for Design-Time Composite Authorization Definitions. They may not be used as a Run-Time payload.

When To Use An Add Allowable Executions Definition

Create an Add Allowable Executions Authorization Definition only if you have enabled expiration by using an execution limit for a specific license.

Create an Add Allowable Executions 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. The customers license could be set to an arbitrary execution limit. Every time they run out of executions, they pay for as many as they wish, you issue them a new Add Allowable Executions Activation Code with the correct parameter and their execution limit is set to the new value, allowing them to execute exactly as many times as they paid for it. 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 (including execution limits), see Expiring Licenses in this feature reference.

For help in actually creating an Add Allowable Executions Authorization Definition, please see Authorization Definition Dialog in the SoftwareShield License Manager Reference.

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