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

Rule name not getting displayed properly on app explorer



Customer did installation of PEGA716 split schema ,after successful installation, customer is facing this issue.Basically when they are creating any New rules and want to see them on App Explorer they found that instead of label it is showing the complete input parameter. For example, if they create a flow name "SampleFlow" in the application explorer they are seeing that it is appearing as " pyStartCase&pxObjClass=Rule-Obj-Flow&pxInstanceName=SampleFlow"

Error Messages


Steps to Reproduce


Root Cause

The root cause of this problem is a defect in customer application code/rules. A number of weird issues were faced post installation. The installation stpes were customized particularly the DB Users did not include ANY privileges. Further the SQL for rulebase setup was generated manually. However this was not reproducible inhouse. The same installation was tried thrice and not once did we face any issues. Perhaps the SQL scripts were not executed properly - although no errors were shown in the database we suspect that a stored procedure (most likely a trigger) was not compiled properly, whicj also reflected the kind of problems the customer faced.

Since PRPC installation is straightforward, it was suggested that we re-install while following the steps carefully.


This issue is resolved by performing re-installation of PRPC.

Published January 31, 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