Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Checkout and SaveAs are not working for Flow rules



After performing upgrade to the application from PRPC 6.2 SP2 to Pega 7.1.9. All rules got upgraded.

However when revalidating and saving the flow rules, developer is getting errors even though rules are in draft mode. 

Same rules were saved successfully in PRPC 6.2 SP2.  Developer has issues while doing checkout and save as of Flow rules after upgrade. 

Also, when developer creates new flow rules, check in and check out options are not displaying.

Error Messages

Field cannot be blank.

Steps to Reproduce

1. Create some draft flow rules in PRPC 6.2 SP2 with some required fields missing, for example Utility without activity and so on.
2. Do upgrade from PRPC 6.2 SP2 to Pega 7.1.9.
3. Same rules giving errors in Pega 7.1.9 though those are in draft mode.
4. Try to checkout or save as the flow rule.

Root Cause

The "-" in the edit validate rule name (CaseMatch-Value0to100) is being treated as a operator which is causing the issue and hence after changing the edit validate rule name to casematchvalue0t0100 fixed the issue  


Perform the following local-change: 

Try to Save Data-MO-Connector-Transition Validate(Rule-Obj-Activity) into the custom Ruleset with following changes. That is, change the name of the validate to validate123

In the validate123 change the validation condition CaseMatch-Value0to100 to CaseMatchValue0to100 but before doing this do saveas the original CaseMatch-Value0to100 to custom ruleset and change the name as shown below

The above changes resolves the issue.

Published May 19, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us