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

Trailing extra space in correspondence rules

SA-30844

Summary



To remove the Extra Space which gets appended after the city field (Customer Table Data from DB) in the correspondence Rule.

As it can be noticed, there is a space after each field, which is not acceptable by business.

The DB has the data without spaces, so in some of the OOTB rules (mostly final rules, the spaces are appended to the data)

Error Messages



Not applicable
 

Steps to Reproduce



Issue is suppose the Treatment Rule has:

Address:
Sprint store
<<.Customer.STORE_ADR_LINE_1_TXT>>
<<.Customer.STORE_CTY_NME>>,
<<.Customer.STORE_STATE_CD>><<.Customer.STORE_ZIP_CD>>

Output is:

Address:
Sprint store
6480 Sprint Pkwy
Overland Park , KS 66251

Root Cause



A defect in Pegasystems’ code or rules In correspondence rule, when engine resolves the stream and replaces the <<property>> with its value at runtime, it always appends a ' ' (space).
This has been the behavior since the inception of stream rules.

Resolution



Use format = "Scalar" so that engine will not add extra spaces.

For example:

<pega:reference name=".pyWorkParty(GCS).pyFullName" format="Scalar"></pega:reference>

Published December 1, 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