Changes

LOCKED OBJECTS

90 bytes removed, 14:01, 31 May 2023
In UBIK objects can be locked for multiple reasons, these different types of locking are discussed in this article.
----
== Locking for system reasons ==
Objects may be globally locked by the system to ensure consistency and stability.
=== Locked during initialization ===
During initialization objects are locked to prevent objects from being edited before their latest state is loaded.
 
== Locking in MRO tasks ==
=== Locked by [[MRO_Objects_(Client)#Locking|hierarchy]] ===
=== Locked by [[MRO_Objects_(Client)#Sequential_Task|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 [[User_Rights|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.
201
edits