When a process is loaded
When a given process is selected and loaded in DPM:
- The selected process and all of its sub-processes are locked.
- All of the products and resources associated with the selected process are locked.
- Any parent of the loaded objects is not locked. However, since at least one of their children is locked, the parent cannot be deleted.
- The deletion of all of the links between the parents and children is locked.
- Any Work System Components associated to the loaded resources are not locked
When a process is closed
When a document is closed, all locked objects are unlocked.
- The selected process and all of its sub-processes are unlocked.
- All of the products, resources and links associated with the process are unlocked.
When a loaded process cannot be locked
When a process is loaded that is already locked by another user:
- The current V5 session will be in read-only mode.
- A Confirmation dialog is displayed to inform the user that the selected process is already locked. The user may then choose to open the selected process in read-only mode, or cancel the loading process.
-
If the user elects to load the selected process in read-only mode, no Save function will be available for the document.
When only some objects of a loaded process cannot be locked
When a process is loaded that is not already locked by another user, but shares objects (products, resources, child processes, etc.) with another process that is currently locked by another user:
- The current V5 session will be in read/write mode.
- Objects that can not be locked during the load of the process (because they were already locked by another user) will be in read-only mode. These objects may be modified during the current session, however the changes can not be saved.
-
A dialog box is displayed to inform the user of those objects that can not be locked.