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-C26047 · Issue 372483

Total count column sorting added to “Timeliness of Top Process Owners” report

Resolved in Pega Version 8.1

Sorting has been added to the total count column of the “Timeliness of Top Process Owners” report in CL Assign-Worklist ID pyAgeByAssigneeTop5.

SR-C26209 · Issue 368478

Status of -action rollback clarification

Resolved in Pega Version 8.1

When -action rollback was executed using prpcServiceUtils it returned Status as SUCCESS, creating the impression that the request has been successfully completed by the server whereas in actuality the request had simply been correctly queued for execution. To be consistent with status reporting for other commands, the Status for this has been updated to be QUEUED.

SR-C26304 · Issue 367156

Output files pool close policy changed to idle timer

Resolved in Pega Version 8.1

The Output files pool in the HDFS data set closed files when there were no threads actively using files from this pool. This resulted in many files being created even when using one thread (one file per partition in that case). To prevent the buildup of files, the Output files pool close policy has been changed to use an idle timer instead. Files will be closed after 10 seconds of inactivity or the value configured via dnode/idle_file_pool_close_timeout HDFS and File Repository Datasets support save operations.

SR-C2637 · Issue 345584

Date control defaults to current year if data is invalid

Resolved in Pega Version 8.1

When given a Random number as input to Date Control, it was considering it as a year and showing the same year when opening the Calendar icon of the Field. This was caused by the processDate function in calendar.js was incorrectly returning the date, and has been fixed by updating the processDate API of pzpega_ui_calendar.js to display the current year if it is given an invalid date.

SR-C26524 · Issue 367359

Validation override option to configure routing in survey flow

Resolved in Pega Version 8.1

In order to support using a property reference to route options in a survey, pzSetSurveyDriverParams, pzSetQuestionShapeParams and pzSetQuestionPageParams have bene modified to not do validation for operator existence if a property reference is passed.

SR-C26566 · Issue 370744

Quotes stripped from property reference for pzActionSetItemFocus RUF

Resolved in Pega Version 8.1

Menu navigation was not working if a property reference included quotes. To resolve this, pzActionSetItemFocus RUF has been modified to remove any extra quotes present

SR-C26648 · Issue 369666

pyTaskName truncation raised to 128 characters

Resolved in Pega Version 8.1

An issue was seen with the Flow.AddHistory RUF truncating the pyTaskname to 32 characters when pxTaskLabel was more than 32 characters. To resolve this, Flow.AddHistory RUF has been updated to truncate the pyTaskname to 128 characters when pxTaskLabel is more than 128 characters.

SR-C26699 · Issue 374934

DSS-configurable idle connections timeout added

Resolved in Pega Version 8.1

In some cases Idle Connections were not getting closed; code has now been added to close idle connections after a specific time based on an idle timeout value set using DSS.

SR-C26782 · Issue 367349

ApplicationManager checks login success state

Resolved in Pega Version 8.1

If there was a network connection error, the mobile application sometimes froze during login. Killing and restarting the app still hung on the splash screen because the initial state of the application was cached even though the login was not completed successfully. This was traced to the ApplicationManager API not checking the state, and has been corrected.

SR-C26841 · Issue 369641

Handling added for missing class definition in DT Java generation

Resolved in Pega Version 8.1

Java generation was failing during the save of a Data transform which referred to a data page present in two different rule set versions; in the lower version it was defined on class, which is no longer in the database, and an exception resulted from the null value. Handling for this has now been added to FirstLevelCandidatesResolver.

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