SR-A8640 · Issue 219698
Display styling updated for Team Members Widget Counts
Resolved in Pega Version 7.2
In the out-of-the-box Team members widget, the counts displayed for each user sometimes appeared outside the container boundaries or displayed on top of other sections. This was due to the operator name length; even when truncated, the widget did not correctly account for the text. The styling handling has been updated to display the counts correctly.
SR-A9389 · Issue 219242
File name truncation used for File Listener recovery
Resolved in Pega Version 7.2
The Property Data-WorkAttach-.pyNote default of Max Length = 60 caused a failure in File Listener's recovery mode if the system added a long string at the end of the file name. This has been fixed by trimming and setting pyNote if the length is more then 60 characters.
SR-A11350 · Issue 223222
RestartStage and StartStageProcess APIs update WorkPage properly
Resolved in Pega Version 7.2
The pxRestartStage API "pxStageHistory" was not updating the pyWorkPage when performing the restart stage or when there were no steps in a stage at run time inPega7Express and steps were added through the case life cycle gadget. The RestartStage and StartStageProcess APIs have been updated to properly handle these scenarios.
SR-A10189 · Issue 222038
Handling added to set baseclass when using Bulk as Update
Resolved in Pega Version 7.2
The use case was missing to properly handle setting the baseclass when Bulk action was selected as an Update process. This has been added.
SR-A10163 · Issue 221183
Fix added for accessing WO correspondence using Microsoft Internet Explorer11
Resolved in Pega Version 7.2
When using Microsoft Internet Explorer11, the error ?Error-Open Authoring control failed to load? was generated when attempting to access correspondence attached to a work object. This has been fixed.
SR-A8915 · Issue 220454
Jump-back page reference fixed for Tree Navigation and TabbedScreenFlow
Resolved in Pega Version 7.2
When starting a ScreenFlow from a SplitForEach using using TreeNavigation7 and TabbedScreenFlow7, the navigation harnesses were not taking the correct interested page for a jump-back on a previous assignment. This has been resolved.
SR-A11101 · Issue 223556
Enhancement added to hide Pega Pulse delete icon/link
Resolved in Pega Version 7.2
When using Pega Pulse for communication with a company's end users, it was possible for the end user to delete a message. This was not desired behavior in scenarios where the company wants full tracking of the interactions with the end users. To accommodate this, an enhancement has been added to allow the delete button to be hidden on the client user side based on 'when' conditions through use of the new rule 'pyCanDeleteReply'.
SR-A13044 · Issue 226206
insHandle updated to resolve PrintWork OOM error
Resolved in Pega Version 7.2
When PrintWork activity was called with an empty insHandle, the activity tried to fetch all the attachments with pxInsHandle as null, causing an out of memory error. To avoid this, a check has been added to skip fetching attachments if the inshandle is blank.
SR-A10040 · Issue 219561
Section refresh added to Integrator shape
Resolved in Pega Version 7.2
The Integrator shape in Data class was not showing parameters in the properties screen. A section refresh has been added to "pzIntegratorTab" that will be triggered upon selection of the rule in the integrator
SR-A10040 · Issue 219304
Section refresh added to Integrator shape
Resolved in Pega Version 7.2
The Integrator shape in Data class was not showing parameters in the properties screen. A section refresh has been added to "pzIntegratorTab" that will be triggered upon selection of the rule in the integrator