AVEVA Model Driven MES 7.0 release notes
- Last UpdatedFeb 13, 2026
- 4 minute read
Expectations and limitations
The following expectations and limitations should be considered for this release of AVEVA Model Driven MES.
Special character handling in Model Driven MES
Unsupported special characters in Model Driven MES can cause failures or unexpected behavior when used in MES object names, SQL filtering, Web API requests, or Middleware Access URIs. These characters are interpreted as SQL wildcard/control symbols, are not escaped by Work Tasks when forming API calls, or result in invalid URIs. The following table summarizes unsupported characters in Model-Driven MES by area of use:
|
Area of use |
Disallowed characters |
Notes |
|
MES object names and IDs |
% (percent) _ (underscore) ^ (carat) [ ] (square brackets) |
These special characters can cause unexpected behavior when retrieving records because SQL Server LIKE treats them as wildcard/control characters. |
|
SQL filtering operations |
These special characters are used by SQL Server calls that use the LIKE operator. If the characters are used in SQL filter expressions filter operations may behave unexpectedly or break. |
|
|
Web API calls |
& (ampersand) \ (backslash) < (left chevron) " (double quotation) |
These special characters are not escaped when Work Tasks forms make Web API calls, causing API errors. |
|
Middleware access URI usage |
These special characters return errors unless escaped in URIs or calls. |
In general, avoid using these special characters in all MES object identifiers, Work Tasks inputs, Web API payloads, and any data involved in SQL filtering or Middleware access operations.
New features and enhancements
This version of Model Driven MES is compatible with System Platform 2023 R2 SP1 Patch 3 or Patch 4, Manufacturing Execution System (MES) 2023 R2, and Work Tasks 2023 R2, but no previous versions of these products.
This following new features and enhancements were added:
-
Support for redundant Single Sign-On (SSO) is provided by System Management Server (SMS), MES, and Work Tasks.
Note: While Work Tasks and Model Driven MES support AVEVA Identity Manager (AIM) redundancy, user access tokens are not synchronized across redundant AIM nodes. Seamless session continuation across AIM nodes is not supported. If an AIM failover occurs, users must log out and log back in to obtain a new authentication token from the active AIM node.
-
The utilization form is now updated to show only the configured allowable reasons for an entity.
Resolved issues
The following important issues were resolved in this release, listed by their reference number.
|
ID |
Description |
|---|---|
|
Bug 2838174 |
The New and Edit buttons are disabled in Quality Management forms hosted in OMI View application when the form parameters are submitted as input XML values. To enable the New and Edit buttons, select the Result tab and then re-select the Sample tab. |
|
Bug 2860951 |
The SPC chart widget point display colors are not updated to black when displaying out-of specification values. |
|
Bug 2889236 |
Non-english translations are not available for the following Information Card List widget error message: "Cannot display one or more cards due to invalid input. For more information, see console." |
|
IMS 2316503 |
The Job Management form is unresponsive after hours of inactivity. |
|
IMS 3001197 |
Unable to split utilization event in MDM Job Management form. |
|
IMS 3359788 |
When creating a new Work order for a line the item Popup filter does not work. |
|
IMS 3642306 |
SPC Chart not loading on first click. |
|
IMS 3669241 |
Enterprise Console crash when editing final filtered item in grid and filtered list now returns no rows. |
|
IMS 3694026 |
The result status displays wrong icons in MDMResultValues form with decimal spec limits. |
|
IMS 3790602 |
Editing of two utilization events consecutively results in the second edit modifying the first event. |
|
IMS 3827669 |
Utilization Reason code cannot be edited for time range during DST change |
|
IMS 3941531 |
Utilization tab is not shown unless there is a job running on the entity. |
Known issues
This release includes the following known issues.
Work Tasks 2023 R2
|
ID |
Description |
|
Case 960648780 |
Model Driven MES forms are not supported in the AVEVA Work Tasks Pro mobile application. Model Driven MES forms currently require access through supported desktop web browsers. |
|
IMS 2540410 |
Errors may occur when selecting Load Columns in the Web API Lookup setting page. To resolve this issue, do one of the following:
|
|
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 |
Users cannot sign in to Model Driven MES using Azure Active Directory (Microsoft Entra ID) accounts. Model Driven MES does not support Azure Active Directory authentication. To avoid sign-in errors, use Active Directory user accounts instead of Microsoft Entra ID accounts to access Model Driven MES. |
Differences between the SPC Chart widget and .NET control
The SPC chart widget has the following functional differences when compared with the SPC chart .NET control:
|
ID |
Description |
|
Bug 2861601 |
The table associated with the SPC chart widget continues to display the associated alarm values for ignored sample points. |
Job Management
|
ID |
Description |
|
Bug 2587555 |
While opening Entity Dashboard without a selected job, the following warning message regarding a web API will appear in SMC: The remote server returned an error: (400) Bad Request. To address the warning message, select a job. |