Common upgrade pitfalls and how to avoid them
During the process of executing an upgrade, there's always a chance that a small error or oversight could cause your project to progress slower than expected. This article gives you the benefit of all the lessons learned by our community members who have learned the hard way about these "red flags" in the past!
Lesson 1: Encryption
Encryption keys are used by Blue Prism to keep certain data, like credentials, safe. Therefore, it's very very important to make sure that the same keys you use today are replicated in your upgraded environment. This encryption key may either be stored in your database (in which case a standard SQL database backup is sufficient) or stored as a seperate file on the Application Server.
For more information about encryption and certificates, see here.
Lesson 2: 32-bit to 64-bit
Bitness is important for Blue Prism Enteprise (BPE), and from version 7.2+ BPE runs as a 64-bit process by default. This can cause issues with business objects which were created before the upgrade to 7.2+. Make sure to check the Upgrade Notices page to see how this might impact your processes.
Lesson 3: Be aware of .NET requirements
Depending on your target version number, you may need to install newer versions of .NET in order to take advantage of new features. For example, the Chromium spy mode introduced in 7.5 requires .NET 8 or above on all target devices. Again, the lesson here is to make careful note of the Upgrade Notices for your chosen upgrade path and ensure the necessary hardware / software requirements for are considered as part of the upgrade project.
Lesson 4: Pay particular attention to browser based automations
The way that Blue Prism Enteprise interacts with browser-based applications has changed substantially over recent years, and you may find a need to respy certain browser based elements if you're making a significant leap across version numbers. We recommend:
