On the Manage Topic Workflow Configurations page, you can export a topic workflow configuration using the Export link from the row menu (
). The exported topic workflow configuration can be imported into another application instance with the same topic schema version (as seen on the About page). This can be useful when developing the topic workflow configuration in a test environment and then loading it into a production environment.
You must have the Manage Topic Workflow Configurations permission to export the topic workflow configuration.
When you click Export, the selected topic workflow configuration is exported into a .dat file in XML format, which you can save on your local computer. By default, the file name is <Topic Workflow Configuration name>.dat.
The exported .dat file contains the following data:
Fields that include work team contexts are not exported.
A warning message appears if more than 5000 values have been defined for a field. If you proceed, the first 5000 values are exported based on their display order.
Recipient values that are exported can include Assigned User, Previous Assigned User and Work Team Members. Individual usernames are not included in the export.
The Topic Field Modified or Action Field Modified notification reasons that reference fields that include work team contexts are not exported. These fields can exist in the Message Subject and Message Text, however, because they will not be exported, they will not be populated when the email is sent on the imported side.
If a topic template contains populated topic or action fields, and these fields have a work team context, then the topic template is not exported.
The history of the topic template is not exported.