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.

INC-211184 · Issue 708499

Removed ORDER BY clause duplication when using MSSQL

Resolved in Pega Version 8.7.2

After updating from Pega 8.4 to Pega 8.7, executing the query for the report definition generated the error "SQLServerException: Incorrect syntax near the keyword 'ORDER'." Investigation showed the ORDER BY clause was added to the Native SQL query from the standard dataflow background task and from the native SQL API as well when using an MSSQL database. This has been resolved by adding changes to restrict the order by clause if the SQL query has order by clause already for MSSQL.

INC-218491 · Issue 717432

Removed ORDER BY clause duplication when using MSSQL

Resolved in Pega Version 8.7.2

After updating from Pega 8.4 to Pega 8.7, executing the query for the report definition generated the error "SQLServerException: Incorrect syntax near the keyword 'ORDER'." Investigation showed the ORDER BY clause was added to the Native SQL query from the standard dataflow background task and from the native SQL API as well when using an MSSQL database. This has been resolved by adding changes to restrict the order by clause if the SQL query has order by clause already for MSSQL.

INC-211018 · Issue 707526

Number control correct when IME is Japanese

Resolved in Pega Version 8.7.2

The Microsoft Windows Input Method Editor (IME) allows developers to enter complex characters in four different East Asian languages using the standard keyboard. When IME was in Japanese mode, entering a number resulted in the input happening twice with the result of an entry such as 12345 becoming 124512345. This has been resolved by updating the code to ensure there is no duplicate IME key

INC-211911 · Issue 713052

Able to expand rows when other rows are expanded

Resolved in Pega Version 8.7.2

When multiExpand, threadProcessing, and readonly flags were true, attempting to expand multiple rows at the same time collapsed already opened rows and generated an error indicating "target is not defined". This was caused by 'handleEditItem' not calling the collapse functionality for an opened row correctly, and has been resolved by adding a check which allows the expansion of multiple rows for readOnly details.

INC-212623 · Issue 709550

Dropdown label is accessible when combined with placeholder or tooltip

Resolved in Pega Version 8.7.2

The screenreader was not reading the dropdown label if tooltips or placeholders were added to the dropdown. This was caused by the label of the element being overwritten, and has been resolved by replacing aria-label with aria-describedby on the input element.

INC-217974 · Issue 715427

Handling added BIX extraction failure when called from custom activity

Resolved in Pega Version 8.7.2

After update, BIX extraction was failing but email from the schedulers indicated success. Investigation showed that when extract was called from a custom activity by calling pxExtractDataWithArgs, the stepStatusFail 'when' rule in the custom activity was not capturing all the exceptions specific to database extracts. This has been resolved by adding the necessary handling.

INC-215582 · Issue 712285

Cosmos calendar icon handles allow entry set to no

Resolved in Pega Version 8.7.2

When using the Cosmos theme, the Calendar icon became disrupted when "allow text entry" option was set to "no". This has been resolved.

INC-199469 · Issue 707515

PDF margins made available as parameters

Resolved in Pega Version 8.7.2

After update, margins were different in exported PDFs. This was due to upgraded jar files: PD4ML v3 used setPageInsets(new Insets(top, left, bottom, right)) , but the v4 jar uses setPageMargins(new PageMargins(left, top, right, bottom)) . Because the order of values (20, 10, 10, 10) were not changed this produced a different result. To resolve this, PD4ML margins are now available to be set as parameters: Param.pyMarginLeft, default value 20 Param.pyMarginTop, default value 10 Param.pyMarginRight, default value 10 Param.pyMarginBottom, default value 10 When standard activities like HTMLToPDF / pyViewAsPDF / pyAttachAsPDF are used, add a Property-Set step before calling the activity to add the necessary margin parameters. When CreatePDF smart shape is used, set the parameters via the connector of the CreatePDF.

INC-204349 · Issue 704562

Updated check for portal name with search

Resolved in Pega Version 8.7.2

After update, using search from a Cosmos portal landing page launched the results in a new tab, and the logoff menu did not show which portal was being used. This has been resolved by updating the 'when' rule to check if pxThread.pxPortal contains the portal name rather that testing for equality.

INC-201625 · Issue 698654

Updated variable handling for filter logic to avoid reuse

Resolved in Pega Version 8.7.2

When adding the property "ItemStatus" as a filter for a report, the validation message: "This property does not exist or has no column mapping" appeared. This was traced to an empty caption for a class join property used in the filter due to RRFilters_Logic reusing the strFieldName variable, and has been resolved by updating the variable handling to use a unique name, strPropName.

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