Externalizing Expressions for a Workflow Template
Use the Externalize Expressions action to create a Java CLASS file in a specified location. In addition to expressions in the template, the CLASS file contains details about the workflow template such as the name, context, organization, and creator.
This action is available to members of the WorkflowAuthors, WorkflowAdministrators, and Administrators groups.
|
|
Only workflow templates that have expressions can be externalized.
|
1. From the right-click actions menu of a template, select Externalize Expressions.
The Externalize Expressions window opens.
2. Select one of the following options:
◦ Externalize latest iteration—Use this option if you want to modify only the latest iteration of the workflow template.
◦ Check out before externalize—It is not required to check out the workflow template prior to externalizing the expressions. However, it is recommended so you can undo your checkout if the updates you make are incorrect.
◦ Externalize all iterations—Use this option if you want to modify all iterations of the workflow template.
3. Specify the name for the package you are exporting. The name can have up to 200 characters.
4. Click OK.
If there is no syntax error in the expressions, the externalized file is compiled and a CLASS file is generated and saved. By default, the exported expressions are saved to the following location:
<Windchill>/codebase/ext/wt/workflow/externalize
A folder with the package name is also created under the <Windchill>/codebase/ext/wt/workflow directory.
|
|
If you make changes after externalizing, you must check in the modified workflow template and externalize the expressions again to view the changes.
Workflow templates that have been previously externalized can be externalized again, but a message appears indicating that the template has already been externalized.
|
