Consuming Executions
One of the license types that you can define for a Feature is Execution Count. A license of this type contains a pool of executions from which the Feature consumes one or more executions as the protected application runs.
A typical use for this type of license is to assign a different "cost" in executions for the different functions that an application can perform. All the executions are consumed from a single pool of executions in the license. For example, the customer could be charged one execution for a save operation and three execution for a print operation. This provides an alternative to the method of assigning a different Feature ID and providing a separate executions pool for each action. With different Feature IDs, the customer might deplete all the executions for one Feature while unused executions remain for other Features.
You can assign a cost in executions for a given Feature by using <execution_count_to_consume> in the login scope for the protection key. This tag should state the number of executions to consume for a single login.