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-B41504 · Issue 299952

Tabbed navigation research wrap-up fixed

Resolved in Pega Version 7.3

Tabbed navigation Research interaction wrap-up was displaying the review harness instead of autoclosing. In order to resolve issues with the Autoclose harness being overridden, in cases where the user is not authorized to perform the assignment AND the harness is set as "Perform", the harness purpose will be set as "Review".

SR-B41874 · Issue 301766

View parsing regex fixed for union statements

Resolved in Pega Version 7.3

While importing jar file through import out-of-the-box, generated SQL Scripts from the manual option system had scripts which were already present in the Database. This was caused by the view parsing regex not handling UNION statements, and has been corrected.

SR-B42911 · Issue 301591

Tomcat config documentation clarification

Resolved in Pega Version 7.3

The documentation for using Tomcat has been updated for clarity. Step 2b of 'Configuring Tomcat by editing the context.xml file' indicates that configuration of the Admin datasource is optional (which it is), but steps 3 and 4, which use this datasource, were not labeled as conditional on 2b. As a result, those opting not to use the admin datasource believed those settings needed to be added. In the new text for steps 3 and 4, the clarification "For dual-user configurations only, insert..." has been added.

SR-B43415 · Issue 299493

Upgrade does not exit when encountering corrupt ruleset name

Resolved in Pega Version 7.3

In order to avoid upgrade failures caused by an application rule existing without a version (corrupted data), handling has been added so that the upgrade will not fail if it encounters an application rule without either a name or version.

SR-B44001 · Issue 302395

Bulk Action filter handles rule withdrawn from landing page

Resolved in Pega Version 7.3

If a property was withdrawn in the Bulk Actions landing page, the other page properties no longer appeared in the Filter Property list. This was due to the getImmutableTerminalPropertyInfo function causing an exception whenever the rule availability was empty. To resolve this, the system will check the availability of the property rules in the "Rule-Obj-Property.LookupList" activity's 3rd step before processing/adding the embedded properties.

SR-B44278 · Issue 302830

MT guide updated for rules blocking/restriction

Resolved in Pega Version 7.3

The MultiTenant guide has been updated to clarify what causes rules to be blocked or restricted and the possible consequences of unrestricting rules.

SR-B44787 · Issue 300852

work object lock released if nextAssignment is false

Resolved in Pega Version 7.3

The lock was not getting released on Work object creation even though back-to-back assignment processing was disabled for the flow. To correct this, the work object will be unlocked if the pynextAssignment parameter is false.

SR-B462 · Issue 271962

Event Late triggers expanded

Resolved in Pega Version 7.3

If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.

SR-B4620 · Issue 277531

Fixed dirty prompt save UI error

Resolved in Pega Version 7.3

The dirty prompt save action was causing corruption in the UI if there were validation errors present. This was traced to the On save of a work object with errors replacing the harness with section. As a result, styles and scripts in harness were lost and only plain/raw html was shown. This has been fixed by removing the Show-Stream step so Show-Harness takes care of refreshing the screen.

SR-B46718 · Issue 304110

pyFLowSLA property added to support pxObjClass change

Resolved in Pega Version 7.3

Validation errors occurred when using a data transform which changes the pxObjClass of primaryPage. Pega Platform tries to validate internally for all the properties during the page change class; in order to support the DT, the new property pyFlowSLA has been introduced. The previous pxFlowSLA property has been deprecated.

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