Working with Applications › Applications › Application Versions › Application Locking and Unlocking

Application Locking and Unlocking

The server manages concurrent updates to an Application. Sometimes collisions can occur if two users try to upload the same Application around the same time.

Example: Management of Concurrent Updates to an Application

• On machine X, user SCHEDMASTER downloads Application APPL1.
• On machine Y, user GURU downloads Application APPL1 also.
• SCHEDMASTER updates and uploads APPL1.
• GURU updates and tries to upload APPL1. The upload fails because SCHEDMASTER uploaded the Application after GURU downloaded it.

When collisions such as the above occur, the server provides the following recovery options:

• GURU can force an upload without considering the changes made by SCHEDMASTER. With this option, APPL1 contains only the changes made by GURU.
• GURU can download the Application version uploaded by SCHEDMASTER, update the Application, and retry to upload. With this option, APPL1 contains the changes made by both GURU and SCHEDMASTER.
• GURU can abandon the upload. With this option, APPL1 contains only the changes made by SCHEDMASTER.

When you lock an Application, other users (with different user IDs) cannot automatically update and upload the Application until you manually unlock the Application. If a collision occurs, the same recovery options as in the example apply.

More information:

Lock an Application

Unlock an Application