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-D40523 · Issue 505926

Corrected Pega-Perf cookie adding double quotes

Resolved in Pega Version 8.2.4

After upgrade, issues were seen with mashup not loading properly. In addition, a region in the environment was not able to access the developer portal. This was traced to an issue with pzPega_ui_statetracking.js, which handles adding the Pega-Perf cookie, adding a cookie with double quotes to HTTP requests. The double quotes have been removed to resolve this issue.

SR-D36335 · Issue 504333

Post Value action properly displayed in upper case after validation

Resolved in Pega Version 8.2.4

After upgrade, if a property with Edit Input toUppercase was created and placed it on a section where the text input has Post Value on Change, validating the uppercased property on the clipboard resulted in the non-uppercase value displaying on the screen. This was traced to the target element with the response value not being updated with the server response for the post value action. Only the attribute value was updated, which is not shown to the user. In order to properly display the value, logic has been added to update the target element value with the response value.

SR-D20423 · Issue 503444

Improved upgrade handling for tables using classes with property references

Resolved in Pega Version 8.2.4

After upgrade, some page property values were blank and exposed database columns did not contain the values. Investigation showed that the reference properties did not have context and hence column population was not able to determine their value. To resolve this, instead of doing column population for all the columns, the system will identify classes that have property references and that are being optimized as part of upgrade process and maintain a list of specific columns to update.

SR-D23723 · Issue 503088

pxGenerateExcelFile updated for handling blank dates

Resolved in Pega Version 8.2.4

When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format.

SR-D42670 · Issue 510183

Force order added to inner join when running a Rules Resolution filter

Resolved in Pega Version 8.2.4

After upgrade, D_getResolvedWorkStatuses was not loading properly due to a Report Definition that used a Filter by Rule Resolution option timing out on the SQL Server. When the Filter by Rule Resolution option is selected in Report Definition, it will generate a rule resolution query with an inner join which can cause a time out on the SQL Server while it tries to find out the join order for tables with multiple joins. To resolve this, the SQL server will provide a Force order, merge inner join hint option by way of an added DSS reporting/useForceOrderHint. Additionally, reporting/useMergeHintForRRquery should be set on Pega-Reporting to set things up for using the Merge Inner join hint in the query.

SR-D32035 · Issue 504705

Save Button for Delegated rules is displayed correctly

Resolved in Pega Version 8.2.4

The save button for delegated rules was displayed in a truncated shape. This has been corrected by removing the split-left style from all of the buttons that are intended to be standalone and not have a drop-down actions menu.

SR-D35734 · Issue 504478

Escalation updated to ensure assignee is notified of missed deadline

Resolved in Pega Version 8.2.4

The Passed Deadline SLA Actions to send email to the owner were not triggered as configured in SLA rule form. To correct that, pzMapEasyEscalationParams steps 3.4.10 and 3.4.11 have been modified to support "NotifyAssignee" for the passed deadline.

SR-D4559 · Issue 486555

Normalized type attribute namespace for Weblogic compatibility

Resolved in Pega Version 8.2.4

After upgrading from Weblogic 12.1.3.0 to Weblogic 12.2.1.3, the namespace in the generated Request XML for some elements was appearing as null/blank. This has been resolved by normalizing the type attribute namespaces' option in Connect-SOAP.

INC-156674 · Issue 660956

Handling added for reactivating combined Passivation and AccessGroup timeout

Resolved in Pega Version 8.4.6

Refreshing a passivated browser window in Dev Studio for an operator with a combined access group and passivation timeout was resulting in a blank screen after re-authenticating. InvalidParameterException and InvalidReferenceException messages were logged. Research showed this was caused by a missing pxPortal property on the pxThread page along with missing Application and Accessgroup pages. While refreshing the browser along with the top URL, there will be few requests with tab threads calling activities such as deletedocumentpg and SetProcessWindowName because there was an unload. Because these requests reached the server before re-authentication, the threads proceeded to the activation flow, causing properties such as pxPortal, Application, and Accessgroup pages to be removed from the thread page and requestor page according to the condition that the requestor was not yet authenticated. To resolve this, the logic in session.internal.authorization.context.BasicApplicationContextImmutableImpl#applyApplicationProperties has been updated to skip removing application page properties from the thread page in this combined Passivation and AccessGroup timeout scenario.

INC-165722 · Issue 636327

Stack trace logging enhanced for engine startup issues

Resolved in Pega Version 8.4.6

Enhanced stack trace logging has been added to capture additional information when the application is unable to start and no PegaRULES logs are generated.

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