Question
Iffco Tokio General Insurance
IN
Last activity: 29 Jul 2025 7:36 EDT
Cannot save a rule in branch ruleset.
I am unable to save a rule in same branch. Branch is created in Higher application hierarchy then even not able to save the rule referenced in same branch and created in lower stack.
Getting below error: "ITGIUWUtilities.DigitalSignedPDF--(String)" exists, but may not be used by this rule due to the ruleset’s validation mode and/or your current application context.(found Rule-Utility-Function ITGIUWUtilities.DigitalSignedPDF--(String) in ITGIUWFW_Branch_ClientPortfolio:01-01-01)
Accepted Solution
Updated: 28 Jul 2025 23:32 EDT
ai4process ltd
GB
You can't directly create or compile a new function within a branch ruleset for execution.
Any new "Rule-Utility-Function" you develop needs to reside in your application's main rulesets, not a branch. This is crucial for the system's rule assembly process to properly recognize, refer to, and execute the function.
Please create or move the 'DigitalSignedPDF' function into an application ruleset, then regenerate the library or function to ensure it can be tested and utilized correctly.
Publicis Sapient
IN
Hi @Dev.Pega007,
You're getting this error because the rule you're trying to use is in a branch ruleset from a higher-level application, but your current application (lower in the stack) doesn’t have access to it.
This happens due to Application Validation mode, which restricts rule referencing unless both rules are in the same app context or allowed ruleset list.
To fix it, make sure the branch ruleset is added to your current application's ruleset stack under Application > Definition > Application rulesets.
Updated: 28 Jul 2025 1:48 EDT
Iffco Tokio General Insurance
IN
Thanks @PoojaPalla
We have tried saving the same rule in RSV and again saving main activity rule created in branch and checking in.
Then we deleted the RSV saved rule and again restored branched rule. Now we are not getting error.
This could be one work around, but I'm still not understanding that how pega is not throwing same error again as rule still resides in same fashion.
Publicis Sapient
IN
Hi @Dev.Pega007
If you've already added the branch ruleset and are still facing the issue, please ensure the branch ruleset is placed above the referencing ruleset in the stack. Also, confirm that your application is in Application Validation mode, and that the referencing ruleset includes the branch or base ruleset as a prerequisite. Make sure the operator’s Access Group points to the correct application version. Lastly, use Tracer or Live UI to check if the correct rule is being picked and that it's not blocked or withdrawn.
Accepted Solution
Updated: 28 Jul 2025 23:32 EDT
ai4process ltd
GB
You can't directly create or compile a new function within a branch ruleset for execution.
Any new "Rule-Utility-Function" you develop needs to reside in your application's main rulesets, not a branch. This is crucial for the system's rule assembly process to properly recognize, refer to, and execute the function.
Please create or move the 'DigitalSignedPDF' function into an application ruleset, then regenerate the library or function to ensure it can be tested and utilized correctly.
Iffco Tokio General Insurance
IN
Thanks @RaviChandra
Yeah, I have tried it and that's why after creating function in one of RSV it worked in referenced rules. But it was still working even after deleting the RSV rule and then again referencing function rule saved as from same RSV rule in one of branch.
It was due to rule cache or something?
ai4process ltd
GB
When you save a function in the application's ruleset and generate the function, a Java class will be created and stored in the Rule Assembly Cache and all the rules referring would work as expected. However, when you delete the function from the application, any new rules you create, or when you do a environment restart, you would still find the same error.
Its a practice to always create and generate libraries and functions in application's rulesets and not branches.
Iffco Tokio General Insurance
IN
Thanks @RaviChandra for explanation.