SR-B68425 · Issue 319425
Text input focus corrected for repeating dynamic layout
Resolved in Pega Version 7.3.1
Clicking on the label of a text input for the second section in a repeating dynamic layout shifted focus to the first section's text input. This was caused by a missing repeating index for the attribute of the label when used in a RDL and has been fixed.
SR-B56367 · Issue 313698
Query updated for Oracle DDL generation
Resolved in Pega Version 7.3.1
When using a class mapped to an external database view, creating a RAP that included a Data-Admin-DB-Table instance in a lower environment for import into a higher environment resulted in invalid generated DDL for the view. This was due to a column alias list in the view definition not being included in the generated DDL, and has been fixed by using a different metadata query for Oracle to ensure the column list is returned if it was originally specified.
SR-B67316 · Issue 317299
Query updated for Oracle DDL generation
Resolved in Pega Version 7.3.1
When using a class mapped to an external database view, creating a RAP that included a Data-Admin-DB-Table instance in a lower environment for import into a higher environment resulted in invalid generated DDL for the view. This was due to a column alias list in the view definition not being included in the generated DDL, and has been fixed by using a different metadata query for Oracle to ensure the column list is returned if it was originally specified.
SR-B53073 · Issue 313234
Handling fixed for properties with a leading dot
Resolved in Pega Version 7.3.1
Inconsistencies were seen in working with properties across different browsers: 1. If a field was set as requiring entering a property, pressing the arrow down to select the first value (i.e. topmost Page Name) caused the focus to point to the icon to the right of the control in Microsoft Internet Explorer and Google Chrome. 2. If it was not a required field, the focus was kept and the property could be set without using the mouse to reposition the focus to the field when in Microsoft Internet Explorer or Firefox, but only after HF was installed in Google Chrome and not for Autocomplete control. 3. When configuring Autocomplete control, the 'dot' disappeared when entering property names of embedded pages from the report based on exposed property when using Microsoft Internet Explorer, or if HF was installed in Google Chrome. This was found to be an issue where the non-required fields having a dot as prefix were having that starting dot trimmed off. To fix this, a check for extra dots has been added before trimming.
SR-B4034 · Issue 306173
Fixed data mismatch from parallel schema migration
Resolved in Pega Version 7.3.1
When a queue method in a loop inside an activity was used to create separate work objects and in parallel migrate work object data from one DB schema to another, running that queue method more than once caused the Source table columns and destination columns to have mis-matched datetime property values after migration. This was an issue where the same DateFormat object was being used by two batch requestors. To resolve this, whenever the requestor object is destroyed, the date format object used for database operations will be made null.
SR-B53383 · Issue 313525
Fixed JAWS reading icon header incorrectly in Microsoft Internet Explorer
Resolved in Pega Version 7.3.1
When using Microsoft Internet Explorer, JAWS was reading the icon headers of a repeat grid configured with a filtering option as 'Click to sort' instead of 'Click to filter'. This was due to the aria-label being missed on filter links, and has been fixed.
SR-B70222 · Issue 322936
Property value submit event for screen flow works in Microsoft Internet Explorer
Resolved in Pega Version 7.3.1
FinishAssignment Action was configured as an Enter Key event for Dynamic layout in order to submit the flow in screenflow, but at runtime when using Microsoft Internet Explorer some of the property values were not submitting to the clipboard as expected. The issue was a defect in the UI framework related to submitting a form through any event when the input had focus in Microsoft Internet Explorer, and a check has been added to resolve the error.
SR-B41316 · Issue 306255
Resolved missed cases in the WO case tree
Resolved in Pega Version 7.3.1
Sometimes several cases were missed in the case tree, shown in the right side of an opened WO. Access was not available for the corresponding WO and assignments. The root cause was a WHEN condition in WORK-COVER- PZLOADNESTEDCASESFORCLASS property "local.ProcessedItemKeys" containing numbers of processed WOs separated by a space, for example, "KPI-101 KPI-72 KPI-52". The WHEN condition checks for presence using "contains", leading "KPI-10" to be ignored and not displayed in cases where "KPI-101" already presented. To correct this, the system will consider the delimiter "\t" while checking the WHEN condition.
SR-B41316 · Issue 306260
Resolved missed cases in the WO case tree
Resolved in Pega Version 7.3.1
Sometimes several cases were missed in the case tree, shown in the right side of an opened WO. Access was not available for the corresponding WO and assignments. The root cause was a WHEN condition in WORK-COVER- PZLOADNESTEDCASESFORCLASS property "local.ProcessedItemKeys" containing numbers of processed WOs separated by a space, for example, "KPI-101 KPI-72 KPI-52". The WHEN condition checks for presence using "contains", leading "KPI-10" to be ignored and not displayed in cases where "KPI-101" already presented. To correct this, the system will consider the delimiter "\t" while checking the WHEN condition.
SR-B56485 · Issue 312961
Mashup gadget cookie requests consolidated in Safari
Resolved in Pega Version 7.3.1
In order to resolve an issue when using Safari where Pega was displaying a message to allow cookies for every Mashup gadget, the isCookieConsentRequired method in PegaCompositeGadgetMgr.js has been updated to check if the host URL and gadget URL are the same to avoid duplicate messages.