Locking Files

You need to lock version-controlled projects and other Flow Service work files before you can edit them. You can also follow a lock-edit-unlock workflow with other work files.

To Lock Files

In the tree pane or file pane, you can select files and folders and do one of the following:

• In the version control toolbar, click .
• Right-click a file or folder and click Lock in the Version Control menu.
• In the main menu, click Version Control > Lock.

In the confirmation dialog that's displayed, you can do the following:

• Select and clear files to be locked.
• Optionally, type a message to explain the reason for the lock.
• Select the option to steal a lock.

Using Locks

You can use locks to temporarily prevent other users from publishing changes to a project so you can commit a change without causing conflicts. After you commit, the lock's removed.

Getting the Status

After you lock a file, the file status icon of the item changes from (read only) to (lock).

Checking the Lock Message

You can check for modifications to see lock messages.

Configuring Files to Require a Lock

You can use locks with other work files, for example, files that teams can't edit simultaneously, such as graphics. Specify the file types that require locks in the version control settings for a Flow Service user:

1. In the management console, go to the Tools > Account page, select the user, and click Edit in the Version Control section.
2. In the Lock Required box, use file patterns to specify the files by the file type. The default value specifies the Flow Service file types: *.xfp;*.xmp;*.xvar;*.xsf.

Stealing Locks

You can select the option to steal another user's lock to lock a file, removing the current lock and relocking the file in one atomic step.