About Locking and Unlocking

A lock on an object prevents others users from making modifications. You must have read/write access to a simulation object to lock and unlock it.

You can lock the following simulation objects:

  • Simulation processes
  • Simulation activities
  • Attribute groups
  • Folders, documents, and files

A locked simulation object cannot be modified by other users. When you lock a simulation process, Process Composer for Dashboard also locks its simulation activities. You can unlock an object that you locked, but you cannot unlock an object that was locked by another person.

Process Composer for Dashboard automatically locks a file when you check out the document in which it is stored. The lock prevents other users from modifying the file and assumes that you intend to change the file and update it back into the database. Other people can view the locked file, but they cannot edit it or check in a new version. Process Composer for Dashboard does not lock documents that you download.

Process Composer for Dashboard automatically unlocks a file when you check in a new version. Alternatively, if you know that you will not be modifying a file or checking it back in, you can unlock a locked file and make it available to other people.

The icon in the Remarks column of the table page indicates that an item is locked.

When you lock a checked-in file, Process Composer for Dashboard locks the document containing the file. Hence, when you lock a file that was checked into a document containing versioned files, Process Composer for Dashboard locks only the subdocument containing the file. However, when you lock a file that was checked into a document containing nonversioned files, Process Composer for Dashboard locks the document containing the file and consequently all of the files inside the document are locked.

exhibits similar differences in behavior when you unlock a file in a document containing versioned or nonversioned files.