SR-B81856 · Issue 335124
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-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-C82619 · Issue 421023
JavaILCompiler updated to skip a type convert when generating code for a ternary operation
Resolved in Pega Version 8.3
A compilation error was generated when attempting to save a Data Transform with a java expression giving the ternary as boolean. In this case, the pyWorkPage.Channel was set to @java("tools.findPage(\"TempInputAccelPage\").getProperty(\"Channel\").getMessageCount()>0") ? "" : pyWorkPage.Channel.
The system previously used EL code generation, which had a gap which allowed such expression to work. Since the system now uses IL code generation, this expression failed. In order to ensure backwards compatibility, logic has been added to JavaILCompiler to skip a type convert when generating code for a ternary operation where the source is ILProgramText (java expression).
SR-C79523 · Issue 421039
Updated the documentation for enabling debug logging during upgrades
Resolved in Pega Version 8.3
The documentation regarding enabling debug logging during upgrades has been updated to reflect the following information: To enable debug logging during installs, upgrades or prpcUtils invocations: The template logging configuration for installs, upgrades and prpcUtils is located within the scripts/config directory of the Pega Platform distribution. To change what gets logged, modify the prlog4j2.xml file (refer to https://logging.apache.org/log4j/2.x/manual/configuration.html#XML). Some of the utilities involved in the install and upgrade processes use java logging. To impact what is logged by these tools, modify the deploylogging.properties file in the same directory.
SR-D8794 · Issue 483814
Import ordering shifted to prioritize Functions and Libraries
Resolved in Pega Version 8.3
A runtime error was seen when running DataTransform getbranchandcbsadetails. Investigation showed that when getbranchandcbsadetails was imported, the RUF it referenced was not imported beforehand. To resolve this, the import ordering has been reworked to prioritize Function and Libraries by shifting Rule-Utility-Library and Rule-Utility-Function to be after Rule-Obj-Property* in the import order.
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.