Purpose: The purpose of this document is to discuss the use of session locking and how it affects the application when the current user is changed when the session locks.
Session Locking
Session locking allows the application to be "locked" to require the user to re-authenticate to continue use of the application. Session locking also allows the logged in user to be quickly switched, without closing and restarting the application. When a user re-authenticates, his/her permissions are re-evaluated from the database, causing objects to which the user does not have access to be hidden or restricted, this includes forms, fields, etc.
Locked Forms
When an application is locked and a different user than the previous one logs back into the system, the new user might not have permission to view all of the forms that are currently open within the application. For each form that the new user does not have permission to view, a "form lock panel" is superimposed over the form to prevent the new user from having access to the already opened forms.
The locked forms and the entire application are prevented from being closed so that information is not lost if the previous user had unsaved changes on a locked. A user with sufficient privileges to view the form must first log into the system to close the forms before the application can be closed.
