Hello Jasper,
The problem with application upgrades is it has always been considered a services engagement, so the process isn't well documented out with a step by step guide. To further complicate things, each business partner has their own set of processes and tools for doing application upgrades. None of the partners really share their processes and tools because it is considered their "Secret Sauce" so to speak versus their competitors. Your best bet is to engage a partner to assist, at least for your first upgrade. Learn as much as you can during that process and maybe you'll be able to do the next upgrade on your own. Here is a high level overview of the process:
- Overlay your target upgrade environment with the latest copy of your production environment.
- Platform Upgrade that environment by running the installer and pointing it to the environment.
- Identify all the customized objects in your environment.
- Get the upgrade OM Package for your version and identify all of the objects in the OM Package.
- For the objects that are in both sets, you have to manually merge the functionality as importing the OM Package would overwrite your customizations.
- Objects that you've customized but are not in the Upgrade OM can be ignored.
- Objects that have changed by the product team that you didn't customize as well as new objects can be imported.
- Once all objects are upgraded, build new OM Package(s) of the objects involved so that the next level environment can be upgraded. At this point its like another dev release. Test, identify bugs, fix, rebuild OM Package, redeploy, repeat.
Identifying the differences in the objects so that you can manually merge can only be done using the built in comparison tool or proprietary tools like my text exports. The comparison tool however only performs a shallow level comparison and stops at the first level of change. So you have to keep doing iterations of compare until you have made all of the changes. You can not use the built in comparison tool for workflows as it only compares the start task of the workflows. You can text export the different workflow versions and then use a comparison tool to see the differences. Be aware that the workflow text export does not sort the mappings, so you are bound to end up with a lot of false positive differences. You will want to manually edit the text exports and sort the mapping lines before you compare so that you can see true differences.
One final point. The best way to make your upgrades easier and faster is through the use of proper naming conventions and object label usage. This is especially true for naming convention usage within workflows. I've written several articles over the years that you can find on my LinkedIn page. Also, whenever new versions of TRIRIGA are released, I'll generally go through them and compare them to the previous version by using my proprietary text exports. I'll then post about some of my findings on LinkedIn as well as X. I am currently in the process of doing this for the new 11.6/5.0 version.
Best of luck with your upgrade!
--Mark
------------------------------
Mark Johnson
Senior Architect
Wipro
Bentonville
7025088528
------------------------------
Original Message:
Sent: Sun October 13, 2024 08:58 PM
From: Jasper Chin
Subject: How to perform Tririga application upgrade
Is there any documentation or guidelines that can guide us on how to perform the application upgrade and what the prework is that we would need to take note of before upgrading the Tririga application? It is our 1st time performing the application upgrade and it is a challenge as we are exploring without any directions.
------------------------------
Jasper Chin
------------------------------