SR-D17973 · Issue 489739
Corected parameter mismatch to allow deletes to be added to history
Resolved in Pega Version 8.3
Pega was not keeping track of a property if it was deleted from the data explorer tab, resulting in not being able to restore the deleted property. This was traced to a parameter mismatch: the Delete API adds the Memo parameter to the history, but while DeleteRecord accepted the Memo parameter, DeleteRecordInner accepted the HistoryMemo parameter. Because the parameters names were different, they were not propagated to the API. This has been corrected by setting the param.memo so that Rule-Delete API adds the history and the rule gets displayed correctly in recently deleted rules.
SR-D21266 · Issue 489798
Corrected mathematical operations in mobile offline data transforms
Resolved in Pega Version 8.3
Mathematical operations such as *, /, or % were not working in mobile offline data transforms. This has been corrected by updating pzpega_ui_datatransform_generator.js to support all mathematical operations and actions.
SR-D18217 · Issue 489810
Corrected PDF generation when an image filename has special characters
Resolved in Pega Version 8.3
When using Export to PDF with an uploaded image file that had special characters in its name, the images were missing from the generated document. This has been corrected by updating the decoding of the URL to not remove the checksum when using RTE.
SR-D17706 · Issue 489885
Corrected error with accessing Request Data link in service trace
Resolved in Pega Version 8.3
After creating a Rest Service and enabling Trace, calling the Rest Service and selecting "Inbound Map Begin" resulted in the "Option Properties" --> "Request Data" link being disabled and generating a syntax error message in the Browser Console. This has been corrected.
SR-D19491 · Issue 489902
Export to Excel formats the DateTime filter for localized values
Resolved in Pega Version 8.3
When exporting to Excel, filter criteria were given in GMT rather than the localized timezone. This was caused by the implementation of localizeDateTimeString method not formatting the output string for the locale/timezone during export to Excel, and has been corrected to display the localized filter values when the filter values include DateTimes.
SR-D19639 · Issue 489967
Rule Security Analyzer failure corrected
Resolved in Pega Version 8.3
Running the rule security analyzer was generating the error "Remove the duplicate Regex". This was caused by RSA validation failing, which was traced to the activity using pyReGex property in invalid-case when the actual property name is pyRegex. This has been corrected.
SR-D19602 · Issue 489989
GetDirections API enhanced to send exact current location to Google Maps
Resolved in Pega Version 8.3
The GetDirections API was not fetching the exact current location for Google Maps. In order to enhance precision, selecting the current location will use the navigation.geolocation.getCurrentPosition API to get the latitude and longitude position and send it as a saddr parameter to Google Maps.
SR-D15275 · Issue 490024
Report title displayed properly when prompting for filter changes
Resolved in Pega Version 8.3
Launching a report from the report browser showed a blank for "Report tab title" if the option "Prompt for filter changes before displaying report" was checked. This has been corrected so the name of the report is properly displayed when prompting for filter changes.
SR-D19821 · Issue 490066
Resolved UI styling for layout group with 'run visibility on client'
Resolved in Pega Version 8.3
UI styling for Layout Group(Tab) was not working, resulting in the border/background color not being saved for layout groups. This was traced to a scenario where the same property was present in both the "Header" and "Tabs" settings of the layout group and "run visibility on client" was checked for the header, enabling the property at runtime. This has been resolved by modifying pyHeader in "Embed-Skin-Component-LayoutGroup" to uncheck "Run visibility condition on client".
SR-D21424 · Issue 490082
Corrected issue with Field Level Auditing re-adding deleted page list items
Resolved in Pega Version 8.3
Pressing a Save button that invoked the pyTrackSecurityChanges data transform caused deleted items to be added back to a page list. This was caused by pyPropertyIndex being set on the removed page in RUF-pzAddHistoryMemosForPageList, and has been corrected by removing that unneeded action.