Import/Export

It is important to backup your database before importing data. Select Import to import an XML file into the Workflow Manager database. When the user selects import, the following message appears. Select an option and click OK.

Designer Users: This dialog will not appear if you're importing Workflow Manager CUs. This type of import does not support the Append Data option. CUs will be replaced in the geodatabase.

• Replace Existing Data: If you select this option, all existing data is deleted and the data in the selected .xml file imported.

  IMPORTANT: If Replace Existing Data is selected when importing users who already exist in Workflow Manager, this deletes those users and recreates them with new user IDs. This also disassociates them from any design data they may own. In this case use Append Data instead to preserve their user IDs.

• Append Data: If you select this option, any items that exist in the selected .xml but not in the existing data, will be added. For example, if a task exists in both the current data and the .xml, it will not be appended, regardless of whether they have different subtasks.

Items added during an append are not assigned as well. For example, if a subtask is added, it will appear as an available subtask in the Process Framework Administration tool and is available to be assigned to a task. It will NOT be automatically assigned to an existing task.

Process Framework will not allow the user to import information specific to Workflow Manager (e.g., CUs) into a database that supports only the Session Manager extension. 

Select Export to create an XML file containing the selection information. Select an export option (or multiple options) and click Export.

• Process Framework Workflow: Select this checkbox to export all information associated with your workflow (e.g., node types, roles, states, filters, tasks, subtasks, etc.). This option also exports how these nodes are related (e.g., the roles assigned to each state). If you have both Session Manager and Workflow Manager installed, a dialog will ask you to select the extension you wish to export. If you click Cancel on this dialog, only the workflow export will be cancelled.

• Users: Select this checkbox to export user information such as user name, display name, description, and assigned roles. This Export option allows you to select from a list of users in the database or export information for all users.

• Workflow Manager CUs: Select this checkbox to export CUs from your Workflow Manager database (e.g., WorkflowManager.mdb). CUs are exported from the MM_WMS_COMPATIBLE_UNIT_LIBRARY table. This option is available only if you have Designer/Workflow Manager installed.

You may assign an XSL style sheet to your exported XML file. Select the "Apply XSL Style Sheet" checkbox and browse to the style sheet. A list of sample XML style sheets provided with the ArcFM Solution install is available in the Appendix.

See the help topic XML Style Sheets.

Click Cancel to stop an import or export. All import changes will be rolled back. Export does not change anything, so no rollback is performed. Log results are displayed in the window on the right and can be saved to a .txt file using the Save log button.

The following are cases in which all information does not get exported:

• From the Configuration tab, FullDBlock is not exported.

• From the Roles tab, if the Extension listed does not exist, then the Role is not exported.

• From the States tab, if the Node Type listed does not exist, then the State is not exported.

• For State Roles, if the State does not exist or the Role no longer exists, the State Role is not exported.

• When exporting Transition From State information, if there is no To State transition, the Transition From State information and the Transition Role(s) associated with this transition will not be output. Similarly, when exporting To State information, if there is no From State transition, the Transition To information and the Transition Role(s) associated with this transition will not be output.

• For both transitions, if the State no longer exists, the transition will not be exported.

• If the Role no longer exists, the Transition Role will not be exported.

• A Transition will not be exported if the Node Type no longer exists.

• A Filter will not be exported if its associated State no longer exists.

• For Filter Roles, if the Filter does not exist or the Role no longer exists, the Filter Role is not exported.

• A Task will not be exported if the Node Type no longer exists.

• For Task Roles, if the Task does not exist or the Role no longer exists, the Task Role is not exported.

• For Subtasks, if the Task does not exist, the Subtask will not be exported.

• For Subtask Parameters, if the Subtask does not exist, the Subtask Parameter is not exported.

• For Messaging Roles, if the Message does not exist or the Role no longer exists, the Messaging Role is not exported.

• USER_IDs are not included in the export.

  • For more, see the myArcFM article FAQ - Designer - Is USER_ID Preserved in the Export of Workflow Manager Users?