INC-156826 · Issue 625436
Logic updated for adding new child/sibling to hierarchical paginated tree/grid
Resolved in Pega Version 8.4.5
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.
SR-D16624 · Issue 490929
Table layout filter popover position corrected for Pega mashup
Resolved in Pega Version 8.1.6
When using an exposed harness with table layout using Pega web mash up, the mash up worked but the apply and cancel buttons were not visible when any column was clicked to filter the result. This was traced to the filter popup having a hardcoded position offset set in its div element, and has been resolved by delegating the responsibility of the filter popover height calculation to the popover.
SR-D21618 · Issue 492938
Stories Word doc includes uploaded images
Resolved in Pega Version 8.1.6
When trying to generate a Word document for the user stories by going to the Options menu and using the 'Document' option, there were images within the user story description that were not rendered in the Word document. Investigation showed that images would show up in the Word document if the images were dragged and dropped or copied and pasted into the description field instead of using the image uploader button. This was because the image was stored in a separate folder when the upload button was used and only a link to the attachment location was added to the description vs using copy/paste or drag and drop directly stored the attachment content in the description. An enhancement has been added to handle the upload use case so the images will appear in the Word document.
INC-159143 · Issue 628921
Methods updated to prevent rounding of JSON response decimals
Resolved in Pega Version 8.4.5
When using a REST connector for an outside service, precision numbers in the JSON response were being rounded or truncated when parsed for the DataSource page. For example, a JSON message with a value like 6045.900000000000000001 became rounded to 6045.9. This happened in both methods used for fast and non-fast processing, and has been resolved by treating the decimal value as a string and then creating a BigDecimal object out of it to avoid truncation in the fast processing scenario, and by adding mapper.enable(DeserializationFeature.USE_BIG_DECIMAL_FOR_FLOATS); for the non-fast processing scenario.
INC-164308 · Issue 634408
UseNoCacheHeaders default expiration set to "0"
Resolved in Pega Version 8.4.5
When the prconfig/HTTP/UseNoCacheHeaders/default was set true it used the value "Expires: Thu, 01 Dec 1994 16:00:00 GMT". This has been updated to the more commonly used setting "0".
SR-D23340 · Issue 497607
Calendar begins with Saturday in the Arabic locale
Resolved in Pega Version 8.1.6
When using the Arabic locale, the week was not starting on Saturday as expected, but was showing Thursday as the first day. This has been corrected.
INC-145802 · Issue 636322
Oracle temporary space explicitly freed after writing LOBs
Resolved in Pega Version 8.4.5
Oracle temporary space used to write the LOB was not freed up after writing records to Log-Service-File when using OJDBC8 or OJDBC10 versions and the table involved had inline BLOB storage such as small blob tables like Log-service-file (2-4kB blobs). This did not occur when using OJDBC7, but investigation with Oracle could not determine why the older version did not have this issue. This issue has been resolved by explicitly freeing the LOB space with a call to free() / freeTemporary() , a utility for LOB objects that was introduced in JDBC 4.
INC-157214 · Issue 631598
Mentioned user in Pulse appears correctly
Resolved in Pega Version 8.4.5
When loading user names while using the "@" functionality in a Pulse post, adding or tagging the operator/user in Pulse by entering each letter brought up the list, but when using copy/paste it was not possible to select the desired value from the user.Suggestions list of operators/users. If by chance the user name was selected from the suggested list, the operator ID was added instead of the full name. This has been resolved.
INC-157957 · Issue 624207
Autocomplete correctly sets null values in clipboard
Resolved in Pega Version 8.4.5
When using an autocomplete control with display configuration "In a List", if a property value was null then the value of the property in the clipboard was set as “undefined”. This was due to the pzGetACData activity returning only properties with values and excluding empty properties, causing setProperty to use "undefined" when a property value was not found in the response. To resolve this, a condition has been added to the processAdditionalProperties method to replace an undefined value with an empty string.
INC-160078 · Issue 628838
Work object status correctly set to Resolved after refresh
Resolved in Pega Version 8.4.5
When using the Refresh option from the Other Actions menu before submitting the flow action, the work object status was not updating to Resolved-Completed. Investigation showed that when performing the Refresh action, the RefreshOnConflicts activity created a Clipboard page named LatestWorkPage with a copy of the work object. This page was not removed after use, causing the Resolved-Completed status to be set on LatestWorkPage instead of pyWorkPage. To resolve this, a step has been added to RefreshOnConflicts to remove LatestWorkPage.