SR-D18589 · Issue 495717
Google Map API updated
Resolved in Pega Version 8.4
When using Address Map control with enabled markers whose source is a datapage, the location in the map was redirected as expected to the address populated by the datapage, but the marker overlay that appeared by default containing address details and a link to "Open in Google Maps" did not load. Clicking on random places on the map caused it to load correctly. This has been corrected with the creation of a custom activity to get section markup that will use reload section with proper context to fix the issue. In addition, enhancements have been made to enable automatic upgrade of existing apps which use Address Map to use pxMap by auto-generating pxMap from the existing configuration. Properties set in Address Map's design time configuration should be mapped to corresponding properties in pxMap as given below. If report definition, clipboard page. or list property was used as marker source, a data page will need to be created manually. 'Starting Lat, Long' property is mapped to 'Custom initial lat / long' 'Markers source' is mapped to 'MARKERS' as follows: - 'None' to 'None' - 'Data page' to 'Data page', 'Property for location' -> 'Location property', 'Marker info section' -> 'Info section' - 'Property' to 'Property', 'Address property' -> 'Address property', 'Allow marker repositioning to change the address value' -> 'Drag marker position to update address value', 'Report lat long in property' -> 'Lat / long logging property', 'Report incorrect address' and 'Error message' is ignored at this time - 'Report definition' is ignored - 'Clipboard page' is ignored - 'List defined on property' is ignored 'Visibility' and 'Tour ID' are mapped 1to1 It is also possible to disable rendering of the Map control from the Address Map configuration: when switched off, pxAddressMap will be generated instead of pxMap.
SR-D21004 · Issue 492467
Corrected case comparison to prevent completed cases being routed to error workbasket
Resolved in Pega Version 8.4
Some cases were routing to the sync error workbasket even while being resolved. Investigation showed that pzSetDeferWrite was comparing the serverside assignhandle with the assignahandle sent by the client upon sync, but since the client was sending assignahandle in lowercase (reproduced if workid prefix is customized), the comparison was failing. To resolve this, the AI has been modified to pass the pzInskey as uppercase to the pzSetDeferWrite activity.
SR-D28060 · Issue 498751
XSS filtering added to App Studio
Resolved in Pega Version 8.4
The pzDisplaySpaceFeedTitle control which is used to display the audit feed in Pega App Studio has been updated with XSS filtering.
SR-D28293 · Issue 498235
Pega Survey answer values support special characters
Resolved in Pega Version 8.4
When using a Complex radio control (RadioButtonComplexQuestionSurvey), a selected option that used answer values containing special characters was cleared on refresh. This was traced to a mismatch between strAnswer and strValue in the control logic, and has been corrected.
SR-D28965 · Issue 501858
Repository document deletion modified for better cleanup
Resolved in Pega Version 8.4
When using documents functionality, creating and uploading a document properly stored it, but deleting the document did not remove the associated files from storage. Whenever a document is created that has a file, instances Of Link-Attachment and Data-WorkAttach-File are also created. Previously, when the document was deleted, the associated instances and actual file were not deleted from the repositories but rather marked as Resolved-Withdrawn and hidden at the UI level. The system has now been updated so that when a document is deleted, the document attachment will also be deleted from all places like list, Tile, and document View, and reference instances like Link-Attachment and Data-WorkAttach-File instance will also be removed along with the actual file from the repository.
SR-D30428 · Issue 503425
Added handling for deprecated UI Kit in Pulse OpenURLInWindow
Resolved in Pega Version 8.4
After upgrade, clicking on a link in a Pulse comment opened a new window with an error message indicating no content was returned. Investigation showed that if an older deprecated version of the UI kit was used, 'Open URL in window' was configured as Run Script function. The more recent versions use an OpenURLInWindow action. To resolve this, the script has been updated to use an action and pass the correct parameters.
SR-D32107 · Issue 503173
jQuery library updated
Resolved in Pega Version 8.4
As part of security enhancement features, the jQuery library has been upgraded. The following rulesets have been updated: pzJquerymentionsInput_custom , pzpega_process_engine , pzpega_ui_addressmap , pzpega_ui_doc_domUtils
SR-D33052 · Issue 502063
Blank space removed in email reply
Resolved in Pega Version 8.4
An issue with blank space being added between the CSR icon and the email content for the first customer mail has been resolved by setting the window width to 100%.
SR-D33930 · Issue 507972
Check added to pyWorkPage before context page replacement
Resolved in Pega Version 8.4
When given an assignment configured with Save and Next buttons where the on-click of the Next button triggered FinishAssignment and the case type used Optimistic locking, the workobject lock was not acquired and an error was thrown when clicking Save and then the Next button. Investigation showed that the lock was not acquired because the pyCaseUpdateInfo page was not available in the work object under pyWorkPage. This was traced to the 'When' condition used to display the delete icon on a pulse post. This When condition needs to be evaluated on the context page (in this case, the work page), but when multiple posts are present on the WorkObject) the pyWorkPage was being replaced with a fresh copy from the DB and any updates on the current work page were lost. To resolve this, the behavior has been changed from always creating a context page to only creating the context page if one does not already exist on the Thread.
SR-D35434 · Issue 504588
Added subprocess cleanup for hasPreviousTask loop
Resolved in Pega Version 8.4
The mobile app hung on a specific scenario where there were no displayable shapes in the flow path (all decision shapes) and the pyFlowPath became empty but wasn't removed from the pxFlow page. This was traced to environmental loops present in the application, and this has been resolved by ensuring that while going back, completed subprocesses are completely removed from the pxFlow on pyworkpage.