Page History

When toggled on, the maximum amount of time (in seconds) that the application is allowed to be idle (the user is not actively using the application), after which the License Harvesting procedure will begin for that application.

You may either type the number of seconds, or use the increase/decrease arrows to adjust the number of seconds. 

When toggled on, the maximum percentage that the CPU activity is allowed to drop down during the specified duration (in seconds), after which the License Harvesting procedure will begin for that application.

Days

Days of the week that the application is available for use. For example, if you want to exclude weekend days from the times that the application can be used, you would toggle off Saturday and Sunday.

Hours

Time range (24-hour clock) that the application is available for use. For example, if you want to limit the hours of usage from 7 a.m. to 7 p.m., you would enter From: 07:00 To: 19:00.

You may either type the time or select it from the drop-down list.

When toggled on, when License Harvesting detects that the application is in an idle state, a confirmation message will be sent to the end-user asking them to confirm closing the application.

When this option is not toggled on, the application will be closed immediately with no alert to the end-user.

This option may be toggled on only when Confirmation Required has been toggled on.

When this option is toggled on, it sets the time (in seconds) to display the confirmation message to the user, after which License Harvesting will automatically close or suspend the application.

When this option is not toggled on, the user confirmation alert will remain on the end-user's machine until the end-user dismisses the alert.

Toggle to select the desired release method to use when releasing the application license due to idle state detection. Release methods include the following:

• The Dry Run method gathers information about application usage, and optionally, issues an alert to the end-user, informing them that the application is idle and recommending that the user close it. Regardless of the user action, all application events are reported so the administrator knows the history of the application's usage.
• The Graceful method asks the application to close, but allows the application to wait and remain open if there is user action required to resolve unsaved state questions or confirmations.
• The Force method immediately closes the application and ignores any unsaved state questions or confirmations.
• The Suspend method "freezes" the application so it can be released to the license pool. Although the application cannot be used while suspended, it remains visible to the end user, and no unsaved data is lost. You can unsuspend the application at any time. See Setting up Suspend mode for information on requirements for using Suspend mode.

Applies only when using Graceful release method.

When toggled on, the time (in seconds) to wait for unsaved state questions or confirmations to be resolved, after which the application will be forced to close.

When not toggled on, the application will remain open indefinitely if there are unsaved state questions or confirmations needed.