Import MES Workflows to a production environment

Standard development practice calls for you to create MES workflows in a development environment for development and testing. Then when the workflows have been tested and verified to work properly, you can move them to the production environment.

Work Tasks allows you to create packages to move workflows from one environment to another. This is the preferred method for moving workflows. For example, this is how MES model-driven application content is installed.

For information about creating and importing workflow packages, see 'Packages' in the Work Tasks Developer documentation, available from the Work Tasks help (https://docs.aveva.com).

The only possible exception is if you are setting up a new MES production environment (for example, if you are setting up a production environment for the first time or due to a machine failure). In this case, you can move a Work Tasks configuration from a development environment to the new production environment. For detailed information, see Move a Work Tasks configuration to another environment.