Work Tasks 2023 R2 U1 release notes

This section provides information about important features, resolved issues, and known issues for AVEVA Work Tasks 2023 R2 U1. The product and the documentation are subject to change without notice.

Important: There are unsigned third-party components that are shipped with AVEVA Work Tasks. It is recommended that you verify that the file names, SHA1 hashes, and SHA256 hashes match those installed on the server. For details, refer Other Components under Acknowledgements section in the online Help.

Expectations and limitations

Review the following information before installing, upgrading, or configuring AVEVA Work Tasks 2023 R2 U1:

• The System Requirements, Product Compatibility, Upgrade Procedure, and Installation Prerequisites documentation have been updated.

  Note:
  - Connector prerequisites: Before installing or upgrading the Connector for System Platform, complete the mandatory prerequisites and follow the version-specific instructions in Upgrading Connector for System Platform.
  - Affected product versions and workaround: For information about the affected product versions and the applicable workaround, see Galaxy Migration Errors After Upgrading to SP2023R2SP1.

• If you use MES Connector/Extension 7.1, install the components in the following order:

  1. AVEVA Work Tasks 2023 R2

  2. MES Connector/Extension 7.1

  3. AVEVA Work Tasks 2023 R2 U1

     Note: Deviating from this installation sequence may cause plugin configuration issues or DLL reference errors, affecting compatibility between AVEVA Work Tasks 2023 R2 U1 and MES Connector/Extension 7.1.

• AVEVA Work Tasks 2023 R2 U1 requires a product License version 23.0 or higher.

• The AVEVA Work Tasks license is now acquired from the License Server specified in the Configurator, instead of the Farm Configuration Wizard.

• The Federated Identity Provider - CONNECT is not supported.

• After upgrading to AVEVA Work Tasks 2023 R2 U1, perform the required Token Service re-registration and repository mapping steps. For more information, see Post-upgrade Token Service configuration in Token Service.

• After upgrading to AVEVA Work Tasks 2023 R2 U1, failed workflow instances in the AIM Repository cannot be resumed due to token limitations. Any workflow instances in a failed state must therefore be corrected and resumed before the upgrade.

• By default, the WebApiRetry registry setting is enabled (true), which can result in duplicate Web API requests. To prevent duplicate requests, set WebApiRetry to false.

• Ensure that Erlang version 27.x and RabbitMQ version 4.2.9 are installed. If multiple RabbitMQ versions are installed, delete C:\Users\<UserName>\AppData\Roaming\RabbitMQ before proceeding.

  For additional RabbitMQ configuration steps to optimize WaitForQueue performance in high-volume environments, see RabbitMQ Connections.

• If you are planning to install any application on the same machine that installs an earlier version of the above mentioned prerequisites (for example, PCS 8.0), install that application before installing AVEVA Work Tasks 2023 R2 U1.

• Microsoft .NET Core 10.0.12 is a prerequisite for AVEVA Work Tasks and is included in the list of prerequisites. However, the installation will depend on the version existing on the target machine.

• When a user runs the AVEVA Work Tasks installer, cancels, or completes the Microsoft .NET Core 10.0.12 installation, and reruns the installer, Microsoft .NET Core 10.0.12 will still appear in the prerequisites list but will be skipped, enabling the installation to proceed. If the AVEVA Work Tasks installation is completed entirely and the installer is run again, none of the prerequisites will be displayed.

• AVEVA Work Tasks needs Microsoft .NET Core 10.0.12 or a newer version to be installed on the machine. Although the Work Tasks installer tries to install it as a prerequisite, if the Microsoft .NET Core 10.0.12 installation encounters any issues, the installation process will continue. However, it will be incumbent upon the customer to manually install Microsoft .NET Core 10.0.12 in such instances.

• While Microsoft .NET Core 10.0.12 is being installed, if an installer screen with Repair, Uninstall, or Close option appears, select Repair option to proceed installation. This will restart the machine after repair and then the installation setup resumes.

• During AVEVA Work Tasks installation, if installation of Platform Common Service and Common Licensing API Framework prompt to restart the machine, you can ignore the prompt and restart the machine after the installation is complete.

• The WixSharp binary or the environment variable WIXSHARP_WIXDIR are not part of AVEVA Work Tasks 2023 R2 U1 version. To ensure the proper functionality of the packages, users must manually install the WiX Toolset. The recommended version is WiX3.14.

