SR-C87463 · Issue 432615
Required image replacing Mandatory Asterisk displays correctly
Resolved in Pega Version 8.1.4
After creating a mandatory text input field in a section and uploading the required image in place of the default image, the previous default image was still displayed in the portal even after clearing the browser cache and /temp folder on the app server. This was caused by the CSS rule 'pzbase-div-layouts' using specific selectors that had a hard-coded content hash for the image, which has been corrected.
SR-C87665 · Issue 424612
CPU time will be fetched from MBeanServer instead of the JRE application to provide consistency
Resolved in Pega Version 8.1.4
The value of CPU time in the Enterprise health metrics was being given in nanoseconds instead of seconds after the IBM JRE version was upgraded by applying Websphere Application Server patches. The CPUTimer is a platform class which has logic specific to different JRE vendors; in order to provide consistent results regardless of which JRE is used, the system has been updated to always fetch the values from the MBeanServer.
SR-C87757 · Issue 431645
Country Code for Austria saved correctly
Resolved in Pega Version 8.1.4
When trying to save an address with CountryCode=AT, the code was saved as "at" instead. This was caused by a temporary field value not being correctly cleared, and has been resolved.
SR-C87881 · Issue 427102
Additional dropdown options exposed for RD column definitions
Resolved in Pega Version 8.1.4
When using Column formatting in Report Definition ruleform, the "Negative format" option was losing its custom style after opening and submitting the "Format" popup using the magnifying glass. This was caused by the submitted popup overwriting the inherited style reference. Previously, the style ref options were hidden from the dropdown because the same UI is shown in the ruleform and the end user portals and the desire was to avoid end user confusion. In order to support developer use, pzPopulateNegativeFormat has been updated to expose the missing options in the dropdown.
SR-C87986 · Issue 428573
Resize handle correctly changed for RTL locale
Resolved in Pega Version 8.1.4
When the locale was set to RTL, dragging sections to the left caused a resize and dragging sections to the right moved them to the left. This has been resolved by ensuring the resizable handle for workarea is correctly changed when the locale is RTL.
SR-C88178 · Issue 429527
docx4j jar updated for compatibility with Office365
Resolved in Pega Version 8.1.4
After generating a docx file with Office365, an error appeared indicating the document had invalid XML data and couldn't be opened. Once the error message was dismissed, the file could be opened normally. This was caused by an incompatibility between Office365 and the Plutext docx4j jar, and the Plutext jar has now been updated to version 6.1.1 to resolve this issue.
SR-C88236 · Issue 428788
Debug logging added to HTTP API for improved diagnostics
Resolved in Pega Version 8.1.4
Debug loggers have been added to the HTTP API to provide more complete diagnostics for an error where users are redirected to login screen after providing valid credentials. As a workaround, restarting the node server will resolve the login issue.
SR-C88309 · Issue 426998
Tooltip added for data table refresh icon
Resolved in Pega Version 8.1.4
An enhancement has been added to provide a tooltip for the refresh icon during data table edits.
SR-C88776 · Issue 428380
Added check for blank Value List Property referenced in Dropdown Control
Resolved in Pega Version 8.1.4
When a value list property was referred in the Dropdown control, the dropdown was shown as empty. This was traced to a property of type value list / value group, ClipboardProperty.getName() api returning as empty. To resolve this, a check has been added to ensure the value is populated with the correct property name if it is blank.
SR-C88882 · Issue 431069
External mapping definitions will be used for exported property names
Resolved in Pega Version 8.1.4
Under the "External Mapping" tab on the class definition, if the property names specified were not the exact format as the column names defined in the database table, an exception was generated when using the "Export" feature. For this functionality, the system was generating an SQL which used the property names instead of column names. This resulted in an invalid column exception and the export did not work. To correct this, updates have been made to NativeSqlApiResolver in the function resolver to check for the property name and replace it with mapping defined in external mapping.