Can you run all patch helpers (10.3 to 10.5.2) after final OM import?


We have upgraded the TRIRIGA platform to 3.5.2.3 and started upgrading the application from 10.2 to 10.5.2 in incremental order (10.3, 10.3.1, until 10.5.2). To minimize the outage and complexity during production implementation, we have been suggested to take a final OM package after completing 10.5.2 deployment, and apply all the customizations which might have been impacted with the upgrade. This final OM package will contain all the changes from 10.2 to 10.5.2.

Our question is on the patch helpers: Can we run all the patch helpers (from 10.3 to 10.5.2 in order) after importing the final OM package?

Also, we are running the Varchar-to-Numeric script before importing the application upgrade packages. This script is taking a long time (almost a day in two test environments), but when we tried in another environment, it’s running for more than 2 days and still didn’t get executed. Is it normal for this script to run like that? Or will it be an issue? There are no differences between the environments.

I wouldn’t recommend doing the upgrade in one package. Usually, it ends up being quite large and it will cause issues. The IBM-recommended way is to perform each OM, then run the patch helpers. Once you have upgraded the OOB OM packages, you can have one OM which has your custom objects…

[Admin: This post is related to the 10.25.17 post and 04.28.17 post about running “SetVarcharColsToNumeric” scripts. To see other related posts, use the Scripts tag.]

Continue reading

Which TRIRIGA 10.4.0 patch helper file should you run?


When upgrading the TRIRIGA application, the customer is requested to import the Patch Helper records. The folder where they are located contains 2 files: PatchHelper_10_4_Federal.txt and PatchHelper_10_4.txt. The TRIRIGA upgrade wiki is not clear about the PatchHelper_10_4 files. So it’s not clear if both need to be run, or the order they should run.

The “PatchHelper_10_4_Federal.txt” file is for Federal customers only. That means if you are not a federal government or your business is not associated to the federal administration, you should run “PatchHelper_10_4.txt” only. If you are a federal customer, run the “PatchHelper_10_4_Federal.txt” file only.

Continue reading 

Reducing process time for TRIRIGA 10.3.x to 10.4.x upgrade


The mapping task of the triPatchHelper – triCalculate – 10.3.2 – Retro Contract to Set Payment Timing patch helper workflow is configured to use the results of a query for all Contract results for both Map To Records and Map From Records information. The Map From Records information can consist of a single record because each Map From Records entry updates each Map To Records entry.

When upgrading from IBM TRIRIGA10.3.x or earlier to IBM TRIRIGA 10.4.x using the 10.3.x patchhelper, change the Update Payment Timing modify task of the triPatchHelper – triCalculate – 10.3.2 – Retro Contract to Set Payment Timing workflow. Update the modify task Update Payment Timing by changing the Map From Records task to use the Start task instead of the Get Existing Contract query task.

Continue reading 

Working with the triPatchHelper business object


Charlie McGarvey: Often you will find you need to run utility Workflows to update data. To follow IBM’s protocol is to use the Business Object triPatchHelper. The idea is you create a Utility workflow and trigger the workflow by creating a Data Integrator file with triNameTX. The start condition for the Workflow would be triNameTX=”Fix Project Data”.

Probably like most developers, the chances of your Workflow being perfect the very first time is highly unlikely. What you will find is when you upload your subsequent data integrator files, is the workflow won’t fire. That’s because the Publish Name is triNameTX. You don’t want to change your Data Integrator file and the start condition of the workflow with each and every revision. I suggest searching and adding triControlNumberCN to the triPatchHelper Business Object. Change the Publish Name from triNameTX to the Control Number field.

[Admin: You need a Facebook login to open the TRIRIGA Around the World link.]

Continue reading

Upgrading from TRIRIGA 10.3 to 10.4.1


Mani Sanjeevi: Is anyone planning to do an Application Upgrade 10.4.1 from 10.3? To upgrade from TRIRIGA version 10.0 and TRIRIGA Application Platform version 3.0, you must upgrade TRIRIGA, TRIRIGA Application Platform, apply object migration packages, and run patch helpers. Check the release notes for the packages you are installing for details about new features and fixes for the release. Refer to the release version summary table for a summary of the TRIRIGA releases available.

[Admin: You need a Facebook login to open the TRIRIGA Around the World link.]

Continue reading