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

Connect-MQ sends special / unreadble characters in MQ messages



Connect-MQ sends special / unreadble characters in MQ messages. Under 'Request' tab of the Connect-MQ rule datatype is set as 'string'. Connect-MQ sends the XML of the Work Object as MQ Message.

Error Messages


Steps to Reproduce

  1. Create Connect-MQ 
  2. Open the work object in an activity rule
  3. Set XML of the work object as request for the Connect-MQ
  4. Set the Request datatype as string in Connect-MQ
  5. invoke the Connect-MQ and check the message on MQ side.
  6. notice that message has special characters, that was not seen in PRPC side.

Root Cause

Recommended datatype setting for this configuration is the 'allchar' as datatype for the Connect-MQ request setting


Instead of 'string' use 'all char' as datatype for the Connect-MQ Request setting. 

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

100% 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