Question
Finansinspektionen
SE
Last activity: 8 Dec 2022 21:28 EST
Doing Save As of a Rule opens in pop up
When i am doing a save as of a rule ( Any rule Type) it opens the rule form in a pop up with rule form data ( XML) . Its not showing the pega UI .
If i try to save as second time it works and i can see Property Creation/Section/Product file form.
Did anyone else face this issue and if so, how was it fixed.
Pegasystems Inc.
GB
Finansinspektionen
SE
Hello @MarijeSchillern
We are using V8.6 . We upgraded from 8.5 to 8.6 . This was a fresh installation so there were no previous versions of Pega and we have Pega Govt Platform FW .
We dont have any custom rule type. Issues happens for most of the rule type when we create or do a save as.
I have seen this pop up when i create/Save as a Rule Type (Product file or Property or Section or Harness) .
I don't see any errors or Warning in logs .
Pegasystems Inc.
GB
@SarathPrashanthC do you also notice any performance issues when Saving rules?
I would advise you that it is probably better to log a support ticket for this as likely an engineer will need to analyze your log files and check the application ruleset stack.
If this is a Dev environment please Enable "CustomDeclarativeRule" to Debug and reproduce scenario and reset the logger to error. Collect the logs and screenshots of the symptoms and full steps to replicate and log a support ticket.
AreteansTech
AU
Hello. We too are facing a similar but intermittent issue. Were you able to find out the cause/fix the issue? Thanks in advance.
Cheers,
Lahiru.
Hello @SarathPrashanthC
Can you confirm the Pega version used?
I can see reference to "pyRuleFormStatus" in your example - did you migrate a Pega class that uses the type "Form" ("Rule-File-Form".) to display the class?
If so the “Form” rule displayed as XML in Designer Studio is an expected behavior.
The “Form” ruleform type still exists in Pega 7.3.1. This is in case clients carry legacy rules over from old releases. If Pega completely remove it, it will cause some forward compatibility issues.
Form based rules are totally deprecated. Deprecated means no longer supported.
Please check below the ML9 release notes for “End of support for form-based rule forms in Pega 7.1.9”.
https://community.pega.com/knowledgebase/release-note/end-support-form-based-rule-forms-pega-719
Also see:
https://community.pega.com/sites/default/files/help_v731/rule-/rule-file-/rule-file-form/main.htm
Are you able to use Standard Harness and Sections for these rules?
More:
If this is not the solution could you give us some more details and the context of when exactly this error appears?
Hello @SarathPrashanthC
Can you confirm the Pega version used?
I can see reference to "pyRuleFormStatus" in your example - did you migrate a Pega class that uses the type "Form" ("Rule-File-Form".) to display the class?
If so the “Form” rule displayed as XML in Designer Studio is an expected behavior.
The “Form” ruleform type still exists in Pega 7.3.1. This is in case clients carry legacy rules over from old releases. If Pega completely remove it, it will cause some forward compatibility issues.
Form based rules are totally deprecated. Deprecated means no longer supported.
Please check below the ML9 release notes for “End of support for form-based rule forms in Pega 7.1.9”.
https://community.pega.com/knowledgebase/release-note/end-support-form-based-rule-forms-pega-719
Also see:
https://community.pega.com/sites/default/files/help_v731/rule-/rule-file-/rule-file-form/main.htm
Are you able to use Standard Harness and Sections for these rules?
More:
If this is not the solution could you give us some more details and the context of when exactly this error appears?
Are these rules related to a custom rule type, or a ruletype introduced by a Pega framework/strategic application? If so can you check the Ruleset version and test to see if you need to unlock a FW rsv and change ruleform from 'form' to 'harness ( then relock rsv)
Did you check the pegaRULES and ALERT log entries the moment you try to save the rule for the first time to see if the error gives you any more information?