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

Wrong Template for Modal Dialog triggered from Navigation Rule

SA-12066

Summary



User has configured local action as an onclick event for an item in Navigation rule. In this local action they have configured the action to open in modal dialog and they had mentioned custom modal template name.
But at runtime PRPC is using the default pyModalTemplate only instead of using the custom modal template.

The same custom modal template is running properly when I used it for Button onclick event local action. 


Error Messages



No error Message, but pyModalTemplate will always be used, no matter what Template is configured.

Steps to Reproduce



1. Create a navigation rule with onclick event as local action.
2. configure the local action such that open some flow action in modal dialog and use some custom template instead of default pyModalTemplate section.
3. Use the Menu bar control to display the navigation menu on screen at runtime.
.

Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules pyOverrideTemplate parameter not passing for menu generation.
Need to add "pyOverrideTemplate" parameter in menu generation code

Resolution



This issue is resolved in new release PRPC 7.1.8
 

Published July 14, 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