Forms Association

You can package and deploy a form with its associated artifacts such as workflow (for Fill Form) from one environment or repository to another environment or repository using the Package feature in AVEVA Work Tasks.

When a form (associated to a workflow) is packaged, the following options are displayed in the Associated Workflow details section under the Settings window. The Associated Workflow details section is displayed only in the Install and the Update tabs. For other options, see Add Forms to Package Template.

Workflow Version

Example

Consider the following scenario:

Source Environment

• Form1 is associated to Workflow1.

• Workflow1 has versions 1, 2, 3 and 4 with version 1 published and versions 2, 3, and 4 in draft status.

Package Template

• Form1 associated to version 4 of Workflow1.

• Target version is not specified.

Target Environment

• Workflow1.

• Workflow1 has versions 1, 2, 3 and 4 with version 1 published and versions 2, 3, and 4 in draft status.

When the package is installed in the target environment, Form1 is created and version 1.1 of Workflow1 is created in Draft status as only version 1 of Workflow1 is published. Form1 is associated to version 1 of Workflow1 and not version 1.1 of Workflow1 as the version is in Draft status. You must publish the desired version of the workflow if you want the form to automatically associate to the latest version (that is the last published version) of the of workflow.

When the package is uninstalled from the target environment, the version 1.1 of Workflow1 is removed. However, Form1 is not removed as Form1 is associated to the next latest version of Workflow1.