Exporting Workflow Templates
Exporting workflow templates creates objects in XML file format and stores it in a JAR or ZIP file. You can select multiple workflow templates to export at the same time.
Typically, you export one or more workflow templates to a JAR file. The JAR has one XML file representing all templates exported. You modify the XML files as needed and then import them to a different database.
1. From the workflow Templates table, select one or more templates and then select > .
2. Provide a name for the export file. When entering the name, ensure you include either a .zip or .jar extension.
3. Save the file to your local machine.
Errors When Exporting
 |
Review Errors When Importing and Properties That Affect Import Functionality before exporting the template
|
The following factors might cause the export operation to fail, or create errors when attempting to import the workflow back into Windchill.
• When you export a workflow template with references to other workflow processes (subprocesses), you have to manually manage the export. If the export is not properly managed, the import fails. The lowest level subprocess should be exported first, then import the parent processes, one at a time, into the same XML file. This sequence ensures that a subprocess is imported before a reference to that subprocess is imported in a parent template.
• When you export a workflow that contains a fixed reference to a specific iteration that is not the latest iteration, the import fails. You should modify all fixed references to floating references (that is, references to the latest iteration) before you export the workflow template.
• If you export a workflow template that is checked out, you must check it back in or undo checkout before you can re-import it into the same system.
• Do not export data from one version of Windchill and import it into a different version. Instead, migrate the data in your database and then export the templates.
• Ensure that all underlying objects referenced in the XML file representation of the workflow template exist in the target system.
An exported workflow template contains references to related objects such as participants and roles, but the underlying objects themselves are not exported. When subsequently importing the workflow template, the underlying objects must exist in the database or the import fails. This can occur especially when importing the object into a different system where the underlying objects might not exist or their system identifiers may be different.