• If Windows Update or the System Platform installation program (setup.exe) detects that a system restart is pending, you must restart your computer and run the System Platform installation program again. If the restart message persists after restarting the computer, check the PendingFileRenameOperations value under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager. If the value exists, review the data to identify the component requiring a restart and contact your IT team or the component vendor for assistance.

Deprecation notice: Features planned for removal in a future release

The following features are currently supported in AVEVA Work Tasks but are planned for removal in a future release. If you use these features, plan to transition to the recommended alternatives before upgrading.

• ASP.NET Membership Providers: Transition to the Active Directory Provider or Entra ID Provider.

• JScript and VBScript in Script activity: Use C# instead.

• Unsafe constructs in Script editor: Avoid the restricted constructs listed in the deprecation notice and use supported alternatives.

• OPC UA integration: Use AVEVA System Platform for downstream data connectivity with plant-floor systems.

• SOA Activity: Use Script activity to implement logic or migrate to Web API integrations.

• SMS Activity: Refer to Tech Alert 55047 for information about this deprecation.

New features and enhancements

• AVEVA Work Tasks now supports .NET roll-forward to a major version, enabling forward compatibility testing against newer .NET releases. Refer to the Technology Matrix for supported .NET versions.

• AVEVA Work Tasks 2023 R2 U1 supports System Platform 2023 R2 SP2. Refer to the Technology Matrix for compatibility details.

• Enhanced Workflow Gateway Object (WGO) to persist the configured Work Tasks (WT) server list during provisioning, enabling seamless failover and connectivity to alternate WT servers without requiring runtime server discovery.

• Improved RabbitMQ message processing when a single queue has a high volume of active records in the SKEventBindings table. Kill/Pause/Resume functionality has been added to the WaitForMQ activity to remove aborted or paused records.

Resolved issues

Known issues

You might come across the following issues when you work with AVEVA Work Tasks:

• When a workflow is scheduled to trigger after a specific time duration and the system experiences downtime, the system may create more workflow instances than expected once it resumes.

• Prolonged use of the Web Logger results in CPU utilization spikes. Immediate closure is crucial to restore CPU to normal levels and maintain application stability.

• Entering GET as an instance name is not supported while designing a workflow in Process Designer or while creating Forms and Lists.

• Entering or editing values in Rich Text control is not supported in Mozilla Firefox browser.

• A colon character (:) is not supported in an Activity Name while designing a workflow in Process Designer.

• When installing a package, if Folder A already exists in the Forms List of the target environment and the package contains a Forms List with the same folder name (i.e., Folder A), the system logs the following message in the package history:

  Folder title is not unique, or it contains special characters like \\,*/, #&[]; ...

• When Quickflow application is integrated with AVEVA Work Tasks, the enabling and disabling persistence of exceptions and warnings into the database requires a restart of the Quickflow Status Monitor service to apply the changes.

• RFID scan is not supported for Work Tasks Pro Universal Windows Platform (UWP) app.

• In some cases, uninstalling a package that contains an MSI may fail or not complete successfully.
  As a workaround, perform an IIS reset on the affected machine, and then retry the package uninstall. This resolves the issue and allows the uninstall to complete successfully.

User documentation

The AVEVA Work Tasks documentation is available on the AVEVA documentation portal. The AVEVA Work Tasks documentation library consists of the following guides:

• AVEVA™ Work Tasks Administrator Guide: Provides information about installing, configuring, upgrading, and administering AVEVA Work Tasks.

• AVEVA™ Work Tasks Connectors and Extensions User Guide: Provides information about installing and configuring Work Tasks connectors and extensions.

• AVEVA™ Work Tasks Developer Guide: Provides information for developers working with AVEVA Work Tasks.

• AVEVA™ Work Tasks Forms and Lists User Guide: Provides information about working with forms and lists in AVEVA Work Tasks.

• AVEVA™ Work Tasks Quickflow User Guide: Provides information about creating and working with Quickflows.

• AVEVA™ Work Tasks User Guide: Provides information about using AVEVA Work Tasks.

• AVEVA™ Work Tasks API Scenarios Guide: Provides examples and guidance for using Work Tasks APIs in supported scenarios.

• AVEVA™ Work Tasks API Reference Guide: Provides reference information for the Work Tasks APIs.