Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Troubleshooting: CPM dialog messages do not refresh on Service Intent confirmation screens

Updated on September 25, 2019

Using CPM 7.1 Release 2, users working with Service Intent tasks see dialog messages refreshed for flow actions and assignment changes, but not for harness changes. Dialog rules do not refresh properly on the confirmation screen.

Example

You perform an Address Change intent, which displays a confirmation screen before closing the Intent tab.

While you update the caller’s address, the defined dialog message is “What changes would you like me to make to the address we have on record?”

The defined dialog message for the confirmation screen is “Thank you. I have updated your address as requested.”

When you advance to the confirmation screen, the dialog does not refresh. You still see “What changes would you like me to make to the address we have on record?"

Explanation

Customer Process Manager (CPM) dialog messages are refreshed by the triggering of events. You experience the problem described if you have designed a custom harness associated with a Service Intent flow that omits the scripts needed to trigger dialog message events.

Suggested approach

When you customize CPM, be sure to include the section rule CAConfirm_ActionSection within a flow action, section, or other UI rule that loads when refresh of a dialog message is needed. The CAConfirm_ActionSection rule triggers the appropriate event to refresh the dialog message.

CAConfirm_ActionSection included in UI Layout to refresh dialog

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us