Repository Guide

10.5
- 10.5.7
- 10.5.6
- 10.5.4
- 10.5.1
- 10.4.0

Back Next

Understanding Repository Object Locks

The repository uses locks to prevent users from duplicating or overwriting work.

The Repository Service creates the following types of locks on repository objects when you view, edit, or run them in a workflow:

In-use lock. Placed on objects you want to view.

Write-intent lock. Placed on objects you want to modify.

Execute lock. Locks objects you want to run, such as workflows and sessions.

The Repository Service creates and releases locks on repository objects. The repository allows multiple users to obtain in-use locks on an object. The repository allows one write-intent lock per object. This keeps multiple users from editing the object at one time, thus preventing repository inconsistencies. If you attempt to modify an object that already has a write-intent lock, the repository displays a message box:

The [object_type] [object_name] is already locked by [user name].

The repository then issues an in-use lock for the object, allowing you to view the object.

The repository allows one execute lock per object. This keeps you from starting a workflow that is already running, which can cause the Integration Service to load duplicate or inaccurate data.

The following table lists each repository lock and the conditions that create it:

Repository Lock	Created When	Maximum per Object
In-use	Viewing an object in a folder for which you do not have write permission. Viewing an object that is already write-locked. Exporting an object.	Unlimited
Write-intent	Viewing an object in a folder for which you have write permission. Editing an object in a folder for which you have write permission. Importing an object.	1
Execute	Starting, aborting, or recovering a workflow.	1