Skip to Content
Technical Articles

UI enhancements in 1705

Session Handling for Multiple Logon

How it works?

  • Log in to Device A with a user id A
  • Now open any record for example, open an Account and try to Edit any data
  • Now go to Device B and log in with the same user id
  • Once you enter the credentials and hit Logon you will get a pop up message as below

  • Here if you click on Yes, this will release the session which is locked in the Device A. Here in this example it will release the lock for the Account that is opened in the Device A
  • If you click No the instance (example: Account) in Device A will still be locked by the user id. In Device B if you try to open the same account, you will receive a message that it is locked by your user id.

Note1: This functionality does not end the log in session of Device A, this will just release the lock of the instances that are running in the Device A.

Note2: This functionality is across all UI’s like HTML5, Responsive UI and Extended Apps.

Note3: This functionality will work only with Normal Logon. Not with SSO.


Edit in parallel session

How it works?

Scenario: 1

  • Log in with a User A
  • Now open any record for example, open an Account and be in Edit mode
  • Consider User B, and open the same Account, and click on Edit, the below message will be shown

  •  So, this will not allow the second user to Edit the same record

Scenario: 2

  • Log in with User A
  • Now open any record for example, open an Account (not in edit mode right now)
  • Consider User B also opens the same account (not in edit mode right now)
  • Now User A clicks on Edit and made some changes to some fields and clicked on Save
  • For User B it will still show old data (changes done by User A is still not shown), as the account was opened by User B before the User A edited the record.
  • Now once User B clicks on Edit, it will refresh and updates the last change that is done by User A. This will help User B to work with the latest data.



You must be Logged on to comment or reply to a post.
  • thanks for this Vivek. can you provide any info on how this works if user A opens multiple browser sessions on device A using the same account? does the session release trigger in this instance?


    • Hi Dave,

      It works if the browser is different, like IE and chrome. If the same user logs in to chrome and IE it will trigger the pop up. This is with regards to Session Handling for Multiple Logon

      • thanks for clarifying Vivek.

        so, if a user had the same record open in either 2 separate tabs or 2 separate sessions in IE on the same device, would they encounter an unhandled record locking problem?

        • Sorry for the delay in response

          There are 2 different functionalities here one talks about session handling which will occur only if the same user logs in to different browser or different device at the same time.

          The other one is about locking mechanism of a particular record. The one you are referring to will fall under this. If user A opens an account for example and goes in edit mode , same user logs in to separate tab and when he opens the same account and clicks on edit the error will be shown that the object is locked by his own user id. But currently this locking mechanism is disabled as this resulted in issues with PDI logic. Development team are working on this again. So this might be available again in next release.