INC-154205 · Issue 618736
Corrected wrap text for Cosmos radio buttons
Resolved in Pega Version 8.5.3
When using Cosmos, radio buttons with large labels were displayed with the text overlapping even when wrap text was enabled and the radio button placement was incorrect. This was traced to a height of 32px being set as the default, overriding the wrap text setting, and has been resolved by adding CSS to set the height as auto when wrap text on radio label is used.
INC-157448 · Issue 638925
Latitude and longitude populated for CreateWork history
Resolved in Pega Version 8.7
After enabling geo location in the casetype rule, when the case was created using the Create menu option from either Dev studio or Manager portal the Latitude and longitude values were set on the pxRequestor page and were available in the Case Audit history in the Map control. When the same case was created using CreateWork action configured on a button, it did not log the latitude and longitude values in the case Audit history. Investigation showed this was caused by a 'when' condition in the AddWorkHistory activity which checks the requestor page for latitude value and which had a null value when a createWork action was used to create the case. To correct this, the template metadata of the form will be populated with latitude and longitude values from pxRequestor page to be used in the latitude and longitude hidden fields.
INC-167388 · Issue 651309
Values treated as strings for offline data transform concatenate
Resolved in Pega Version 8.7
When using a Data Transform to construct a URL using multiple properties that contain values with a leading or trailing "0", the "0" was trimmed when the corresponding mobile JS code was generated using pega.process.expression.getValue("pyWorkPage.PlanData.SegmentID", "pyWorkPage.PlanData") . This was traced to the offline property type assuming that any numbers-only string should be treated as a number, so the data transform concatenate was converting “0001” to 1. To resolve this, the value will be treated as a string when being evaluated in an offline data transform.
INC-184729 · Issue 669741
Pinning document to space correctly generates thumbnail
Resolved in Pega Version 8.7
When pinning a document to a space using the standard document repository tile, the resulting pin did not have an image corresponding to it. The process worked properly when pinning a document directly from the space itself. This was a missed use case and has been resolved by adding an update to set the pyImage of the document while pinning the space.
INC-156826 · Issue 625439
Logic updated for adding new child/sibling to hierarchical paginated tree/grid
Resolved in Pega Version 8.5.3
When using a hierarchical table with pagination enabled, navigating to the last page and attempting to add a new child or sibling produced unexpected results. Navigating to the last row, selecting child, and clicking 'add sibling' caused a new row to be added. Adding a child caused the child elements to be added on top instead of at the bottom. This was a missed use case for adding a child/sibling when using a paginated tree/tree grid, and has been resolved.
INC-150172 · Issue 611775
Updated class handling for View field security
Resolved in Pega Version 8.5.3
When using a defined View which returned a page and its fields and used an inherited custom work party definition, trying to update the pyWorkParty(Customer) by calling the "post /assignments/{ID}/{actionID}" did not work as expected when Field Security was ON. This was traced to the field security relying on the design time page class information stored in the list/group property, and has been updated to resolve the view fields using actual class information from the work page.
INC-153281 · Issue 612785
Selectors updated for segmented radio buttons in Cosmos
Resolved in Pega Version 8.5.3
When using a Segmented format radio button in an application built on Cosmos, clicking the control caused the screen to flicker and the focus moved to the top of the screen. This behavior did not occur when performing the same action in a classic application built on UI Kit. This was due to a difference in positioning: in UI Kit, the input for the segmented radio button is positioned using an absolute position and the parent radioTable div uses a relative position, while in Cosmos the radioTable div is given a static position. This has been resolved.
INC-179478 · Issue 662927
Handling updated for progressive load on scroll in repeating dynamic layers
Resolved in Pega Version 8.7
When using progressive load on scroll on a repeating dynamic layout with a bar graph control, the bar which was loaded earlier was being removed during scrolling and only the current page's bar graph was displayed. This was traced to the page load and refresh handling in repeating dynamic layers, and has been resolved by modifying the logic to use a partial-refresh when appropriate.
INC-182375 · Issue 664344
Report filter description correctly displayed
Resolved in Pega Version 8.7
When a function alias was used in the filter of a report definition without the caption and with some value assigned, the FilterName was not getting displayed when the report was run. This has been resolved by updating RRFilters_Logic.
SR-C77072 · Issue 415542
Title of Repeating Layout is passed correctly with ViewAPI
Resolved in Pega Version 8.1.3
When using a section with a repeating dynamic layout and a header (title) set with a property that had value, using the view API displayed a title which showed the property name instead of the value. To correct this, RDL has been updated to use a title and include support for text/property/fv and localization.