Recently in my application we deployed a suite of "production support tools" for our production support team. The aim behind them was to allow prod support to bulk process data remediation efforts.
For example, we deploy a workbasket routing decision table into Prod and there is a bug in it. As a result ~100 cases are in the wrong workbasket and must be moved. Normally this might be done case by case, or via some SQL on the backend, both of which are time consuming. So i made a cute little harness and now they just enter a CSV of cases and click "run." Everyone is much happier.
Everyone is so happy we're planning on deploying these tools into other PEGA applications within my organization. The problem is my application is in 7.2.2 whereas some of the other applications are in 7.1.8 and some others in 7.4.1.
What is the best strategy of synchronizing this code between applications so we're not literally recoding it for each version?
Congratulation for successfully making the "cute little harness" for your team.
If it is developed by using OOTB components like Harness, Section, Data transform etc, then moving it to 7.4 from 7.2 will not be a challenge. You can create a R-A-P for this rule and associated application and move it to 7.4
However, downgrading it to 7.1.8 might be bit challenging. If the redesign work does not cost much then you can think of redesigning it in 7.1.8
Posted: 3 years ago
Posted: 3 Jan 2019 14:05 EST
Mike Townsend (MikeTownsend_GCS)
Director, Technical Support, Customer Service
I agree with Santanu. Also, I'm not sure if you've looked at the out of the box bulk processing tools. While you don't get to use a handy CSV, you can definitely reassign items in bulk if need be. If there's already an out of the box tool that meets your needs, then you may not need to worry about maintaining your tool.