Map Vault and Fusion Manage states
Configure state mapping to synchronize lifecycle states between Vault and Fusion Manage. State mappings ensure that when an Item changes state in Vault, the corresponding Item in Fusion Manage updates to the mapped workflow state.
Access the Vault Connector configuration dialog:
Navigate to Tools > Administration > Vault Settings, then select the Collaborate tab and click Configure in the Vault Connector Management section.
Navigate to the State Mappings tab:
In the Vault Connector configuration dialog, click the State Mappings tab.
(Optional) Configure Fusion Manage state transition behavior:
- Select the Use FM state transitions checkbox to enable automatic state transitions in Fusion Manage.
- When enabled, state changes follow the workflow transitions defined in Fusion Manage.
- From the From and To dropdowns, specify the allowed state transitions.
Add a new state mapping:
From the Vault State dropdown, select the Vault lifecycle state or file state.
From the Fusion Manage State dropdown, select the corresponding workflow state in Fusion Manage.
Click the Add button.
The mapping displays in the state mapping table with columns showing Vault State, Fusion Manage State, and Entity Type.
(Optional) Remove a state mapping:
- Select the row in the state mapping table that you want to remove.
- Click the Remove button.
(Optional) Replace an existing state mapping:
- Select the row in the state mapping table that you want to modify.
- Update the state selections in the dropdowns.
- Click the Replace button.
Save the state mapping configuration:
Click Apply to save your configuration.
The Vault Connector now synchronizes state changes between Vault and Fusion Manage based on your configured mappings.
State mapping errors
If you change the tenant or workspace after configuring state mappings, a warning dialog displays with options to keep or remove your previous mappings. If you choose to keep mappings and states are missing in the new configuration, an error dialog displays with details about:
- Affected mappings that reference missing states
- Specific reasons for each error (missing lifecycle definition, missing item state, or missing file state)
Missing state mappings are automatically removed from the configuration.
