Upgrading to AVEVA Work Tasks 2023

Upgrading Scenarios

You can upgrade to AVEVA Work Tasks 2023 from the following versions:

• AVEVA Work Tasks 2020

• AVEVA Work Tasks 2020 Update 1

• AVEVA Work Tasks 2020 Update 2

However, if you want to upgrade from versions earlier than AVEVA Work Tasks 2020, you must first upgrade to AVEVA Work Tasks 2020, and then to AVEVA Work Tasks 2023.

Make sure that the user has appropriate rights for installing and upgrading software on the machine.

Upgrading to AVEVA Work Tasks 2023

When you upgrade the product to AVEVA Work Tasks 2023, the earlier product version is uninstalled and all the files are removed. Therefore, we recommend that you back up the files before upgrading the product.

After the upgrade, you will see the following changes:

• When you opt to back up the files during the upgrade process,

  • the CentralConfig.xml file is retained in the old AVEVA Work Tasks install folder with a .bak suffix.

  • the AWT2020_Backup folder is created in the old AVEVA Work Tasks install path. The existing Locales, Web, and WorkflowElements folders are moved to this backup folder.

• AVEVA WorkTasksTemp and AVEVA Work Tasks Cache files are removed from the machine.

  Note:
  - Customizations to files in Locales, Web, and WorkflowElements folders need to be applied again to the newly created files after an upgrade.
  - The SAP Connection list will not be present after an upgrade. The workflows with SAP activities will be replaced with dummy activities, and the workflows may not get executed properly.

Steps to Upgrade

1. Run AVEVA Work Tasks 2023.exe to upgrade to AVEVA Work Tasks 2023.

   The installer splash screen, and then the Prerequisites installation screen appears.

2. Install the Prerequisites.

   Note: The system restarts after installing .NET Framework 4.8.

3. Click Next after installing the prerequisites.

4. Perform one of the following:

   • Click Yes if you want the installer to take the backup.

   • Click No if you do not want the installer to take the backup.

     The installer waits 20 seconds for any input and continues the installation process without backing up the files if no user input is provided.

5. Click Next.

   The system prompts you for the restart.

6. Click OK if you want to restart the machine.

7. After restart, on the InstallShield Wizard Completed dialog box, click Finish.

8. The Upgrade Manager automatically gets launched and performs the following tasks:

   • Opens Cryptography Settings window. Provide the Passphrase to proceed.

     Note: While upgrading the product from AVEVA Work Tasks 2020 to AVEVA Work Tasks 2023, you are prompted to provide a Passphrase.
     But the Passphrase is not needed while upgrading from
     - AVEVA Work Tasks 2020 Update 1 to AVEVA Work Tasks 2023
     - AVEVA Work Tasks 2020 Update 2 to AVEVA Work Tasks 2023

   • Stops the services and Application Pools.

   • Deletes the WorkTasksTemp and Work Tasks Cache files from the machine.

     For more information on how to run the Upgrade Manager, see Run Upgrade Manager in the Administrator Guide.

     You may be prompted to restart the machine. After the machine is restarted, launch the Upgrade Manager manually using AVEVAWorkTasksUpgradeManager.exe available in the <Installation Path>.

Notes:
- During AVEVA Work Tasks upgrade, if Operations Control Logger, Platform Common Service, and Common Licensing API Framework prompt to restart the machine, you can ignore and do a restart after completing installation. If you opt to restart the machine, the installation does not resume after a restart. You will have to run the installer to continue the installation.

- After the upgrade completes, the Work Tasks services and Application Pools start automatically.

- It is recommended to clear the browser cache on the machines where Enterprise Console site is accessed to get the (js, css, images, etc. files) changes to take effect after the upgrade. For more information on how to clear cache, see the Cache Refresh Settings section in the Administrator Guide.

- Deprecated SQL Server Management Objects (SMO) will not be removed from the system automatically.