Issue in Rule Resolution - Does not pick the correct Rule at RunTime
Hi All,
Please help on issue which we faced in Production environment and kindly provide a solution.
Scenario - When user perform Get Next Work, we have modifided the activity to add the party to the case. Due to some reason application picks PEGA OOTB rule at runtime (this is not happend everytime). Because of that party is not added to the case and this will cause an inconsistent in some Reports which used by Managers.
Attempeted Solution - We have noticed that this rule is not cached properly in few nodes. So we have Reassemble the Cache through SMA and Save the operator again. After that it worked for him for sometime, But again issue occured.
This has been a critical issue in Prodcuction. Appreciate your help at earliest.
Thank You!
Jayami Dayarathna
***Moderator Edit: Vidyaranjan | Updated Categories | Added SR details***
***17/10/2017: Updated by moderator: Lochan to close post***
EvonSys (Pvt) Ltd
SG
Hi Swarnendu,
Application does not pick up the correct rule. It does not happened everytime. But everyday 3-4 cases affected with the same. We have thought this is the cache issue that is the reason we reassemble it. But did not solve the issue.
Kind Regards,
Jayami Dayarathna
BUPA
AU
It could be possible that draining is happening at the backend due to cache size settings. Pls check the log files to get any pointer. It's better to raise an SR or get in touch with Pega GCS.
Pegasystems Inc.
IN
Hi Jayami,
Please let us know if you do log an SR for this and its ID. That way we can track it and follow-up this discussion with the resolution.
Thank you,
Pegasystems Inc.
IN
Hello,
On reviewing the SR, we see that it was marked closed since the issue was not reproducible on production system. Please reopen the SR once the artifacts to support investigation are collected.
Regards,