INC-171257 · Issue 651732
Expanded results for Proposition Filter Relevant Record Properties
Resolved in Pega Version 8.5.5
Previously, a maximum of 500 records were returned from pr_data_tag_relevantrecord when using Edit Parameters for the report definition proposition filter rule. In order to accommodate more complex needs, an update has been made to use the D_pxGetClassDataModel data page to fetch all the records and make them available in the dropdown.
SR-A20072 · Issue 238701
Portal markup in PDF resolved
Resolved in Pega Version 7.2.1
When using the Google Chrome browser, the portal harness markup was being included in PDFs generated from the user portal due to the frameless dynamic container. This has been corrected.
SR-A20072 · Issue 240043
Portal markup in PDF resolved
Resolved in Pega Version 7.2.1
When using the Google Chrome browser, the portal harness markup was being included in PDFs generated from the user portal due to the frameless dynamic container. This has been corrected.
SR-A15490 · Issue 233417
Grid layout correctly displays columns with empty rows
Resolved in Pega Version 7.2.1
In a repeating grid, when Width of content -> Pixels(Fit Content) and Fixed (pixel) size grid : Grid size (in pixels): 1000 px (Width) and 0 px(Height), Freeze grid header are selected, all the columns are not shown when there are no records in the grid. This was traced to a div function that did not sync properly and clipped columns in this circumstance, and a check has been added to correct the display when using progressive loading.
SR-A15695 · Issue 233521
Grid layout correctly displays columns with empty rows
Resolved in Pega Version 7.2.1
In a repeating grid, when Width of content -> Pixels(Fit Content) and Fixed (pixel) size grid : Grid size (in pixels): 1000 px (Width) and 0 px(Height), Freeze grid header are selected, all the columns are not shown when there are no records in the grid. This was traced to a div function that did not sync properly and clipped columns in this circumstance, and a check has been added to correct the display when using progressive loading.
SR-A13528 · Issue 229419
Fixed dropdown harness action focus
Resolved in Pega Version 7.2.1
If a pyActionArea section was dropped inside a harness with dropdown mode, the focus was going to the first focusable element in the harness when the dropdown was used to switch among local actions. This has been fixed.
SR-A20504 · Issue 241375
Queue type validation updated in MDBListener
Resolved in Pega Version 7.2.1
Queue type validation failed when testing connectivity in MDBListener if the pyResourceName was set with queue name and there was no pyResQueueName defined in the page. To handle this, the getString function will use the pyResourceName instead of pyResQueueName.
INC-169186 · Issue 655536
Disconnect button availability extended
Resolved in Pega Version 8.5.5
A case was not refreshing when the disconnect button was selected while using the standard section for authorization grant type authentication. This was traced to a query executed to find a div with attribute pzInsHandle, but that attribute was not applicable in the user portal. To support this use, the query has been extended to be applicable for user portal (attribute data-ui-meta) and Dev Studio landing page.
SR-A22365 · Issue 243530
Multi-parameter function value handling added to Report Definition chart
Resolved in Pega Version 7.2.1
When a chart control was configured using the property panel in design view, the chart preview did not update appropriately if it used a column defined by a function that with two or more parameters. To handle this, part of com.pega.pegarules.priv.desktop.reporting.chart.AutoChartConfigTranslator.translateDataItem(DataItem, ClipboardPage) has been refactored such that it only splits pyReportColumnKey on the first ',' (comma).
SR-A21908 · Issue 245505
Eliminated new case creation on browser refresh
Resolved in Pega Version 7.2.1
When using the tabbedscreenflow7 harness, refreshing the screen caused a new Case to be created. This was seen in a no-frame portal with the top navigation for every action set to createNewWork, and the same new work URL was hit during the refresh. This has bene fixed by modifying replaceHistory in dynamiccontainer_lite.js to add a condition to skip returning when strHarnessMode is not action.