Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Work Tasks

TABLE OF CONTENTS

Upgrade Connector for System Platform

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedJul 30, 2026
  • 2 minute read

You can upgrade to AVEVA Work Tasks 2023 R2 Connector for System Platform from the following version AVEVA Work Tasks 2023 Connector for System Platform.

Prerequisites

  • On the AVEVA Work Tasks server, upgrade AVEVA Work Tasks 2023 to AVEVA Work Tasks 2023 R2.

  • Undeploy the Platform and Workflow Gateway Object.

  • Upgrade the Connector to the latest version.

  • Restart the Connector machine after upgrading the Connector and before importing any files into System Platform IDE.

Steps to upgrade

Import files to System Platform IDE

After restarting the Connector machine, import the following files in the exact order shown:

  1. ArchestrA.InTouch.SkeltaControls.dll to enable workflow features in InTouch HMI

  2. AVEVA Work Tasks controls for InTouch OMI

  3. WorkflowGateway object file, aaPKG or aaPDF

  4. Script function library (ArchestWorkflowScripts.dll)

On importing the object to System Platform IDE

The following DLL files are stored in 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 stored in the CustomCategoryUIFiles folder are copied to:

ArchestrA installed path > Framework > Bin >IDEExtensions.

If they are not present, 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

  1. Open System Platform IDE.

  2. Select Galaxy > Import > ArchestrA Apps.

  3. In the Import ArchestrA App dialog box, navigate to: <Installation Path>\ArchestrA\Workflow\InTouchOMI\.

  4. Import the ArchestrA App.

    The imported ArchestrA App appears as AVEVAWorkTasksAppXXX in the Graphic Toolbox.

    The WorkflowGateway object file (.aaPKG or .aaPDF) stored in the AppObjects folder must also be imported.

    1. Open System Platform IDE.

    2. Select Galaxy > Import > Object(s).

    3. In the Import Automation Object(s) window, navigate to:

      <Installation Path>\ArchestrA\Workflow\AppObjects

    4. Select the WorkflowGateway_XX.X.aaPKG file.

    5. Select Open.

    6. In the Import Preferences window, select OK.

    7. After the import completes, select Close.

    8. Close and reopen System Platform IDE.

      Import Script Function Library (ArchestrAWorkflowScirpts.dll)

      1. Open System Platform IDE.

      2. Select Galaxy > Import > Script Function Library.

      3. In the Import Script Function Library window, navigate to:

        <Installation Path>\ArchestrA\Workflow\Scripts

      4. Select ArchestrAWorkflowScripts.dll.

      5. 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.

        - Ensure that the existing WorkflowManagementApp is not referenced by any ViewApp, Layout, or other objects before deleting it. Otherwise, warnings may be generated in the logger.

        In This Topic