SR-D76927 · Issue 541421
VirusCheck added to all Pulse uploads
Resolved in Pega Version 8.3.2
The upload file activity has been updated to invoke VirusCheckActivity for all Pulse uploads.
SR-D81859 · Issue 543764
Maps and signatures inside layout groups scroll correctly
Resolved in Pega Version 8.3.2
A map configured in the screen was getting grayed out while scrolling horizontally. Analysis showed that when an address map is inside a layout group, the layout group swipe was triggered instead of scrolling. To resolve this, the target parent now has the data attribute "data-nogestures" = true so the layout group swipe will not be triggered. This will also prevent swipe on signature while scrolling horizontally.
SR-D74246 · Issue 543724
Accessibility improved for Pega Survey Question pages
Resolved in Pega Version 8.3.3
Question Pages in Pega Survey lacked accessibility. This was traced to aria-label not being generated for Radio buttons and Drop-downs, and "title" not being generated for other controls used in Question and Question Pages. This has been resolved.
SR-D68572 · Issue 543002
Added check for duplicate attachment names with S3
Resolved in Pega Version 8.3.3
S3 Storage does not allow duplicate file names, but the AttachContent function was allowing duplicate file attachments. Due to this, the sync was failing to attach on the server and the message was never communicated to the client. This has been resolved by adding a check for duplicate file names when the storage is repository.
SR-D89427 · Issue 548936
Corrected Microsoft Internet Explorer displaying checkboxes as sliders
Resolved in Pega Version 8.3.3
Checkboxes were displaying as sliders in IE version11.1304.17134.0 due to IE returning Table pc 2.0. Since Pega HTML class includes tablet, .tablet related styles were getting picked up and displaying the checkboxes in tablet mode. To resolve this, a check has been added to pyIsTablet to evaluate correctly at runtime.
SR-D85780 · Issue 547813
Corrected iosVersion handling for getDirections
Resolved in Pega Version 8.3.3
When opening the map function in the iPhone app, it first navigated to Google maps but clicking on 'get directions' opened Apple maps. This was traced to pzpega_control_actions_getDirections. When using the getMapURL function the value being assigned for iosVersion dictates the behavior: If the iosVersion is greater than 8 it opens Google maps, else Apple maps. However, an error caused the value to be sent as string instead of integer, causing the iosVersion check to fail. This has been corrected.
SR-D83630 · Issue 546142
IsQuestionHidden property added to skip validating hidden questions
Resolved in Pega Version 8.3.3
After configuring a simple question which had a validation rule defined on it and a display 'when' rule configured to show or hide it based on another question condition validation was still being fired on the hidden question and it was not possible to proceed. This has been resolved by adding code to skip validations for a question if it is hidden, based on the pzIsQuestionHidden property.
SR-D86079 · Issue 548108
Label truncation added for pinned item title
Resolved in Pega Version 8.3.3
While pinning a Space, document, or URL, the length of the item title was causing validation issues if it exceeded 64 characters. This has been resolved by modifying the pzGetPins activity to truncate pyLabel to 64 characters using the truncateLongText function.
SR-D73237 · Issue 539124
Pagination updated to resolve repeating Pulse notes
Resolved in Pega Version 8.3.3
After adding a case and entering 15 Pulse notes, scrolling down resulted in the notes being duplicated. Investigation traced this to entering more than 10 posts in a single interaction on a previously empty case when "Progressive pagination" was enabled for the repeating dynamic layout. On Private Edit, if the pagination was changed to "NONE" then the issue was resolved. Pagination depends on the pzPagingStartDateTime property, which is set on D_pzFeedParams, but since there were no results in this scenario this property was not being set. To resolve this, an update has been made so that pzPagingStartDateTime will be set if it is empty.
SR-D76620 · Issue 544576
Resolved touch events issue with updated Google Chrome
Resolved in Pega Version 8.3.3
After upgrading Google Chrome, touch events on a flow action under the Action Button in a case or on the application under "Launch web interface" were not reacting and the flow actions were not accessed. Investigation showed that Google Chrome's latest upgrade (79.0.3945.130) removed the ontouchstart property in the window, causing the isTouchable capability identification method to fail. This has been resolved by adding a check for navigator.maxTouchPoints to identify for Google Chrome whether the device involved has a touchscreen.