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.
INC-183559 · Issue 664812
Handling added to process Actions chunks on multiple nodes
Resolved in Pega Version 8.5.5
If the synching of chunks to a node was interrupted, attempting to resume the remaining chunks resulted in a processing issue if the Load Balancer passed the connection to a different node than was used for the first connection. As an example, if chunks were synched to node "A" and the restarted sync saved the remaining chunks to node "B", when all chunks were synced node "B" incorrectly determined node "A" was actually doing the work and skipped the processing of the chunks on node "B". This resulted in queued chunks being left untouched. To resolve this, the logic has been updated to allow multiple nodes to process the chunks.
INC-183559 · Issue 664814
Handling added to process Actions chunks on multiple nodes
Resolved in Pega Version 8.7
If the synching of chunks to a node was interrupted, attempting to resume the remaining chunks resulted in a processing issue if the Load Balancer passed the connection to a different node than was used for the first connection. As an example, if chunks were synched to node "A" and the restarted sync saved the remaining chunks to node "B", when all chunks were synced node "B" incorrectly determined node "A" was actually doing the work and skipped the processing of the chunks on node "B". This resulted in queued chunks being left untouched. To resolve this, the logic has been updated to allow multiple nodes to process the chunks.
INC-188573 · Issue 671570
Handling added to process Actions chunks on multiple nodes
Resolved in Pega Version 8.7
If the synching of chunks to a node was interrupted, attempting to resume the remaining chunks resulted in a processing issue if the Load Balancer passed the connection to a different node than was used for the first connection. As an example, if chunks were synched to node "A" and the restarted sync saved the remaining chunks to node "B", when all chunks were synced node "B" incorrectly determined node "A" was actually doing the work and skipped the processing of the chunks on node "B". This resulted in queued chunks being left untouched. To resolve this, the logic has been updated to allow multiple nodes to process the chunks.
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-D43808 · Issue 512662
Resolved loop causing search to fail
Resolved in Pega Version 8.4
After upgrade, searching for a case caused node failure. This was traced to a system loop when trying to remove duplicate workpool classes and has been resolved by updating the pyPopulateWorkPoolsAndClassesForTagsSearch activity to remove extra looping on workpool classes in step 3. In addition, a new 'when' rule pyIsTagSearchEnabled has been added: the pySearchWrapper activity will only search tags when this rule is true.
SR-D50137 · Issue 528824
Resolved loop causing search to fail
Resolved in Pega Version 8.4
After upgrade, searching for a case caused node failure. This was traced to a system loop when trying to remove duplicate workpool classes and has been resolved by updating the pyPopulateWorkPoolsAndClassesForTagsSearch activity to remove extra looping on workpool classes in step 3. In addition, a new 'when' rule pyIsTagSearchEnabled has been added: the pySearchWrapper activity will only search tags when this rule is true.
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.
INC-191970 · Issue 680396
Updates made for reviewing online case in an offline app
Resolved in Pega Version 8.7
After developing a Field Service Mobile app on Pega 8.3, updating and assessing the Mobile App on Pega 8.6 resulted in a flicker in the back arrow for returning to the work list. This was traced to WebViewManager not being available for online cases in offline apps, and has been resolved by adding an update that will use attachOnload/detachOnload if WebViewManager is not available. In addition, an issue with creating a space or document on mobile has been corrected by using the onViewRendered method instead of attachOnload for the offline app case.
SR-D37117 · Issue 511358
Update Survey Work Objects' utility differentiates between survey and other objects
Resolved in Pega Version 8.4
Running the Update Survey work object utility calls the “pxUpgradeSurveyProperties” datatransform, which has a 'when' rule to call the function “@pzSurveyUpgradeSetProperty” to replace the Questionnaire page in the first step. This function was failing with a logged exception when it was passed a string instead of the page it was expecting. This issue occurred when the WO did not have survey data structure, and was due to the Survey Utility being intended to upgrade only Pega Survey class instances. In order to allow for more flexibility, the Survey Upgrade Utility has now been enhanced to differentiate between survey and other objects to resolve the exceptions.