Hello Oleg,
Thanks for the response.
Please be informed that "periodic background check" looks for the presence of license key on the system but not for its validity.
Hence even though the license got expired, background check would still not interrupt the session as the same key ID is still present.
The license manager restart (as well as system reboot) or re-insertion of the key are the parameters where the license expiration could be detected.
License expiration is not detected in a live session as this may abruptly freeze the execution of the application and user would not be able to save program/application data.
However, if there is a requirement to implement periodic check on expiration then way may have to programmatically design the same using hasp_login() API.
In this, we would require the program to call for login - logout on a fixed definite interval.
Hope this explanation helps our concern. Please feel free to write if any further detail may be needed.
Regards,
Parth
Thanks for the response.
Please be informed that "periodic background check" looks for the presence of license key on the system but not for its validity.
Hence even though the license got expired, background check would still not interrupt the session as the same key ID is still present.
The license manager restart (as well as system reboot) or re-insertion of the key are the parameters where the license expiration could be detected.
License expiration is not detected in a live session as this may abruptly freeze the execution of the application and user would not be able to save program/application data.
However, if there is a requirement to implement periodic check on expiration then way may have to programmatically design the same using hasp_login() API.
In this, we would require the program to call for login - logout on a fixed definite interval.
Hope this explanation helps our concern. Please feel free to write if any further detail may be needed.
Regards,
Parth