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

PegaFS-Data-Party-Shortname is limited to 20 positions



In the Pega Foundation for Financial Services (PFFS) Framework, the PegaFS-Data-Party-Shortname property is limited to 20 positions. As a result, the GET relation fails. This occurs when the Shortname is populated with the ShortCommercialName from Siebel which can be up to 35 positions long.

Error Messages

Not Applicable

Steps to Reproduce

Create a DateTransform to map a field of 35 positions to PegaFS-Data-Party-Shortname.

Root Cause

The ShortName property length was changed between versions.


Here's the explanation for the reported behavior:

The restriction is added in accordance with the corresponding database table definition. Since this is the short name, the restriction is enforced to not more than 20 characters.

If this restriction is removed, it causes incorrect results or data being saved to the database because it does not comply with the table definition.

Since the implementation must be overridden with respect to the system of record, the property must be updated at the user end with the restriction set to that definition which complies with the user's table.

Published August 19, 2019 - Updated December 2, 2021

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