Is it possible to reuse & extend OOTB stages and processes using case designer in Pega7?
e.g. This screenshot is from Pega's Appeals and Grievance framework. We like to reuse and also, as needed, extend the OOTB stages & processes into a customer built framework and customize. We will then customize further in each IMPL layer .. preferably all using Pega7's case designer.
In the end, our goal is to have our team members to use Pega's Case Designer to reuse/extend OOTB stages/processes, which I assume is a best practice in managing cases in Pega7 (rather than having to change individual rules like flows).
Stage is nothing but logical group of processes. If you want to customize the case, you need to create case with same name in implementation layer or If you want to customize the processes you need to customize the flows individually in implementation layer
Posted: 6 years ago
Posted: 16 Sep 2016 7:23 EDT
Will Cho (Will Cho)
Principal System Architect
Just did a POC to verify. Once the FW case type rule is extended at the IMPL layer, any new stage or process change at the existing FW case type rule can't be reused anymore. This is a consistent behavior from overriding just like any other rule type.