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.

INC-145802 · Issue 636324

Oracle temporary space explicitly freed after writing LOBs

Resolved in Pega Version 8.5.4

Oracle temporary space used to write the LOB was not freed up after writing records to Log-Service-File when using OJDBC8 or OJDBC10 versions and the table involved had inline BLOB storage such as small blob tables like Log-service-file (2-4kB blobs). This did not occur when using OJDBC7, but investigation with Oracle could not determine why the older version did not have this issue. This issue has been resolved by explicitly freeing the LOB space with a call to free() / freeTemporary() , a utility for LOB objects that was introduced in JDBC 4.

INC-154026 · Issue 631041

Resolved exception from expanding deserialized Data Page

Resolved in Pega Version 8.5.4

When using a data page backed by a report definition where the data page data type was Rule- and the virtual page data type was Rule-Obj-Property, serializing and deserializing the data page and then expanding the deserialized data page generated the exception "the reference .pzInsKey is not valid. Reason: .pzInsKey is mapped to class Rule-Obj-Property, which is not the primary class of the list: Rule-; must specify a group name in mapping". The issue occurred only if "Run on Data Page" on the data page was checked and "Report on descendant class instances" on the report definition was unchecked, and has been resolved by updating the runLoadActivity() of DeclarativePageDirectoryImpl to skip setting pyObjClass for the report definition if it already present, i.e. if already set by the loader activity.

INC-155624 · Issue 634716

MSGraph email listener enhancements

Resolved in Pega Version 8.5.4

Attachments with .eml /.msg extensions were treated as FileAttachments by the MS Graph API and generating a classcastexception. To resolve this, a check has been added to identify the attachment along with content type so .eml will be correctly recognized. In addition, the MSGraph email listener functionality related to converting from Graph to MIME message has been enhanced around the 'TO' and 'CC' recipients in a MIME message and for parsing nested attachments in Item attachment for addition to MsgraphMessage.

INC-156758 · Issue 629937

ExpandStream called before Page-Merge-Into to ensure correct merge

Resolved in Pega Version 8.5.4

The Page-Merge-Into method was not merging the source page into the target page when the use case was run without tracer, but merged properly when run with tracer. This was traced to an intermittent issue with expanding properties, and has been resolved by calling expandStream on the source property if it is unknown prior to checking if the source and target properties are merge compatible.

INC-158728 · Issue 625588

Oracle handling updated for upgrade DDL

Resolved in Pega Version 8.5.4

DDL generated for a Pega upgrade displayed the error "ALTER TABLE PC_ASSIGN_WORKBASKET DROP CONSTRAINT GETNEXTWORKINWORKGROUP" when trying to install. This was traced to a change made by Oracle for optimization, and has been resolved by updating the handling for primary key constraint and the corresponding index name.

INC-159143 · Issue 628923

Methods updated to prevent rounding of JSON response decimals

Resolved in Pega Version 8.5.4

When using a REST connector for an outside service, precision numbers in the JSON response were being rounded or truncated when parsed for the DataSource page. For example, a JSON message with a value like 6045.900000000000000001 became rounded to 6045.9. This happened in both methods used for fast and non-fast processing, and has been resolved by treating the decimal value as a string and then creating a BigDecimal object out of it to avoid truncation in the fast processing scenario, and by adding mapper.enable(DeserializationFeature.USE_BIG_DECIMAL_FOR_FLOATS); for the non-fast processing scenario.

INC-159438 · Issue 632186

HTTP Strict Transport Security update

Resolved in Pega Version 8.5.4

An update has been made to increase the max age of the HTTP Strict Transport Security (HSTS) header parameter from 7 days to 1 year.

INC-159717 · Issue 634926

Zero Downtime Upgrade mechanism updated

Resolved in Pega Version 8.5.4

Scheduled Agents were running several times on each node when there were many executions scheduled for the same agent. This was due to the task derived from the agent's schedule not being unique to the agent, allowing the Zero Downtime Upgrade logic handling the insertion to restart agents several times while reacting to cluster topology changes. To resolve this and make the process more robust, the Zero Downtime Upgrade mechanism has been updated with better tracking and logging.

INC-161737 · Issue 642673

Queue processor correctly moves items to Broken Items

Resolved in Pega Version 8.5.4

When an exception occurred while Queue Processor processed an item, he queue item was not moved to Broken Items. The error " inconsistent datatypes: expected - got CLOB DatabaseException caused by prior exception" was generated. This has been resolved by modifying the NativeSQL builder and NativeSQLBatchExecutor to allow the batch of queries to be retried. Additional changes were also added for Oracle databases to identify the correct column types.

INC-162198 · Issue 628704

Tracelist cleared to address parser exception in REST Service

Resolved in Pega Version 8.5.4

In a requestor pool of mixed types, HTTP and REST, the alert data was not initialized properly if there was a parse exception due to invalid data in the incoming payload. For example, last_input, first_activity, and last_step could all be left over from the prior HTTP service request. This was caused by the system pulling in seemingly unrelated activities for the "Last activity called" in the stack trace of a service when a single alert was created by two different service types which were sharing the same package, and has been resolved by explicitly clearing the tracelist for the service to prevent inaccurate information being reported in the logs.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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