Locking
When Amount Keying operators key transactions, the transactions are first locked for the user ID that accesses them. Automatic lock management prevents situations where transactions become locked to a user ID and never handled because the user does not key the transactions in a timely manner, possibly because of a system crash. The automatic behavior for these locked transactions may cause unexpected results if an operator did not complete keying for a transaction that was automatically unlocked.
- A user receives a list of transactions to key and does not complete the keying before the session times out. When the browser session times out, all transactions locked by the user are released for other users to key. The pending transactions for the user are automatically finalized after a session times out.
- A user receives a list of transactions to key and begins working in another area of the Control Center. Since the Control Center is in use, the session does not time out. A separate lock timeout, specified in the Expiration Time property, may expire and release the transactions with old locks for other users to key. The pending transactions for the user are automatically finalized when the lock timeout occurs.
- A user receives a list of transactions to key and logs out before keying them. In this situation, the transactions are released automatically as part of the log out processing. The pending transactions for the user are automatically finalized after logging out.
- An administrator deactivates the priority control configuration while users are keying transactions. All
transactions for all users are immediately unlocked.
When priority control configuration activation occurs, transactions can be retrieved using the get more items button. All pending transactions for all users are returned to the new state when a priority control configuration is reactivated. The reason this occurs is because when the active priority control configuration is deactivated, it is handled as a stop all activity event.