Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Model Driven MES 7​.0

Set install options for Work Tasks Form and Workflow artifacts

Set install options for Work Tasks Form and Workflow artifacts

  • Last UpdatedOct 06, 2025
  • 2 minute read

Forms and workflows are versioned artifacts. By default, they will be imported and installed as the next major version within an existing repository and will be automatically published. However, you can change the update behavior using available install options.

You can apply global install options at the Forms and Workflows level in the Configuration tree of the Edit Package window, as shown below.

Work Task package installation settings.

You can also override the global Forms or Workflow install option settings for individual form and workflows, as shown below. The Inherit Artifact Type Settings option must be set to No.

Work Tasks recommended package installation settings.

For example, for forms:

  • The Form Exists options allow you to choose how to version the new artifact or to not install it.

  • The Install Form as Draft option allows you to install the artifact in Draft mode and not have it published automatically.

Note the following when updating forms and workflows:

  • If a form or workflow has been installed during a package update, you can roll back the active form or workflow to the previous version by unpublishing it.

  • If custom changes have been made to an existing form or workflow but you want to use the updated version, you will have to manually create the custom changes in the updated version.

  • For versioning, use either the Install as next major version or Install as next version options.

    • Install as next major version This option increments the version to the next major version. For example, 1 and 1.1 would both version to 2.

    • Install as next version This option increments the version to the next version at the same hierarchy level. For example, 1 would version to 2 and 1.1 would version to 1.2.

    • It is recommended that you not use Install as next minor version, which is the default. This option increments the version by adding another level to the version hierarchy. For example, 1 would version to 1.1 and 1.1 would version to 1.1.1. Subsequent versioning would cause the version number hierarchy to continue to expand.

For additional information, see Form and Workflow artifact versioning and package updates.

TitleResults for “How to create a CRG?”Also Available in