Support Article

Rule Check in and Delete fail with "none matched this request"

SA-23776

Summary



When a developer does a rule check-in or delete, it fails with the error : .Failed to find a 'RULE-OBJ-FLOW' with the name 'CHECKINMODALFLOW' that applies to '@baseclass'
 


Error Messages



Errors while doing Check in:
1).Failed to find a 'RULE-OBJ-FLOW' with the name 'CHECKINMODALFLOW' that applies to '@baseclass'. There were 8 rules with this name in the rulebase, but none matched this request. The 8 rules named 'CHECKINMODALFLOW' defined in the rulebase are:
8 related to applies-to class '@baseclass', but were defined on subclasses: {Work-ProjectManagement-CheckIn, Rule-}.
2).Failed to find instance @baseclass.pyModalFlowTemplate of type Rule-HTML-Section.

Errors while doing delete:
1). Failed to find a 'RULE-OBJ-FLOW' with the name 'DELETEMODALMAINFLOW' that applies to '@baseclass'. There were 6 rules with this name in the rulebase, but none matched this request. The 6 rules named 'DELETEMODALMAINFLOW' defined in the rulebase are:
6 related to applies-to class '@baseclass', but were defined on subclasses: 'Work-ProjectManagement-Delete'.
2). com.pega.pegarules.pub.PRRuntimeException: Failed to find instance @baseclass.pyModalFlowTemplate of type Rule-HTML-Section.
3). Failed to find a 'RULE-OBJ-WHEN' with the name 'ISDISPLAYINTRANSACTIONCURR' that applies to 'Code-Pega-List'. There were 2 rules with this name in the rulebase, but none matched this request. The 2 rules named 'ISDISPLAYINTRANSACTIONCURR' defined in the rulebase are:
2 unrelated to applies-to class 'Code-Pega-List', for example: 'AEXP-FW-GD-Data-FinancialAction'.


Steps to Reproduce



1) Open any checked-out Rule.
2) Check in or delete a rule.


Root Cause



An issue in the custom application code or rules ;

Developer customized ApplicationProfilesetup activity application rule set. First step of activity is Page-Remove and it is removing Application specific user pages and pyDisplayHarness and pyWorkPage

For Check-in, check-out and delete internally flow gets executed Which is present in Work-ProjectManagement- class.

During Check-in and Check-out process pyWorkPage is created and used to do flow processing.

System is throwing error because pyWorkPage is removed.

After removing step to delete the pyWorkPage developer is able to check-in, check-out and delete rules. 

Resolution



Here’s the explanation for the reported behavior:

pyWorkPage is removed after application setup activity. 

After removing step to delete the pyWorkPage, developer is able to check-in, check-out and delete rules.

 

 

Published June 4, 2016 - Updated October 8, 2020

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.