flow Rules not opening properly
Unable to open flow rules -- PFA screenshot.
Tried restarting server, Browser cache cleaning as well.
***Updated by moderator: Lochan to tag SR to post***
Pegasystems Inc.
US
Can you do a private checkout of the Rule-Obj-Flow.RuleFormLayout section to see if that changes the behavior?
Pegasystems Inc.
US
You will probably need to open an SR so someone can look at it on your system. I suggested the private edit in case it was a cache issue with the section but that does not appear to be the case.
Pegasystems Inc.
US
Please reply back with the SR ID once you open it so that we can track for you!
Thanks @CarissaW_GCS!
EPAM Systems, Inc.
ES
Hi PratikK2,
Thanks for posting on PSC.
I have verified the screen-shot shared and initial root cause could be CSS associated with the rule form were missing from the database. As expected, there should be 3-4 CSS files generated which could be observed in the developer tool of browser as well but in your case, there could be only one available. Like this:-
pzharnessv2_ruleform94f2d7a58a9cbb61846b42ed08982de421a30fa4ad7a98f830e18a71ead326ca_0--1
Re-generation of CSS is necessitated alongwith reassembling of skin rule. I would've recommended "Revalidate and Save" but it couldn't be done for OOTB rules. It's a process equivalent to explicitly performing opening of a rule and saving. While saving every rules go through a validation as well.
Similar issue is reported under SA Article,
Suggestion:-
1. Perform a private edit of the activity @baseclass • BulkValidateSave.
2. In the second step of Obj-Open-By-Handle, uncheck Lock and release on commit options.
3. Run the activity.
4. Put the pzInsKey of the Designer Studio skin in the parameter.(pzDesignerStudio applied to the developer portal).
5. Execute the activity.
6. Log out , clear cache and log back in.
Hi PratikK2,
Thanks for posting on PSC.
I have verified the screen-shot shared and initial root cause could be CSS associated with the rule form were missing from the database. As expected, there should be 3-4 CSS files generated which could be observed in the developer tool of browser as well but in your case, there could be only one available. Like this:-
pzharnessv2_ruleform94f2d7a58a9cbb61846b42ed08982de421a30fa4ad7a98f830e18a71ead326ca_0--1
Re-generation of CSS is necessitated alongwith reassembling of skin rule. I would've recommended "Revalidate and Save" but it couldn't be done for OOTB rules. It's a process equivalent to explicitly performing opening of a rule and saving. While saving every rules go through a validation as well.
Similar issue is reported under SA Article,
Suggestion:-
1. Perform a private edit of the activity @baseclass • BulkValidateSave.
2. In the second step of Obj-Open-By-Handle, uncheck Lock and release on commit options.
3. Run the activity.
4. Put the pzInsKey of the Designer Studio skin in the parameter.(pzDesignerStudio applied to the developer portal).
5. Execute the activity.
6. Log out , clear cache and log back in.
Hope it resolves issue at your end, kindly revert back with your observation and accordingly update this post.
Regards,
Asif
VSSI
IN
I tried doing the same. My Application was referring to AppSkin Skin rule and i gave its pzInsKey as parameter in the said activity. But it Didnt Work. It will be helpful if you can give any other suggestion.
PEG
US
Try opening the Developer Toolbar (F12) and going to the console. Then try again to open the flow rule. See what errors (if any) show up in the console.