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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-B97434 · Issue 343276

FirstName and LastName updated on change of workparty

Resolved in Pega Version 7.4

After adding the default operator as a Work Party to a case, the pyFirstName and pyLastName properties were correctly populated. However, when the work parties were updated to have an operator other than the default as required, the pyFirstName and pyLastName properties were not updated and still contained the values from the previous workparty, i.e. the default operator First Name and Last Name. This was traced to a missed use case where pyFirstName and LastName were not getting set on change of Operator ID, and has been fixed.

SR-B97750 · Issue 349456

Enhancement to propagate remote addresses with load balancing

Resolved in Pega Version 7.4

Enhancements have been made to ensure the remoteHost and remoteAddr fields present in the original Servlet request are consistently populated even when the server is behind a load balancer.

SR-C10235 · Issue 351442

DDL comment added for DB2/zOS NOT NULL error handling

Resolved in Pega Version 7.4

After importing RAP on DB2/zOS with schema changes, downloading the DDL and attempting to apply it resulted in the generated DDL working on DB2/uDB but not on DB2/zOS. This was due to the DDL not having a needed DB2/zOS keyword default, but the column required attribute (NULL or NOT NULL) is not allowed to be changed on an existing table in a DB2/zOS database platform. The class was incorrectly generating DDL in an attempt to change it, causing a failure during the DDL application of the import. The class now generates a DDL comment indicating the change is not allowed so that the application of the DDL will continue without error.

SR-C1381 · Issue 343768

Performance improvements in assembled rule classloader

Resolved in Pega Version 7.4

The code for the assembled rule classloader has been modified to improve performance.

SR-C1769 · Issue 351478

Day function corrected for pre-1970 dates

Resolved in Pega Version 7.4

The function day (datetime) was behaving differently for dates before and after 1970/01/01. To resolve this, the Date diff calculation logic has been modified.

SR-C1769 · Issue 351502

Day function corrected for pre-1970 dates

Resolved in Pega Version 7.4

The function day (datetime) was behaving differently for dates before and after 1970/01/01. To resolve this, the Date diff calculation logic has been modified.

SR-C1859 · Issue 344369

Clipboard clears on form submit, plus performance improvements

Resolved in Pega Version 7.4

Progressing through an application questionnaire was causing clipboard size to increase without being cleaned. This was due to a page clearing request not being triggered, and the harnessonbeforeunload method has updated to trigger pyDeleteDocumentPg on submission of the form in topnavigation portal. In addition, performance improvements have been made to this process.

SR-C1960 · Issue 348388

Support added for RTE images with Mashup

Resolved in Pega Version 7.4

Using Mashup code to include a Rich Text Editor configured to accept images inside a section was not working as expected. Uploading an image displayed a cross image in the upload window, and subsequently the file was displayed as a broken image in RTE. Investigation showed that in a NonMT environment, data content requests from mashup will send requests with access group hash, which was not previously supported. An enhancement has now been added to accept data content requests with or without access group hash at the engine side in both MT and NonMT environments.

SR-C216 · Issue 351334

Restart flag added to connector errors

Resolved in Pega Version 7.4

Connector error messages have been updated with a Boolean flag "whether to restart: true/false".

SR-C2190 · Issue 345689

Enhancement to allow disabling application requestors

Resolved in Pega Version 7.4

A new DSS has been added to disable passivation of application requestors. When set to true, application requestors will not be passivated and the system will not check pr_page_store for a passivated thread for app requestors. Note that when this is enabled, passivation for ALL application requestors will be suppressed.

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