Difference between revisions of "SYSCLS EXCLUSIVE ACCESS"
(One intermediate revision by one other user not shown) | |||
Line 27: | Line 27: | ||
{{Category/Version|3.6.2}} | {{Category/Version|3.6.2}} | ||
+ | |||
+ | ==See also== | ||
+ | * [[Exclusive_Access_Content_(Client)]] | ||
[[Category:3.6.2|SYCLS EXCLUSIVE ACCESS]] | [[Category:3.6.2|SYCLS EXCLUSIVE ACCESS]] |
Latest revision as of 06:53, 28 October 2024
Classifies an object as Exclusive - Access - Object which means the object is locked (on the client) until it is checked out by one user. Once it is checked out it can only be edited by this user. The object stays locked for all others until it is released again. This classification is an Autonomous Classification where the defined properties are autonomously added to the ACM/MetaDefinitions.
MetaProperties
Name | Data type | Comment |
---|---|---|
ENABLED | Boolean | Indicates whether the object supports to be checked out (based on the underlying business case /workflow). It does not indicate whether it is currently checked out. |
CHECKOUT_TS | Date/Time | If the object is checked out, this property provides the time it was checked out. If this property is null, the object is NOT checked out. |
CHECKOUT_USER_ID | Guid | If the object is checked out, this property provides the UID of the user who has checked out the object. If this property is null, the object is NOT checked out. |