Object Locking Service
- 12 Mar 2021
- 1 Minute to read
- Print
- DarkLight
Object Locking Service
- Updated on 12 Mar 2021
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Example Lab Article
While Example Lab projects are resources for public use, articles and assets are not actively maintained. Screenshots and features are from the specified version below. These references may become dated as new versions are released.
Overview
Example Lab Details | |
| Version | 6.14.0 |
| Root Folder | Example Lab - Object Lock Service |
| Modules | None |
| Dependencies | None |
This project demonstrates how the Object Lock Service can be leveraged to prevent users from editing an object at the same time.
Explanation
In this example, a 'Edit Case' user action has been fitted with steps from the Object Lock Service to check if the target entity is locked. If it is locked, the flow tells the initiating user that they cannot edit the item because it is locked by [email_address]. If the object is locked by the initiating user, the lock is broken and then locked again to refresh the lock's duration. The user is then able to make their changes, and the lock is released. There is also a 'Break Lock' user action that is only shown to the owner of the lock when the object is locked or administrators.
Reference Articles
Project Download
The examples attached were developed to be instructional and were not developed as officially supported components. For more information or to engage our service team to develop fully supported, production quality solutions, please contact services@decisions.com. Import the project below to a Decisions environment on version 6.14.0 or later using our Importing/Exporting article.
Was this article helpful?
