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

Custom buttons added by Possible Choices property do not render



Custom buttons which are added to workflows through "Possible Choices" property are not rendered on processeFooter.jspx screen.

Error Messages

Not Applicable

Steps to Reproduce

Invoke Example Interaction Flow from the ccagent desktop and verify the buttons on the second screen (displayAccountEntries.jspx).

Root Cause

JSTL xmlns namespace in processFooter.jspx are pointing to incorrect URL. Ideally it should be pointing to xmlns:c="".


Apply HFix-903. It is suggested to configure BA Environment first and then to configure JSF2.1.0. This will ensure that JSTL core namespaces are pointing to the JSF 2.0 specification. 

 Below is the recommendation mentioned in Chordiant_JSF_6.8.pdf which is delivered as part of the HFix-903.
The JSTL core tags should point to JSF 2.0 specification. Change the JSTL core namespace for JSF 2.0 support from xmlns:c=” to xmlns:c=”

Published November 19, 2015 - 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