LOCKED OBJECTS
In UBIK objects can be locked for multiple reasons, these different types of locking are discussed in this article.
Contents
Locking in MRO tasks
Locked by hierarchy
By design, an MRO object is locked if its parent MRO work package is confirmed. This type of locking is applied recursively to all child MRO objects.
Locked by sequence
An MRO task can also be locked if it belongs to a sequential list of tasks that must be completed in order, in this case all tasks but the current one are locked.
Locking through access rights
Locked by exclusive access
Objects may have exclusive access, allowing only a single user to edit it by checking it out, for all other users this objects is locked and can not be edited.
Locked by user rights
If a user does not have the necessary right to write to, or even read the contents of an object this object appears locked. This can apply to groups of objects, single objects or even properties of objects.
Locking for other reasons
Locked during initialization
After login objects are locked to prevent objects from being edited before the session is fully initialized.
