Form and Workflow artifact versioning and package updates
- Last UpdatedSep 30, 2025
- 2 minute read
The default behavior of versioned artifacts—forms and workflows—is configured to be published as the next major version. For example, if version 2 of a form already exists, installing version 3 of the MES Model-Driven application content package will cause version 3 of that form to be automatically published. Version 3 of the artifacts will be referenced and used during design and run time.
When installing a new version of the package, you can choose the following versioning options for each versioned artifact:
-
Publish the versioned artifacts as a minor version.
-
Publish the versioned artifacts as Drafts, in which case the artifacts are installed but not published. You can publish the artifacts later when you are ready to use the new version of them.
You can edit a versioned artifacts installation settings from the Edit Package page (on the Manage Package page, select the package and click Edit). The Install Form (or Workflow) as Draft and Form Exists: Install as next minor version options are highlighted in the following figure.

You can edit the settings of multiple forms or workflows at the same time: Multi-select the forms or workflows and then change the settings. The changes will be applied to all selected forms or workflows. If you select only one form or workflow, make sure that you set Inherit Artifact Type Settings to No.
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.
Note: When updating packages, a warning or error message might appear in the Work tasks installation window as well as error in the SMC. The error relates to duplicated folders used by multiple packages and indicates the following condition: Folder title is not unique or it contains special characters like [\\,*,/,\",<,>,|,\',{,},?,:]. These messages do not affect the functionality of packaged features.