Update best practice
Common recommendations
Before updating Intelligent Automation Cloud Business, there are some steps we recommend to follow.
- Check all the changes mentioned in Release notes.
- Make sure you have a full installation package (including IntelligentAutomationCloudInstaller.exe and folder "resources" with the necessary MSI files) for your current Intelligent Automation Cloud version. It may be required to restore your previous installation.
- Test update procedure on your Test Environment before doing it on Production Environment.
- Close all unnecessary applications to free up memory usage during the update procedure.
Preconditions
Before updating, make sure that:
- You have enough free disk space according to system requirements. We recommend having some additional free space (at least 15 GB).
- You have backed up your business processes in Control Tower as described in this guide. Thus, in case the update goes wrong, you are able to restore all the data.
- You've copied all projects from your workspace folder (by default C:\Users\%user_name%\workfusion-workspace) and saved them somewhere on your PC or another available storage.
- You have made screenshots of schedules for business processes which you don't want to miss, as there is no option to back up your schedules.
- There are no running business processes during the update. To update Intelligent Automation Cloud Business, define a maintenance window for about three hours. A time period can vary and depends on your PC performance.
Update procedure
Now, as you made all the preparations, you are ready to update. Follow the steps below.
caution
Note that update should be done with Administrator rights.
- Close your Business Edition. In the latter case, server components should be closed too.
- Refer to this instruction to update.
Checkout
When the update is finished, do as follows.
- Start Intelligent Automation Cloud Business.
- In case of Business Edition, check that all components (Control Tower, OCR, WorkSpace, File Storage) are running correctly.
- Run some test script in WorkFusion Studio. You can use scripts from the Welcome to WorkFusion Studio page or from our Examples Library.
- Publish a test script to Control Tower using the Publish to Control Tower button.
- If you have Bot Tasks, create a test one and publish it to Control Tower, too.
- Open Control Tower and run the test business process to check that everything works as expected.
Results
If the checkout results confirm that everything works ok, your update procedure is successful.
If you face any critical issue you haven't faced before, restore your previous installation and backups. To restore the previous version of Business Edition, do as follows.
Uninstall Intelligent Automation Cloud Business you have just installed.
Install the previous version from the installation package (you should have it before starting the update procedure).
Restore all your backups. In order to do it, follow the following steps.
- Put all the project files you previously copied to the workspace folder. By default, it is C:\Users\%user_name%\workfusion-workspace.
note
Keep in mind that while opening a recording created with an older version of Intelligent Automation Cloud Express or Business, migration can fail sometimes. Refer to Troubleshooting to deal with the issue.
- Make sure that all your scripts are successfully executed in WorkFusion Studio. In some cases, you may need to rewrite or correct your scripts. Refer to Release notes for more details about new features and bug fixes.
- Go to your Control Tower (it should be running), click Import package, and import the backed up packages one by one.

- Check how your business processes are executed in Control Tower. Due to the difference in versions, some processes may require changes. If you have their scripts in WorkFusion Studio, you can republish a new version from WorkFusion Studio and check how they run.
- After you correct all your scripts and business processes, configure your schedules according to the screenshots you previously made. Then, check execution by schedule.