SR-D90367 · Issue 556686
Cleanup enhanced for long pyEditElement names
Resolved in Pega Version 8.2.7
A pyEditElement error relating to decision data was seen multiple times in a stack trace. Research showed that while the utility worked as expected for decision data rules with names of less than 30 characters, the pyEditElement section was truncated the name for the decision data. This meant that decision data with the name SampleIssueandSampleGroupTwosalkdjkightntbmkblffvfvfv would be saved as SampleIssueandSampleGroupT for the pyEditElement section. Because of this, the utility failed the match and did not clean up the pyEditElement section. To resolve this, the cleanup utility has been updated to handle pyEditElement sections of decision data with longer names. Additional logging has also been added to improve debugging.
SR-D90579 · Issue 550769
Real Time data flow exception during shutdown corrected
Resolved in Pega Version 8.2.7
A Real Time DataFlow run was failing with a java.util.concurrent.RejectedExecutionException. This occurred when the node was shutting down while picking up a partition, and was due to the life cycle events not being able to update the partition status. To resolve this, a check has been added to prevent the exception form occurring by evaluating whether the Executor is shutdown while distributing messages.
SR-D96836 · Issue 555748
Refinements made to MarkerNode memory use
Resolved in Pega Version 8.2.7
Significant memory usage can be observed when data join in strategies are missing the join conditions. E.g., when the primary source in the strategy can have up to 300 or even more propositions, the join without the join condition would perform a cartesian product with possibly up to 400 or even more records returned. This may cause performance degradation. To guard against this, an update has been made that seeks to prevent repetitive markers being accumulated under a MarkerNode while trying not to rely on any implementation of equality and hashCode for individual marker implementations.
INC-120326 · Issue 564435
Landing page refresh modified to avoid frequent reloads
Resolved in Pega Version 8.2.7
Approximately every two weeks, clients were able to login but it was not possible to work as the landing page refreshed constantly until all of the nodes were rebooted and the issue was cleared. Investigation indicated the frequent reloads were related to the cacheing of the operator details, and this has been resolved by updating the datapage reload strategy based on 'when' so frequent reloads will be avoided.
SR-D68572 · Issue 543003
Added check for duplicate attachment names with S3
Resolved in Pega Version 8.2.7
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-D77580 · Issue 550093
Corrected Survey button refresh issue
Resolved in Pega Version 8.2.7
After implementing a Pega Survey question page with dynamic / reflexive questions (Answer to Question 1 determines Question 2 and so on) where every answer pick caused a refresh, picking various radio buttons quickly caused an unexpected busy indicator. Investigation showed that on click, both refresh section and run activity were executed asynchronously, triggering the property mapping refresh before answers were clicked. To correct this, the clearSelection function call in pzsurvey_ui_userscript JS file has been modified, and questionPageName has an added 'if' condition.
SR-D81500 · Issue 554903
Uploading Pulse attachments made more robust
Resolved in Pega Version 8.2.7
Upon uploading a file in the Pulse section for a case created in the Case Worker portal, the error message "File <filename> doesn't exist or is empty" appeared. This was traced to using a third-party repository when the network was slow, and has been resolved by instituting the use of callbacks/timeintervals to execute a particular function call only after getting proper results.
SR-D83548 · Issue 544307
JMS push notification made more robust
Resolved in Pega Version 8.2.7
After creating a JMS Service to call pySendPushNotification from an activity, running it using User Context worked as expected but selecting initialize Service Context resulted in the Push notification silently failing in the context of JMS service. The JMS is used as a communication medium between legacy and Pega solutions. When the message arrives, Pega creates a new case and sends a push notification to the user, who has only 2 minutes to accept the case. Because of the urgency of timeliness in this situation, the push is sent directly from the context of the service rather than expend 30 seconds for agent processing. However, because the application was not always available to the pySendPushNotification activity (and further to API call), the push failed. In order to avoid this condition, the system has been modified to use the more widely available pxThread instead of Application when possible.
SR-D85624 · Issue 552695
Corrected browser displaying checkboxes as sliders
Resolved in Pega Version 8.2.7
Checkboxes were displaying as sliders in Microsooft internet Explorer version11.1304.17134.0 due to the browser 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-D90279 · Issue 554390
Data sync updated for use with DeferWrite
Resolved in Pega Version 8.2.7
After update, attempting a data sync from the client mobile application worked for the first object submission, but the second object failed and stayed in the list. This was traced to finish assignments running back to back when deferWrite was enabled and svcPerformFlow failed to find the assignment. To resolve this, the assignmentHandle will be passed to the activity when calling the pzSetDeferWrite activity from FinishAssignmentActionProcessor.