Importing Workflow Templates
From the workflow Templates table, select > .
You can import multiple templates at a time. A JAR or ZIP file can include multiple XML files each representing a unique workflow template, and a single XML file can represent multiple unique workflows.
 |
The layout of the XML is determined using a DTD file:
<Windchill>/loadXMLfiles/standard<version>.dtd
This file contains all the XML tags for objects supported for import and export functionality. For more information about importing and exporting, see When to Use LoadFromFile and Import/Export.
|
Errors When Importing
Some errors result in messages displayed, others might be fatal. Check the method server log for error information.
The following factors are not allowed or might cause the import operation to fail:
• A template references underlying objects, such as participants and roles. If the underlying objects do not exist in the database, the import fails.
• Iterations of a workflow template are not imported.
• If your exported workflow template contains a reference to a group, the group name in the target location must match the source group name exactly. If the name does not match, the import fails.
• Importing and exporting across releases is disabled by default.
|
|
If you export a workflow template and re-import it into the same system, a new iteration is created. If you do not want to create a new iteration, you must delete or rename the original before you import the template.
|
Properties That Affect Import Functionality
The following properties affect the import functionality for workflow templates:
wt.ixb.import.allowCrossReleaseImport
Set this property to true to allow importing workflow templates across releases.
You can import a template into a later version of Windchill, but not to an earlier version. The import and export functionality is not backward compatible.
wt.workflow.IterateOnImport
This property determines how to handle situations in which a workflow template is imported to a context that already has a template of the same name.
If set to true, the imported template is appended to the existing template as a new iteration.
If set to false, the imported file causes a method server exception and the operation fails.
wt.workflow.templates.import.useTargetGroup
If your exported workflow template contains a reference to a group, the group name in the target location must match the source group name exactly. If the name does not match, the import fails. If the import is successful, the template refers to the group in the target context.
If you want the workflow template to refer to the group in the source context instead, set this property to false.
This property only applies when importing and exporting within the same Windchill system.