Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C6181 · Issue 348042

pyGuideID size limit increased to 128 characters

Resolved in Pega Version 7.4

The Guides task progress was not updated when tasks status was modified and the guide name was more than 32 characters. This was due to column pyGuideID having a size limit of 32, causing the extra characters to be truncated. To resolve this, the column size of pyGuideID of pc_work_guide has been increased from 32 characters to 128.

SR-C6181 · Issue 347504

pyGuideID size limit increased to 128 characters

Resolved in Pega Version 7.4

The Guides task progress was not updated when tasks status was modified and the guide name was more than 32 characters. This was due to column pyGuideID having a size limit of 32, causing the extra characters to be truncated. To resolve this, the column size of pyGuideID of pc_work_guide has been increased from 32 characters to 128.

SR-C6182 · Issue 348515

Conditional binding added to handling literals in SQL

Resolved in Pega Version 7.4

Literal values were appearing in the the SQL against PR_SYSGEN_STATIC_CONTENT, causing the query to be reassessed every time on an Oracle system and adding a new entry to the shared pool instead of using a pre-existing execution plan. In order to reduce overhead on the database caused by non-bind values, conditional binding will be implemented if PRThread context exists.

SR-C6751 · Issue 349286

Corrected duplicate table names for DB2 z/OS import

Resolved in Pega Version 7.4

When using Explicit DDL generation for DB2 z/OS, auxiliary tables were generated with the same name when deploying on single schema deployment. This happened when importing archives that created tables in both the PegaRULES and PegaDATA logical DBs when those logical DB names corresponded to the same database schema, and was due to the handling of lob table names for single schema deployments using Pega DB logical names for storing the last generated index. This has been fixed by changing to tracking the last generated index by DB2 z/OS database name / database schema name in order to prevent PegaRULES and PegaDATA lob tables from having naming collisions.

SR-C6751 · Issue 349078

Corrected duplicate table names for DB2 z/OS import

Resolved in Pega Version 7.4

When using Explicit DDL generation for DB2 z/OS, auxiliary tables were generated with the same name when deploying on single schema deployment. This happened when importing archives that created tables in both the PegaRULES and PegaDATA logical DBs when those logical DB names corresponded to the same database schema, and was due to the handling of lob table names for single schema deployments using Pega DB logical names for storing the last generated index. This has been fixed by changing to tracking the last generated index by DB2 z/OS database name / database schema name in order to prevent PegaRULES and PegaDATA lob tables from having naming collisions.

SR-B56256 · Issue 335795

VBD cache handling changed to preserve data integrity

Resolved in Pega Version 7.4

When VBD was configured to use on-heap memory, no data was displayed in VBD planner and logs showed queries failing with ArrayIndexOutOfBoundException. The cause of the error was a corruption of VBD cache data in a partition: VBD compresses its partitions after getting no inserts for 15 minutes. When an insert is received by a compressed partition, the partition is first decompressed before writing. During decompression, the buffer position is set to the end of the uncompressed buffer. However, the buffer may include padded nulls added during buffer expansion. The system writes the new VBD records after the padded nulls, but the nulls would then throw off the read logic during query execution. To fix this, during decompression the buffer position will now be set to the end of the data, not the end of the buffer.

SR-B56256 · Issue 337432

VBD cache handling changed to preserve data integrity

Resolved in Pega Version 7.4

When VBD was configured to use on-heap memory, no data was displayed in VBD planner and logs showed queries failing with ArrayIndexOutOfBoundException. The cause of the error was a corruption of VBD cache data in a partition: VBD compresses its partitions after getting no inserts for 15 minutes. When an insert is received by a compressed partition, the partition is first decompressed before writing. During decompression, the buffer position is set to the end of the uncompressed buffer. However, the buffer may include padded nulls added during buffer expansion. The system writes the new VBD records after the padded nulls, but the nulls would then throw off the read logic during query execution. To fix this, during decompression the buffer position will now be set to the end of the data, not the end of the buffer.

SR-B67003 · Issue 329137

Enhancement added to validate mandatory fields in custom proposition definition forms

Resolved in Pega Version 7.4

Enhancements have been added in order to support extended customization of a proposition definition form. Previously, the custom form containing the custom fields was rendered in the context of a requestor-level, editable data page for creating a new proposition. The custom form section itself did not belong to the same class as the data page but was only rendered in the context of the data page at run-time. Therefore, validations defined on the custom form were not triggered due to the mismatch in the context of execution. The system has now been updated with an extension activity which will have the required-field validation pre-loaded. The same activity can then be extended to include additional validations whenever needed. The approach has some limitations as below. Process: On the custom form for the proposition group, the appropriate fields will need to be marked as required-always from the 'Required' dropdown field configuration form. After this, with the local fix branch included, new propositions should be validated for missing required fields. Limitations: The validation will work only on the manual creation of a new proposition. Conversely, the validation will NOT work if the propositions were uploaded using the Import/Export feature on the Decision Data form. The validation error messages for the custom fields will appear on the top of the page unlike that for the proposition name property. However, the message will list all properties that are marked as required but haven't been filled-in on the form.

SR-B72990 · Issue 326318

DataFlowGenerator class files preserved longer

Resolved in Pega Version 7.4

When creating a campaign, running the generated data flow manually resulted in an illegal argument exception indicating a null property name. This was traced to the use of an overwrite data flow API: class files were generated and removed immediately after the DataFlow object is constructed. In some cases, the java classloader may delay loading of the classes, causing the NoClassDefFoundException as files have been already removed. To resolve this, the DataFlowGenerator will now wait one day to remove the classes.

SR-B75057 · Issue 328508

CSV import of list segment fixed

Resolved in Pega Version 7.4

After upgrade, CSV import of a list segment in Pega Marketing was not working if the header name was "WorkEmail" in LMMS. This was due to a redundant call made to pxgetFilteredUniqueKeysListFromDB, and the code has been updated to correct this.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us