SR-B5417 · Issue 274794
Logic added to convert UTC Date for REST clipboard mapping
Resolved in Pega Version 7.3
An error was generated while mapping UTC format Date fields to the clipboard in REST. This was traced to the DateTime properties in the JSON response not being converted to Pega-supported datetime format, and the necessary parsing logic has been added.
SR-B5450 · Issue 274669
Tab layout focus corrected for "show next error"
Resolved in Pega Version 7.3
The "Show Error" and "Show Next Error" functionality in the layout group of type tab were not giving focus to the correct element when clicking the 'show next error' if an autocomplete was present. Instead, focus was given to the element whose CSS property display was set to none. To correct this, an additional filter condition has been added to ensure the expected focus.
SR-B5560 · Issue 276633
Corrected page passivation for parameterized data pages
Resolved in Pega Version 7.3
A null-pointer exception error was generated when performing findPage() on a parameterized Data page after the page/thread was passivated and restored. This was traced to a situation where a page with meta data was not correctly saved while passivating due to a failed condition check on last update time, and has been resolved with changes to the EditDataPageHandler to update the access time whenever page is loaded from findDataPage() method.
SR-B5618 · Issue 281402
Autocomplete works in grid layout
Resolved in Pega Version 7.3
If a data transform was in the data class and the same was used as a source for the autocomplete inside a repeat grid, the data was not present in runtime. The configuration did work if the data was in the work class. This was traced to missing context, and has been fixed by ensuring the pre-datatransform and pre-activity have the grid row page context.
SR-B5672 · Issue 280747
Corrected and improved calculations for multiple page Business Calendars
Resolved in Pega Version 7.3
The Business Calendar time zone was not correctly populated when a second page was added to the calendar. This was due to the new page using the operator time zone instead of the business calendar time zone, and has been fixed. In addition, the difference calculations for calendar processing have been improved for greater accuracy.
SR-B5672 · Issue 283549
Corrected and improved calculations for multiple page Business Calendars
Resolved in Pega Version 7.3
The Business Calendar time zone was not correctly populated when a second page was added to the calendar. This was due to the new page using the operator time zone instead of the business calendar time zone, and has been fixed. In addition, the difference calculations for calendar processing have been improved for greater accuracy.
SR-B5678 · Issue 277570
Fixed out of bounds issue for deleting nested grid row
Resolved in Pega Version 7.3
An IndexOutOfBoundsException was generated when trying to delete a row in a nested grid. This was due to an incorrect base_ref being generated by the tools.getActive function for the second cell because the first cell also had a grid. To fix the issue, the cell generation has been changed to use tools.getStepPage instead.
SR-B5813 · Issue 276080
DuplicateProperty checked on enqueue
Resolved in Pega Version 7.3
The enqueue() method of PRQueueManager was not honoring the "pyDuplicateProperty" value of the existing queue items which have a higher pyMinimumDateTimeForProcessing. To correct this, QueueManagerImpl has been modified so the enqueue() method uses an overloaded version of next() method which is intended to ignore pyMinimumAgeForProcessing when checking for duplicates.
SR-B5820 · Issue 276037
Properties of type Integer text value properly formatted
Resolved in Pega Version 7.3
Properties of type Integer text value were not properly formatted when set to property. This has been fixed by modifying the assembler code to pass the property type and use it properly for runtime mapping.
SR-B5982 · Issue 279431
Tabbed form submission errors read by JAWS
Resolved in Pega Version 7.3
JAWS was not reading the error messages on the screen if the form submission was in a tabbed layout. To correct this, a setTimeout has been added to the reloadAcessibility function to call displayErrorTable.