Get started with Model Driven MES development

This developer guides provides procedures and conceptual topics that enable you to extend your MES model-driven application content using web widgets to create custom applications from within Work Tasks. The following Work Tasks web widgets are provided with the MES model-driven application content installation files and are described in detail in this guide:

• Gantt

• Merge

• Split

• Information Card

• Progress Bar

• SPC Chart

In addition the MES model-driven application content includes the Work Task Grid and Hierarchy Selector widgets. For information about these widgets, refer to the Work Tasks help (https://help.aveva.com/worktasks/).

Note: This guide is intended for advanced users who are familiar with both Work Tasks and MES model-driven application content.

Implement security for the MES Web API

Before you begin developing custom applications using Work Tasks and MES model-driven application content, you have to configure authentication for the MES Web API. See Configure MES Web API authentication.

Using the MES Web API in workflows

For instructions about how to use the MES Web API in a custom workflow—such as adding an MES Web API activity, handling transactions, and getting error messages from a failed call—refer to "Using the MES Web API in a Workflow" in the MES Web API V3 Reference help.

MES Model-Driven workflows and Work Tasks quickflows

All MES model-driven workflows are Quickflow-compliant. This allows you to save any MES model‑driven workflow as a Quickflow.

To create and use a MES model‑driven Quickflow, you must first deploy the Quickflow engine. See "Deploy Quickflow" in the Work Tasks help (https://docs.aveva.com/).

Note: Once Quickflow is deployed, you can save existing MES model-driven workflows as Quickflows. However, they will be given a new name, and you must update the associated form to use the Quickflow workflow.

Use Work Tasks Web widgets with MES Model-Driven forms

Standard MES model-driven forms include several Work Tasks web widgets. You can use these widgets in your custom MES model-driven forms. See Web widgets provided with Model Driven MES.

Move a Work Tasks-MES configuration to another 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.

For details on how to move the configuration to other environments, see Move a Work Tasks-MES configuration to another environment.

Deprecated Split Control

Starting with MES Model-Driven Application Control version 6.0, the Split widget has replaced the Split control that was used with the Job Management package. The Split control has been deprecated and will not be available for use after Work Tasks 2020 U2.

For existing custom forms that use the Split control, you must replace it with the Split widget. See Split Control for legacy reference information about that control.