How much effort is required to get the automation to work after upgrading Office to a newer version?
I am currently building an Openspan solution that automates a Excel 2010 spreadsheet. I'm running the Office 2010 runtime, so this is working fine. If the client were to upgrade their office suite to a newer version like 2013, then how much effort is required to get the automation working with the new version? What actually is required to be done? Thanks.
***Updated by moderator: Lochan to update Categories***
Pegasystems Inc.
US
Hi Gar,
What is the build version of Robotics that your client is currently using?
--Zach
Accepted Solution
Pegasystems Inc.
US
Gar,
If you are running Pega Robotics 8.0 and higher, you will simply need to adjust the user's runtimeconfig setting to specify which version of Office you are running on the machine. See illustration below for clarity.
If your client is connected to OMC, this change would need to occur for the user or user group runtime settings on OMC.
If your client is not connected to OMC, you will need to make this change for each user's runtimeconfig.xml inside of the user appd data directory, i.e. %appdata%/openspan
<!-- Version of OpenSpan Office assemblies to use with Runtime. -->
<!-- Values: "None", "2002", "2003", "2007", "2010", "2013" or "2016" -->
<add key="OfficeVersion" value="None" />
In the case in which you are running a Robotics version lower than 8.0, i.e. 7.1.x, 7.0.x etc.. You will need to re-install the Runtime Enterprise on the user's machine and specify the higher version of Office during the re-install.
Thanks,
--Zach
Accenture
CA
Hi Zach,
The client is running Pega Robotics 8.0, so based on your answer, only the runtimeconfig.xml will need to be changed and it is not necessary to re-install the Runtime Enterprise.
Thanks,
Gar