Upgrade Connector for System Platform
- Last UpdatedOct 28, 2026
- 3 minute read
You can upgrade to AVEVA Work Tasks 2023 R2 U1 Connector for System Platform from AVEVA Work Tasks 2023 R2 Connector for System Platform.
Prerequisites
Before upgrading the Connector for System Platform, complete the following prerequisites:
-
Upgrade AVEVA Work Tasks 2023 R2 to AVEVA Work Tasks 2023 R2 U1 on the AVEVA Work Tasks server.
-
Undeploy the Platform and Workflow Gateway Object.
-
Upgrade the Connector to the latest version.
-
Restart the Connector machine before importing files into System Platform IDE.
Additional steps for specific System Platform versions
Before importing the Connector related files, complete the following additional steps for your System Platform version:
System Platform 2026
-
Restart the virtual machine.
System Platform 2023 R2 SP2
-
Apply System Platform 2023 R2 SP2 hotfix IMS 5081639.
System Platform 2023 R2 SP1 P04
-
Follow the workaround described in Galaxy Migration Errors After Upgrading to SP2023R2SP1.
Steps to upgrade
Import files to System Platform IDE
After completing the prerequisites and any applicable version-specific steps, import the following files in the exact order shown:
-
ArchestrA.InTouch.SkeltaControls.dll to enable workflow features in InTouch HMI
-
AVEVA Work Tasks controls for InTouch OMI
-
WorkflowGateway object file, aaPKG or aaPDF
-
Script function library (ArchestWorkflowScripts.dll)
Import DLL files
When you import the object into System Platform IDE, the following DLL files are stored in the ArchestrA Installation folder > Framework > FileRepository > CustomCategoryUIFiles folder.
-
ArchestrA.Workflow.IDEExtension.dll
-
Skelta.ArchestrA.WinForms.dll
-
Skelta.WinForms.dll
-
Skelta.WinForms.Security.dll
If these DLL files are not added automatically, copy the files manually from C:\Program Files (x86)\ArchestrA\Workflow\IDEExtension to:
-
C:\Program Files (x86)\ArchestrA\Framework\FileRepository\CustomCategoryUIFiles
-
C:\Program Files (x86)\ArchestrA\Framework\Bin\IDEExtensions
Verify that the files are available in the Framework\Bin\IDEExtensions folder under the ArchestrA installation path.
If the files are missing, copy them manually. The Workflow tab in System Platform IDE > Workflow Toolbox is not displayed unless these DLL files are available.
Import ArchestrA.InTouch.SkeltaControls.dll to use additional controls that enable workflow features in InTouch. For information about InTouch controls, see Workflow Status View Inside InTouch.
Import ArchestrA App
-
Open System Platform IDE.
-
Select Galaxy > Import > ArchestrA Apps.
-
In the Import ArchestrA App dialog box, navigate to: <Installation Path>\ArchestrA\Workflow\InTouchOMI\.
-
Import the ArchestrA App.
The imported ArchestrA App appears as AVEVAWorkTasksAppXXX in the Graphic Toolbox.
Import WorkflowGateway object file
The WorkflowGateway object file (.aaPKG or .aaPDF) stored in the AppObjects folder.
-
Open System Platform IDE.
-
Select Galaxy > Import > Object(s).
-
In the Import Automation Object(s) window, navigate to: <Installation Path>\ArchestrA\Workflow\AppObjects
-
Select the WorkflowGateway_XX.X.aaPKG file.
-
Select Open.
-
In the Import Preferences window, select OK.
-
After the import completes, select Close.
-
Close and reopen System Platform IDE.
Import script function library
To import ArchestrAWorkflowScripts.dll:
-
Open System Platform IDE.
-
Select Galaxy > Import > Script Function Library.
-
In the Import Script Function Library window, navigate to: <Installation Path>\ArchestrA\Workflow\Scripts
-
Select ArchestrAWorkflowScripts.dll.
-
Select Open.
Note:
- Import the ArchestrA App only once. System Platform IDE allows multiple imports
of the ArchestrA App by creating multiple objects with incrementing sequence numbers,
such as AVEVAWorkTasksAppXXX, which can lead to inconsistencies.
- During an upgrade, the existing WorkflowManagementApp is not overwritten. Delete
the existing WorkflowManagementApp before importing the new version.
- Before deleting the existing WorkflowManagementApp, ensure that it is not referenced
by any ViewApp, Layout, or other objects. Otherwise, warnings may be generated in
the logger.