AVEVA™ Work Tasks Extension and Connector for MES 7.1

AVEVA Work Tasks Extension and Connector for MES 7.1 release notes

Save PDF

AVEVA Work Tasks Extension and Connector for MES 7.1 release notes

Save PDF

Last UpdatedApr 03, 2026
4 minute read

These release notes contain important information about AVEVA Work Tasks Extension and Connector for MES (Version 7.1).

Release notes from previous releases of Work Tasks Extension and Connector for MES are posted to the Products page of the Knowledge and Support Center. Once on the Products page, you can use the filter to list the MES documents, which include the release note files.

There are no plans for a future release of Work Tasks Connector / Extension for MES. For MES activities, use the MES Web API as done in Model Driven MES. For events, AVEVA will publish alternatives with the next release of MES.

Expectations and limitations

The following expectations and limitations should be considered for this release of AVEVA Work Tasks Extension and Connector for MES.

BigInt data type support

Because Work Tasks does not support the BigInt data type, MES APIs that use BigInt values convert them to the Double data type. Double supports integer values up to 2⁵³, whereas BigInt supports integer values up to 2⁶³.

New features and enhancements

This version of the Work Tasks Connector and Extension for MES supports MES 2023 R2 and Work Tasks 2023 R2.

This release is a compatibility release with no new functionality. There are changes to the product to support changes made in Work Tasks 2023 R2 that impact both the Connector and Extension code.

Resolved issues

The following issues were resolved in this release of AVEVA Work Tasks Extension and Connector for MES.

ID	Description
IMS 4089128	Decimal separator problem when calling MES activity from Workflow in Danish region.

Known issues

The following known issues were identified for this release of AVEVA Work Tasks Extension and Connector for MES.

ID	Description
Bug 4657590	After restarting the machine, the MES Workflow Connector service may not transition to Running or may fail to connect to MES. To resolve this issue, manually restart the Connector service after the MES Middleware Host service has started.
Bug 4676228	Workflow execution does not complete when an MES Transaction includes Wait-for-Event or Timer activities. After the wait activity, subsequent MES actions fail because the transaction resumes on a different execution thread. As a result, the workflow stops and later MES actions do not run. Avoid using wait-based activities in MES transactions.
Bug 4683046	After upgrading from MES 2023 (7.0) to MES 2023 R2 (7.1), legacy workflows that use MES-Wait-for-Event activities may fail when processing parameters of type long. This issue occurs when the event configuration expects a 32‑bit integer but receives a value that exceeds the integer limit (2,147,483,647). For example, a CertSignOff event with a ref_row_id that exceeds 2,147,483,647 will cause the activity to stop with an error. Workflows that store long values as strings (for example, DataLog events) are not affected. To address this issue, open the affected activity, clear the event configuration and parameters, re-enter the values, and save the workflow.
ENH 3697206	Work Tasks Connector configuration does not allow for password of more than 40 characters. This is an MES limitation of the API to verify an MES User exists in the database.
IMS 4408587	Sometimes, when opening the Work Tasks Enterprise Console, or changing locations within the console, the Enterprise Console menu does not load and the following ValidateTokens error message appears in the Operations Control Management Console (OCMC) Log Viewer: The provided anti-forgery token was meant for user "<domain>\<user>", but the current user is ""'. To address this issue, in Internet Information Services (IIS), navigate to AVEVAWorktasksSites and select EnterpriseConsole. On the right-hand side, open the Authentication feature and set Anonymous authentication to Enabled.
na	In distributed deployments, the Work Tasks Enterprise Console Authentication Provider page may not display the Active Directory and MES User provider links after you configure the Work Tasks Extension for MES. This issue occurs because the required diagnostics assembly (Skelta.Connector.Diagnostics.dll) is not installed on nodes that run only the Work Tasks Extension. Without the assembly, the authentication components cannot load correctly. To address this issue, install Work Tasks 2023 R2 HF4 on the node that hosts the Work Tasks Extension. Note: Work Tasks 2023 R2 HF4 (AWT2023R2-HF4) is included on the Work Tasks Extension and Connector for MES installation media. For details on installing the hotfix, refer to the hotfix readme (AWT2023R2-HF4 Readme).
na	Some transactions might be blocked or might not work properly if the stored procedures involved in the transaction are missing NOLOCK hints. As a result, the transaction might not complete within the transaction timeout period, which will cause changed data to be rolled back. If using custom stored procedures, make sure NOLOCK hints are added to the SQL SELECT statements to prevent transactions from being blocked.
na	When using the MES transaction control activities in a workflow, the entire workflow must execute against a single MES middleware. There are scenarios where Work Tasks load balancing may move the execution of the workflow between workflow engines mid-execution which will result in transaction control failures. It is also possible that an MES middleware proxy may switch MES middleware if the initial MES middleware fails during execution of the workflow. This will also result in transaction control failures. This release of the connector will log additional messages in the logger if it detects a change in the MES middleware proxy or MES middleware node executing transaction control.