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

Dynamic content in message rule is not consistent

SA-10372

Summary



The dynamic content (passed as a MessageKey parameter) mentioned in the message rule does not maintain its correct position and the output message is incorrect.

Error Messages



Not Applicable

Steps to Reproduce



1. Use a message rule in the Message Key in History-Add method. The message rule is being evaluated by the getRuleMesssage function
2. Observe that the dynamic content in the output is not in a correct position


Root Cause



The Message given by the user has three parameters with datatype as text for each one of them. But the text datatype is used only for the last parameter. The text includes tab characters. Supplied text is copied without processing into the message. During runtime it is unable to resolve the message property which results in inconsistency.

Resolution



During the creation of message rule parameters, text datatype must be used only for the last parameter. If text datatype is given for a parameter, supplied text is copied without processing into the message. During runtime it is unable to resolve the message correctly, resulting in inconsistency.

Change the datatype to name.

Published June 22, 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