SR-B85963 · Issue 339603
Resolved duplicate Guardrail warnings
Resolved in Pega Version 7.4
Duplicate guardrail warnings were appearing in the DT and Section rules due to multiple warnings being generated with the same time stamp. To fix this, the system will use the synchronized timestamp function to ensure the created time is different for each warning.
SR-B85963 · Issue 338180
Resolved duplicate Guardrail warnings
Resolved in Pega Version 7.4
Duplicate guardrail warnings were appearing in the DT and Section rules due to multiple warnings being generated with the same time stamp. To fix this, the system will use the synchronized timestamp function to ensure the created time is different for each warning.
SR-B86181 · Issue 334246
Cursor behavior fixed in search text field
Resolved in Pega Version 7.4
The cursor was moving ahead when typing search text in a filter grid, causing typos. This was an unintended side effect of a fix to the method used when focusDomElement is called in settimeout, and has been fixed.
SR-B86753 · Issue 339777
Mouse resize of modal dialog fixed
Resolved in Pega Version 7.4
After opening a flow in a modal dialog and resizing the first window by using the mouse (drag bottom-right corner), the resize option disappeared after proceeding to the next assignment. In this case, when back-to-back assignments were executed in the modal dialog, the resizehandler was not registered when navigating to the second assignment as the modal dialog was not initialized again but instead used a section refresh. A script has now been added to call pega.u.d.modalDialogExtras in pzModalActionAreaContainer if the resize handler is not available for back-to-back assignments.
SR-B90586 · Issue 340645
Baseref set correctly on Microsoft Internet Explorer 11 action launch
Resolved in Pega Version 7.4
An 'Activity status error' appeared when trying to launch a local action upon click of a menu item on Microsoft Internet Explorer 11. Investigation showed this was due to the 'Basereference' not being set in Microsoft Internet Explorer because it was being calculated on a stale element, and this has been fixed by calculating the proper live element when the baseref is null.
SR-B93716 · Issue 340451
Grid summary added for accessibility
Resolved in Pega Version 7.4
pzRBShortcutsGrid7 now includes a Grid Summary to enhance accessibility.
SR-B97228 · Issue 343365
Added support for imported flow stage ID in DS dropdown
Resolved in Pega Version 7.4
In Designer Studio, any flow rule that contained a Change Stage flow shape imported from a previous version that was configured to go to a specific stage name displayed an incorrect value in the dropdown list. This was due to the difference in the application versions: Previously, Stage ID was used in Flow metadata while recent versions support both ID and Name. The UI depends on the Name to show the drop down, meaning imported flows were not passing the needed information. To make the system more robust, a new 'when' rule has been added to pzIsIDUsedInChangeStage to decide whether to show the Name or ID.
SR-C3153 · Issue 345296
Manage review team error fixed
Resolved in Pega Version 7.4
Any action in "Manage review team" function inside branch review was showing an error. This has bene fixed by passing a missing parameter as AssociationClass:"Link-Association".
SR-C3921 · Issue 349058
Handling added for idled WO with empty values
Resolved in Pega Version 7.4
After opening a work object and then idling it for at least 15 minutes, trying to perform a Word merge resulted in HTML code being inserted into previously empty values. This has been corrected.
SR-C6529 · Issue 350614
Edit Pipeline trigger on merge state resolved
Resolved in Pega Version 7.4
The property "pyStartBuildOnBranchMerge" (which corresponds to the UI setting called "Trigger build on merge" on the 'Add Application pipeline') was not changed as expected when using the Actions>Edit Pipeline to alter the state of "Trigger build on merge". This was true whether the option was being switched OFF or ON, with the setting remaining fixed at its original state. This was traced to pyStartBuildOnBranchMerge persisting after being deleted, and has been resolved by defaulting the value of pyStartBuildOnBranchMerge to false to allow the calculation of the pyStartBuildOnBranchMerge state to work correctly.