runtime changes for win-7 to win-10 migration (microsoft office version)
We are moving from Openspan Proprietary information hidden (for Windows 7) to Robotics 8.0.1082.0 (for Windows 10). Our current runtime is configured for "Office 2016". Our new Office version will be "Microsoft Office 365 ProPlus 32-bit".
There is no version for this on the "Pega Robotics Office Support" page of the install. How do we configure this? Does anyone have experience with this?
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
IN
Hi faithr28,
As per the information from Microsoft website, Office 2016 is a part of Microsoft Office 365.
So , there should not be any issues if the Office version selected while installation is Office 2016
mutual of omaha
US
So if Microsoft Office 365 is later associated with a future version, let's say Office 2022, Will configuration using Office 2016 break?
I ask because we went through a painful upgrade when we updated all our runtimes to use Office 2016. It was costly and I would like to avoid going through this if possible.
mutual of omaha
US
Can someone respond to this?
I am told that at present Microsoft Office 365 and Office 2016 are alike when configuring our runtime install today. However, if Microsoft Office 365 opens a different Office version in the future, will this break our runtime configuration which says it is for Office 2016?
mutual of omaha
US
Thank you again for your response. Are you able to add anything more to answer my question?
What happens to my solution if I build it for 2016 today and tomorrow's outlook requires something like 2020?
Or is there a way to make this configurable without forcing a reinstall of the runtime?
Pegasystems Inc.
IN
Hello faithr28,
Apologies for delay in response.
If microsoft adds any new version to 365 , then first Pega Robotics has to add it in their new release to make it compatible.
Then probably after that you may have to download the latest version of robotics where it will support new versions of Microsoft office.
As of now it supports 2016 and other versions very well.
Thanks.
mutual of omaha
US
@pandr2
Thank you for your answer. If we must reinstall runtimes, we will remove this functionality. Reinstalling the last runtime was exceptionally painful with our packaging tools.