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-A19932 · Issue 243259

Corrected cancel function in Calendar options

Resolved in Pega Version 7.2.1

If the pxCalendarViewGadget was launched in a modal dialogue, clicking the cancel button in the Calendar options menu caused the assignment to be submitted. This was caused by a form submit and harness refresh being incorrectly called together by the cancel, and has been changed so the click of cancel in calendar options will refresh the pzCalendarOptionsDefinition section but disable the form submit, resulting in the previous values being retained.

SR-B380 · Issue 270771

New round function for Expression Builder

Resolved in Pega Version 7.2.2

The round(...) function in Expression Builder was not working as expected due to the engine not supporting the use of "Number"(Java type) as an input parameter. In order to resolve this, a new RUF has been provided: pzRound--(BigDecimal,BigDecimal), which will change the Number parameter to BigDecimal/ int, which is a parameter supported by the engine.

SR-A103203 · Issue 276928

SQL alias function getLastDayofYear repaired

Resolved in Pega Version 7.3

After upgrade, the SQL alias function getLastDayofYear generated an error. This was due to missing format conversion for the date value parameter, and has been corrected.

SR-B33387 · Issue 298483

Incorporated synchronized timestamp function for addWarning

Resolved in Pega Version 7.3

When the pxWarningCreatedDateTime was the same for two warnings with the same pxWarningName, one of the warnings was not getting justified. To fix this, the addWarning function will use the synchronized timestamp function getCurrentDateTimeUnique() to generate the created time.

SR-B92155 · Issue 343548

ADM and Batch Decision functions compile

Resolved in Pega Version 7.4

Trying to compile the functions of ADM or batch decision was failing with a compilation error. An issue was found in the library which was resulting in picking up and compiling the all the previous versions, and this has been corrected so the system will pick up the latest version of the Batch decisioning Library.

SR-B92155 · Issue 346408

ADM and Batch Decision functions compile

Resolved in Pega Version 7.4

Trying to compile the functions of ADM or batch decision was failing with a compilation error. An issue was found in the library which was resulting in picking up and compiling the all the previous versions, and this has been corrected so the system will pick up the latest version of the Batch decisioning Library.

SR-D8794 · Issue 483814

Import ordering shifted to prioritize Functions and Libraries

Resolved in Pega Version 8.3

A runtime error was seen when running DataTransform getbranchandcbsadetails. Investigation showed that when getbranchandcbsadetails was imported, the RUF it referenced was not imported beforehand. To resolve this, the import ordering has been reworked to prioritize Function and Libraries by shifting Rule-Utility-Library and Rule-Utility-Function to be after Rule-Obj-Property* in the import order.

SR-C81946 · Issue 418710

Maintenance function operator ID will not persist in the system

Resolved in Pega Version 8.2

After a hotfix maintenance activity, an audit revealed that an extra operator created for the purpose called CloudMaintenanceUser persisted in the system. The code has now been updated to bypass saving operator records marked with pzPersistOperator="false" on user initialization; the CloudMaintenanceUser will be created with this property set to false, and updating this operator will be skipped during unauthentication.

SR-C76417 · Issue 430545

Check added for reference function in DB2 join

Resolved in Pega Version 8.3

In DB2, when a sub-report column contained a function that was used for a join condition in the main report, an invalid filter property error was generated while saving. This was traced to the edit validate rule checking for the data type of both of the properties used in the join, and has been resolved by adding a check to see if the join operand is of function 'reference'; if so, the system will resolve the function, check for data type property, and set it.

SR-D2615 · Issue 439225

Added function to auto-validate Chinese date

Resolved in Pega Version 8.3

If a datetime property with custom format was created in the zh_CNadtimezoe (Asia/Shangai) locale, the property was not updating if a date was selected with any time unless an onchange refresh action was included. This has been resolved by adding a function that will automatically validate the date for the Chinese locale.

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