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

FixCorrespondence – ResendCorr problem when no Party Role



FixCorrespondenceResendCorr does not work for email correspondence generated from the 'Send Email' smart shape in a flow. This occurs when the correspondence does not use a Party Role.

Error Messages

No Role Defined to work object

Steps to Reproduce

  1. Create a correspondence template
  2. Create a flow, which uses the 'Send Email' smart shape to send to an email address (not a party).
  3. Set a hard-coded error (for example, set invalid host) in the Data-EmailAccount instance used by the correspondence ('Default/Notify').
  4. Run the flow to generate correspondence, which must be routed to the FixCorrespondence flow.
  5. Fix the hard-coded error in Data-EmailAccount.
  6. Set the Tracer on for the Work-.CorrUpdate activity.
  7. Use the 'Resend Correspondence (ResendCorr)' flow action to attempt a resend.
  8. View the trace. Step 7 role validation requires that the pyCorrPage must have the .pyCorrPartyRole property be populated.

Root Cause

A defect in Pegasystems’ code or rules.


Apply HFix-39667.

Suggest Edit

Published December 18, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

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.

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