INC-138501 · Issue 592287
Added VBD support for CSRF token setting
Resolved in Pega Version 8.5.2
Attempting to open any VBD reports in the marketing portal for a simulation test caused the user to be logged out. Investigation showed that this happened when CSRF token check was enabled in System > Settings > Cross-Site Request Forgery, and was caused by the planner not passing the CSRF tokens in its Ajax calls. To resolve this, handling for the CSRF tokens has been added to the necessary Ajax calls.
INC-143531 · Issue 598644
Dirty Flag reset updated
Resolved in Pega Version 8.5.2
After opening a case in Cosmos, making updates, and then navigating away without saving, the dirty flag message appeared as expected and offered the option to save, discard, or cancel. After clicking on save and opening the next case, performing the same steps did not cause the dirty flag to display when navigating away. This has been resolved by updating the reset of the isDirtyDialogOpen inside the hide API of a modal close.
INC-175672 · Issue 652944
ServicePackage threads properly released
Resolved in Pega Version 8.7
After completing a system stress test, the requestor pool threads for the ServicePackage were not released. Investigation showed that the threads were waiting for Data Pages to be loaded in the background even though there was no background job corresponding to those data pages in the Async Services pool. This has been resolved by making an update to avoid removing the object handlers when the load-datapage finds that an entry exists with a NOT_STARTED state.
INC-187708 · Issue 680012
Handling added to StreamChangeTracker for non-String mode
Resolved in Pega Version 8.7
Incorrect StreamChangeTracker mode properties were being tracked for value changes. Investigation showed this was due to the StreamChangeTracker.trackValueChanges API tracking value changes on properties of mode page and page list, which resulted in logging a WrongModeException in the logs. This has been resolved by updating the behavior of the StreamChangeTracker.trackValueChanges API to return false when value change tracking is invoked for a property other than mode String.
INC-146237 · Issue 608744
Corrected popover scroll for AnyPicker
Resolved in Pega Version 8.5.2
Using the AnyPicker control caused display problems. In the initial display of the selection list, the line of choices and the search field overlapped and they were displayed from the second line of choices which forced the user to scroll up to see the first line. After displaying the selection list, clicking outside the selection list without selecting anything to close the list and then displaying the selection again caused the options to be displayed from the 4th line, requiring a scroll up to see lines 1 to 3. This has been resolved to ensure the Scroll on Popover goes to the first element.
SR-D11980 · Issue 484186
Resolved missing feedback entry update
Resolved in Pega Version 8.2.3
An issue with the Feedback entry not being updated in the manual triage process was traced to a local configuration which loaded the D_pxEmailPosts data page on 'send feedback' instead of upon opening the email triage case (or Interaction case). This difference caused the required ChannelConfig page to be removed from the 'pyCheckIfHtmlOrPlainText' activity so ModelName was not populated for use by pzSendFeedbackToNLP. ModelName is a required property to send feedback. To resolve this, an update has been made to ensure Work-Channel-Triage.pyCheckIfHtmlOrPlainText will not remove the ChannelConfig page.
SR-A17183 · Issue 241734
Swimlane flow connectors visible after upgrade
Resolved in Pega Version 7.2.1
After upgrade, some of connectors between the flow shapes were not appearing as expected when opening flow rules forms designed with Swimlane even though the flows ran as expected. Attempting to amend the flow rules by reconnecting the shapes caused the ruleform save to fail. This issue stems from problems opening the Decision Tree rule Data-MO-Connector-Transition.pyBuildLabel on a Pega 7.1.8 system. This has been fixed.
SR-A17544 · Issue 236778
Removed pagination size restriction on listview if page size is set
Resolved in Pega Version 7.2.1
When an application had more that 50 data-types, not all data-types were shown in the application packaging wizard due to the page size being set to 50 while the list view function was set to return a maximum of 50 results if pagination was enabled. The pagination size limit on listview has been disabled in cases where page size is set in order to remove this conflict and display the results as expected.
SR-A17758 · Issue 234057
Check added to avoid duplicate encryption
Resolved in Pega Version 7.2.1
When a property of type TextEncrypted was edited from the clipboard viewer, the encrypted value was being encrypted again. This was caused by the server side trimming the string values of parameters sent in a post body, removing '\t' from the encrypted value '\t{ps}XXXXX' and triggering encryption of an already encrypted value. To prevent this, the system has a check for strings starting with '\t{ps}' at the time of parsing URL Parameters or post body.
SR-A18100 · Issue 234215
BIX documentation updated for new "-J" timezone conversion option
Resolved in Pega Version 7.2.1
A -J option has been added to BIX to allow the specifying the timezone for datetime properties to be converted to when written to the XML output file. The documentation is as follows: A new command line option J is being added to take in a user specified time zone for e.g., UTC+05:00 format(s); If the specified timezone is not valid, it defaults to GMT example :How to specify this option: "-J" "UTC+5:30"