SR-D36176 · Issue 508406
Work List loads as expected in Microsoft Internet Explorer
Resolved in Pega Version 8.2.4
After upgrade, the Work List was not loading in Microsoft Internet Explorer. This was an unintended side effect of work done to handle resizing the Recents list when another tab was open, and that change has been reverted to resolve this issue.
SR-D40617 · Issue 507565
Escape added to Radio button field value to handle HTML tags
Resolved in Pega Version 8.2.4
A radio button with a field label to display a help icon and to open the help URL when the icon was clicked did not display as intended. Changing the control to text area produced the desired results. This was traced to the radio button's label being assigned to a field value which returned a string that at some points contained HTML tags, and has been resolved by escaping the pyLabelFor value before assigning it to the aria-label attribute of the radio button's div tag.
SR-D38946 · Issue 507906
Dragresize plugin removed from RTE for better Microsoft browser compatibility
Resolved in Pega Version 8.2.4
When a messge was sent through Pega chat while using the Edge web browser, the text field where the message was entered before the send button was pressed did not get cleared. This was traced to the Edge browser throwing a Permission Denied error while attempting to access a detached DOM element. To resolve this, the 'dragresize' plugin has been removed from RTE as its implementation is not compatible with Microsoft Internet Explorer 11 and Edge.
SR-D39455 · Issue 508605
Shortened URLs (bit.ly) supported with custom image size
Resolved in Pega Version 8.2.4
Marketing offers were very slow to load, often generating requestor lock exceptions due to the wait time. This was traced to one cell in one section that housed a company logo: the source to icon had a shortened "bit.ly" URL when the ImgaeIO API in Java expected the actual URL as its input. The API could not convert the shortened URL to the actual URL, resulting in the retries and connection failure. To resolve this, 'javax.imageio.ImageIO' invocation will happen only when the image size is auto. If custom height and width are used to display an image, Pega will not depend on the Java library and the system will be able to resolve the shortened URL.
SR-D42143 · Issue 509316
Tab names maintained after Ajax container refresh
Resolved in Pega Version 8.2.4
When using an Ajax container in Tabs mode, a browser refresh with multiple tabs opened caused the active tab name to be changed to the main tab name. This was caused by the work object name being lost during the refresh, and has been corrected.
INC-135335 · Issue 588510
Parent flow next step will take precedence over sub-process
Resolved in Pega Version 8.5.1
A Breadcrumb configured in the screen flow was not displaying at the last assignment when there were multiple embedded sub processes and the last assignment was called in a sub process. This was traced to the parent flow next step information not being passed due to the next step in the sub process being marked as an end shape. To resolve this, the pzFlowSteps7 html control has been updated to pass the parent flow's next step information in this situation.
SR-D77719 · Issue 569769
OpenIfStale updated to resolve optimistic locking race condition
Resolved in Pega Version 8.5.1
A race condition was created in optimistic locking by having two assignments save at overlapping times. This has been resolved by modifying the pzShowConflicts activity to use a version of openIfStale which will consider a workpage as stale even if the difference in pxUpdateDatetime is in milliseconds.
INC-134912 · Issue 581326
Handling updated for wait shapes with different outgoing connector flow actions
Resolved in Pega Version 8.5.1
After configuring a flow with a wait shape that by default used the pyContinueAfterWait flow action for the outgoing connector of the wait shape refer, adding any other valid flow action resulted in the error "Action To Take must be a valid flow action for this assignment". This was due to the post-processing of the connector properties modal updating the ActionToTake value based on wait shape, so that changing the flow action on a connector caused the validation on save to fail if the ActionToTake on wait shape and the connector flow action did not match. To resolve this, the system has been modified to validate a wait shape with different flow action on the outgoing connector.
SR-D59283 · Issue 523207
Check added for WorkParty property to catch changes
Resolved in Pega Version 8.5.1
After configuring a send email shape to send email to work parties, proceeding through the flow without work parties and then triggering the send email shape and creating the Fix correspondence assignment worked as expected. If the work party details were later updated and the send email shape was triggered again for the Fix correspondence assignment, the error message "No role defined to work object" appeared. This was an issue with the handling of the email flow the second time through: PyCorrPage.pyCorrPartyRole did not have the work object party details which were added to the work object after the fix correspondence assignment was created, and SendSimpleEmail was not designed to handle the email that needs to be retried during the FixCorrespondence flow call. To resolve this, the system will check whether the pyWorkParty property exists prior to calling the PartyCorrPreferences HTML rule.
INC-136208 · Issue 585226
Case history filter added for manual instantiation of Child Case
Resolved in Pega Version 8.5.1
After upgrade from v7.4 to v8.3, creating any child case from a parent case unexpectedly added the audit history "Child case xxxxx has been manually instantiated" to the parent case. In order to make this customizable, an "isHistoryAvailable" function has been added in the 'when' condition of "AddCoveredWork" Activity's "History-Add" Step. This will use the FilterHistory decision tree, which now has a setting for "ChildCaseInsAudit" to control whether or not the manual Instantiation of a Child Case will appear in the case history. The default is "true"; setting it to "false" will suppress the message.