Question
Raytheon Technologies
US
Last activity: 3 Aug 2018 12:54 EDT
Best Practice for Optimized Properties
We have run into an issue where our customer would like to see property values that are longer than 32 characters in reports.
Found this article that explains why values with more than 32 characters are being truncated and how to update the database columns to solve the problem: https://community.pega.com/support/support-articles/full-description-not-displaying-particular-column
This article is a few years old and tagged with Pega Platform version 6.2. We are in the process of upgrading from version 7.3 to 7.4. Is there a better approach to solve this problem in the newer versions of the platform?
I expect that the columns for optimized properties are set to be VARCHAR(32) for a reason, is it a best practice to increase the size of these columns? Is there anything we should be cautious of when doing this?
Is there any way to specify the size when optimizing the property instead of having to go back and manually updating the database column after the property is optimized?
Pegasystems Inc.
US
32 characters was the original default Text column size. This has since been increased to 256 characters.
In the Data Type view you should define Properties then visit them before deciding to create a Local Data Source.
Open each Property that you want to size appropriately.
Click on the Advanced tab.
Change the "Column Inclusion" drop-down's value to "Required".
In the Max Length column enter the database column size.