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

CreateMergeWordDoc searches the wrong correspondence type



According to the help article here (
the final key part of the correspondence rule must be Email.

However when including a correspondence rule in a word template, the merge fails, because the flow action searches for "Mail" type correspondence as against "Email".

Error Messages

Status fail
Message Failed to find instance PegaSample-CustomerRequest.mycorr.Mail of type Rule-Obj-Corr.
Operator ID [email protected]
Requestor ID H1B12F28EA648A270A7E9CA850CAECF2F
Timestamp Fri Feb 20 15:33:55 EST 2015
Engine Version PegaRULES 7.10 ML7 (coreAssemblyCached_717_644)

Steps to Reproduce

1) Create word template document and upload blank document utilizing field codes.
2) Incorporate correspondence with email key type into document template and use.
3) Set up the createmergedworddoc flow action and then run and submit flow action using created template.
4) Perform step 3 again, with working template derived from WordMacroManagerDot and attach it to a work object.
5) Open attached document

Root Cause

The root cause of this problem is an error or omission in product documentation. Document incorrectly states, that the correspondence rule should be of type "Email", instead it must be type "Mail".


Mentioned document will be updated to reflect the behavior of the product. Also, enhancement request has been raised to accommodate all correspondence types.

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