The calculation between cases, defined in the calculation tab of the case type rule, is not working for case specialization. I am using Pega version 7.1.9.
I have the following case structure
Level1, Level2 and Level3.
Level3 is a child of Level2 and Level2 is a child of Level1
All the calculations are performed at Level3, moved to Level2 and then to Level1. The calculations are working fine for base case structure but when Level2 case is specialized, then the calculations are not moving from Level3 to Level2, Tried deleting "pyCaseTypeAggregates" trigger and re-saved case type rule but no success.
Can someone please confirm whether there is an hot-fix else we need to write our own custom activities.
Thanks in advance
***Updated by moderator: Lochan to add Categories***
I could see the similar behaviour inhouse. In the below screen shots : prop1 , prop2, prop3 were initialized to 30,20,10 respectively, via setProperties on a connector.
Using the calculation tab on the case , performed prop2=prop2+prop3, and prop1=prop1+prop2
Hence the final value of prop1=60.
I am able to see the value 60 to prop1 intially, but once the Level2 is specialized, prop1 is getting displayed as 50.
other observation :
1)Even after removing the specialization, I could see the same behaviour.
Only the behaviour is proper , before specialization has been performed.
2)Could see the same behaviour in latest version of prpc as well. So I don't think there is a hotfix available. I will check if this is bug or not, and update you.
Posted: 5 years ago
Posted: 23 Mar 2017 3:43 EDT
Pankaj Rawal (rawap)
Senior Software Architect, Low-code
When you say Calculation not working after specialization, does that mean property changes in specialized Level 2 case are not getting calculated OR property changes in regular Level 2 case is also not working after specialization ?
OOTB case management does not support calculations for specialized cases (you can check the same in Calculations tab in specialized case type) .
If it is the other way around, then go ahead and raise an SR for the same.
Posted: 5 years ago
Posted: 29 Mar 2017 12:02 EDT
Kiran Kumar (KIRAN_KUMAR)
Lead System Architect