Limitations

Messages or notifications in AVEVA Work Tasks, which are returned by third party controls such as, ISWebGrid, Telerik, or Kendo does not comply with the Message bar usage and guidelines.

When Email Notification is configured for an Invoke Form Activity, the form opens through the Email. However, when the form is submitted successfully, the confirmation message does not appear.

When you receive an email notification configured for an Invoke Form Activity, and click the link in the email, the form opens in a window. If Google Chrome is the default browser, then the window closes as expected.

In Invoke Form Activity, Multi-select and Close on Finish property are not supported in Forms.

The user interface messages and error messages for Publish, UnPublish, and Publish and Test run in workflows do not conform to the Message bar standards.

While packaging, workflows containing the following combination of Property and Activity does not work as expected:

• Exception Template Property (Affected activity : Start Activity)

You can associate multiple events to a single workflow. However, the event provider type must be the same.

Although localization is supported, some of the special characters such as, ' " # & / & [ \ ] | ~ + < > are not supported for Workflow names and List names. We recommend that these special characters are not used in naming the activities.

When a workflow with Message Queue activities is installed in the target environment and if its associated artifact (Message Queue Connection) does not get installed, then the workflow is installed in Draft status. If you manually publish this workflow, it will return unexpected results.

In Workflows and Forms, when users log in through various repository providers such as Microsoft Entra ID, Active Directory, Active Directory with token authentication, and Forms, the Owners field displays the configured Display Name rather than the logged-in repository user name. However, for CONNECT, List, and ASP.NET, the Owners field displays the same name as the logged-in user, as the Display Name and logged-in repository user name are identical in these cases.