Last update: 21 October 2022 (cf)
From Fabasoft Folio 2016, changes of objects always require an object lock by the method COOSYSTEM:ObjectLock. Changing of an object without lock will fail with an error.
In versions earlier to Folio 2016, the Fabasoft Folio Kernel applied an automatic lock when changing attributes without locking. This lead to an information in the log „Automatic lock for object ... set“ if the automatic lock was successful, or a warning „Automatic lock for object ... failed“ in case the automatic lock failed (e.g. when the object is already locked by another user).
The automatic locking feature was removed in Folio 2016 as this could lead to unexpected or unwanted behavior, especially in cases of an automatic lock failed, the current transaction was not aborted, meaning that the changes got committed even though the object might be locked by another user.
Therefore with Fabasoft Folio 2016 and above, explicit locking is absolutely essential before changing any object properties programmatically.
Changing objects without lock will fail with an error.