INC-136768 · Issue 588452
Question Wizard import will downcase answer types to match system requirements
Resolved in Pega Version 8.3.5
The Question Upload wizard would not create a File type question while using a survey template. The template has a column Answer mode in which accepts an input of the type of answer expected, but in this use case "File" was given instead of "file", resulting in the question being created using the default values. To resolve this, during the import process when the system parses the file and gets the contents from the data using the pzSetdefaultValuesforQuestions DT, mode values will be explicitly set to lowercase.
INC-148099 · Issue 607290
Resolved button flicker
Resolved in Pega Version 8.3.5
The buttons were flickering when moving between screens in an offline-enabled mobile app. This has been corrected.
INC-146521 · Issue 602657
Survey Question Page Radio/Dropdown Button retains value
Resolved in Pega Version 8.3.5
After creating an Interaction from the portal and selecting "Survey", the Survey Question Page using a Radio button/Dropdown button as Question did not retain the value after a selection was made. This has been resolved by modifying the refreshSurvey method in pzsurvey_ui_userscript.js to work with an Ajax container.
INC-144311 · Issue 601109
Updates for nested "Append And Map To"
Resolved in Pega Version 8.3.5
Nested actions "Append And Map To" in Data Transforms were producing incorrect results when offline. This was traced to all operations being performed on the Page List which was on first level of nesting, which was caused by changing the Data Transform into JavaScript form for offline use. The JavaScript form of DataTransform uses variable the "targetListObj" to represent the Page List, and this same name was reused regardless of the "Append And Map To" nesting. An additional problem was seen with the "Update Page" Data Transform action when used with conjunction with a nested "Append And Map To" action: the action assumes that top level Pages exists, but "Update Page" did not create them. This caused the "Append And Map To" action to fail. To resolve this, the "Append And Map To" action will use suffixed variable names to reference nested PageLists, and "Update Page" will create the Page if it doesn't exist.
INC-144566 · Issue 600857
User lookup list correctly populated when using # tag
Resolved in Pega Version 8.3.5
When typing '#ANewTag @' in Pulse, the user lookup list was not shown. Using '#ExistingTag @' worked as expected. This was a missed use case in work done to improve the performance of pzJquerymentionsInput by restricting REST calls, and has been resolved.
SR-D68235 · Issue 534783
Stale WorkSearchPreference data cleared when switching apps
Resolved in Pega Version 8.4.1
The D_pyWorkSearchPreferences data page data was not refreshing while switching between apps, causing stale data to be populated under the case search dropdown for all the applications after switching the application from one to another. This has been resolved by removing the D_pyWorkSearchPreferences data page as part of pzProcessApplicationSwitch.
SR-D73536 · Issue 538403
FetchApplicationLogo modified to Filter by rule resolution
Resolved in Pega Version 8.4.1
It was observed that the Report Definition rule "pzFetchApplicationLogo", referenced by Activity rule "pzLoadApplicationLogo", always returned the older version of the Binary File "webwb • pyapp-logo • svg" because it had been set to retrieve a maximum of one record and in this case the results were sorted in an order where the oldest record was at the top. As the Report Definition did not indicate any sorting, most DBMS were returning the results in no particular or predictable order. To resolve this, "Filter by rule resolution" has now been enabled for RD pzFetchApplicationLogo.
SR-D76291 · Issue 547843
Updated retry logic for S3 AddAttachmentFromEmail
Resolved in Pega Version 8.4.1
When using the AddAttachmentFromEmail activity with S3 repositories, performing an obj-save on the data-workattach-file page executes a deferred save while also saving the file into the repository. if the data was inserted into S3 successfully but encountered an issue when saving the related data-work-attach-file page, the system was trying to call the save operation again. This tried to insert the duplicate attachment again to S3, causing an error on that side of the process. To resolve this, the duplicate Obj-Save functionality in AddAttachmentFromMail Activity has been removed.
SR-D79113 · Issue 543723
Updated DisplayAttachment to handle SIngleClick download from Case Worker portal
Resolved in Pega Version 8.4.1
On using the script "pega.ui.HarnessActions.doAttachmentSingleClick" in the Worker portal to download attachments displayed within a screen flow, the entire application was hanging and no action was invoked even on clicking the Continue or Finish buttons of the screen flow. Whenever an attachment is downloaded using the script function pega.ui.HarnessActions.doAttachmentSingleClick() , an iframe is used and changetracker is called to communicate data between different iframes. However, the case worker portal is a single thread model while the manager and admin portals are multi threaded, which resulted in changetracker freezing on the worker portal. To resolve this, the DisplayAttachment HTML rule has been updated to build the necessary changeTrackerMap for the worker portal.
SR-D84480 · Issue 546189
FilterHistory decision tree used for audit log status
Resolved in Pega Version 8.4.1
Attempting to use the “FilterHistory” decision tree in the work class to return value “false” for “pyCloseOpenAssignmentsOnResolution” to hide the “pyCloseOpenAssignmentsOnResolution” field value (“Unfinished assignments were cleaned up by the system after the completion.. ”) from history was not working as expected, and still returned the audit message. This was due to the system setting this AuditNote parameter within the “pzProcessResolutionStage” activity, where Param.UpdateHistory was set to true always. In order to support more flexibility, the Param.updateHistory paramter in step3 of the pzProcessResolutionStage activity will be set based on the FilterHistory decision tree. When set to false in FilterHistory decision tree, pyCloseOpenAssignmentsOnResolution will be set as false and audit will not be logged.