By default, the changes to documents that reside in a project folder and that are under change by a user in their local workspace are uploaded to the vault automatically by their own workflows. This happens independent of the project workflow unless there are Interlocks configured. But if your business process requires that document changes be uploaded at a specific project workflow transition, the transition can be configured to do so automatically so that users don't have to upload the files manually.
Use this option with care. Documents that are simultaneously locked and downloaded to a different user's local workspace while the synchronization is processing are not detected and the transition will succeed.
The transition will:
-
Upload to the vault any changed files from the user's local workspace who executes the transition
-
Unlocks any documents that are locked by that user
Keep in mind:
-
The transition may fail if some documents are locked by a user other than the one executing the transition.
-
This option is supported only when a site cache is connected.
-
Only documents in the project folder are synchronized to the vault and unlocked, not any references that reside outside the project folder.
To enable local workspace unlocking:
-
In Configurator, expand Workflow Definitions in the configuration tree and select the workflow definition you want to edit.
Its property pages appear in the right pane.
-
Click the States tab to display the current workflow.
-
Click Edit.
-
Double-click the transition the transition that you want to configure.
The transition's Properties page appears.
-
On the Document Control tab, click options or type values using the descriptions in the following table.
-
Click OK.
The Properties dialog closes.
-
Click OK.
| Option | Description |
|---|---|
|
Unlock all project documents from local workspace |
Enable this option to upload changed files from the local workspace of the user who is executing the transition. |
