There are various scenarios which may prompt you to upgrade your Studio clients.
On this page, we illustrate the best path to follow for each of the following scenarios:
- Update your SAP ERP release
- Update your SAP GUI
- Update your Microsoft Office or Microsoft Operating System
- Update based on your Studio version End-of-Life date, or based on access to new Studio features
It is assumed that you will follow the standard upgrade practices; for example, always update your Sandbox/Development environments and move to QA and Production systems to minimize the impact of any upgrade risks. It is also recommended in cases where you are not required to upgrade the AFM in the beginning, that you plan to do so ultimately, in order to reap the full benefits of the new Studio version.
Update your SAP ERP release
This applies when you are upgrading your SAP basis release from version A to B (for example, upgrading to SAP S/4HANA 1909). Please review the Studio System Requirements before making this decision, to ensure that there is a version of Studio that supports the specific SAP release.
Best practice
- Upgrade AFM and Studio at the same time to the version that has been tested with this SAP ERP release.
- Import your scripts and regression test them, modifying them as necessary.
- We do not receive advance access to the SAP S/4HANA software, so our SAP certification process may take several months to complete once SAP has made their S/4HANA release. The length of time required depends on the scope of their changes and whether we also need to include other third-party software component changes in our product.
Alternative supported option
- Contact Automate Customer Support to learn if there are any known changes that were required in Studio or any of its third-party software components as a result of this SAP ERP release. If none are identified, verify that the AFM version that was compatibility tested by Automate with the version of SAP is listed as being compatible for your existing version of Studio or of Transaction, Query and Direct.
- If compatible, then first upgrade just your AFM to the version that has been tested with this SAP release.
- Start regression testing of your existing scripts in your lab environment with this version of SAP. If you find errors that you can’t live with, upgrade to the Studio version that matches your AFM version and import your prior scripts to see if that resolves your errors.
- If the errors are still present in your scripts, then modify your scripts to update them to resolve the errors.
- Regression test as deemed necessary by your organization.
Update your SAP GUI
This applies when you are upgrading your SAP GUI from version A to B. Studio System Requirements should always be considered before making this decision to ensure that there is a version of Studio that supports this SAP GUI release.
Best practice
- Upgrade AFM and Studio to the version that has been tested with this release of SAP GUI.
- Import your scripts and regression test them, modifying them as necessary.
Alternative supported option
- Review Release Notes or contact Customer Support to learn if there are any known changes that were required in AFM as a result of Automate’s qualification of this SAP GUI release. If none are identified, verify that the version of the Studio that was compatibility tested by Automate with the version of SAP GUI is listed as being compatible for your version of AFM.
- If compatible, first upgrade just your Studio Clients to the version that has been tested with SAP GUI.
- Start regression testing of your existing scripts in your lab environment with this version of SAP GUI. If you find errors that you can’t live with, upgrade to the AFM version that matches your Studio version to see if that resolves your errors.
- If the errors are still present in your scripts, modify your scripts to update them to resolve the errors.
- Regression test as deemed necessary by your organization.
Update your Microsoft Office or Microsoft Operating System
This applies when you are updating your Office or OS versions and the current Studio install does not support this update. For example, Office 2016 is not supported with Automate version 10.7.
Best practice
- Use the Studio System Requirements to confirm which versions of Microsoft products are supported in each Automate product release. Upgrade Studio to the latest version that support the combination of the intended Office or OS version.
- Start regression testing of your existing scripts in your lab environment with this version of OS/Office.
- If there are issues you can’t live with, check with Automate Customer Support or review Release Notes if the issues have a AFM dependency. If there are issues with a AFM dependency, upgrade your AFM to the version that matches Studio. If not, wait for a patch fix to be delivered for the issue.
- Regression test as deemed necessary by your organization.
Update based on your Studio version End-of-Life date, or based on access to new Studio features
This scenario is applicable when the EOL date would trigger expiration of your customer maintenance contract which governs both your access to Automate Customer Support and your right to upgrade to the latest version of Studio without additional charge.
However, if you are working with 10.x on Office 2013 and are now required to move to version 12.x or 20.x because the older Automate version is no longer supported, you can refer to this section since you are not required to upgrade your Office.
Best practice
- Upgrade Studio to the latest available GA version that is supported for your current environment (refer to the Studio System Requirements). If the current environment is not supported, please refer to the sections on SAP GUI, SAP Release, or Office/OS update practices.
- Start regression testing of your existing scripts in your lab environment.
- If there are issues you can’t live with, check with Automate Customer Support or review Release Notes if the issues have a AFM dependency. If there are issues with a AFM dependency, upgrade your AFM to the version that matches Studio. If not, wait for a patch fix to be delivered for the issue.
- Regression test as deemed necessary by your organization.