An intent-based lock prevents other developers from saving changes to the object. Occasionally, locks create conflicts between developers that require access to the same object.

For example, a developer locks an object before going on vacation. The lock creates a conflict for other developers that require access to the object. To resolve such conflicts, you can use a third-party tool to read employee work schedules, detect potential conflicts, and pass logic to infacmd commands that list the locked objects and unlock the objects if necessary.