SR-116613 · Issue 170409
JAWS no longer reads out table structures
Resolved in Pega Version 7.1.7
When JAWS encountered tables, it considered them to be data tables if there were no aria labels or roles defined on it and proceeded to read out the table structure to the user. If one of the td had ' ' it read out as blank. Table tags being generated for layouts are now given a "role" attribute as "presentation" for accessibility compliance: this will mark the table structure not to be read out by JAWS. In addition, JAWS will read out any html associated to the input rather than the aria-label format information.
SR-117230 · Issue 172209
JAWS no longer reads out table structures
Resolved in Pega Version 7.1.7
When JAWS encountered tables, it considered them to be data tables if there were no aria labels or roles defined on it and proceeded to read out the table structure to the user. If one of the td had ' ' it read out as blank. Table tags being generated for layouts are now given a "role" attribute as "presentation" for accessibility compliance: this will mark the table structure not to be read out by JAWS. In addition, JAWS will read out any html associated to the input rather than the aria-label format information.
SR-119223 · Issue 177088
DefaultValue API updated to retain values after deleting rows
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When deleteing rows from a repeating grid configured with readonly dynamic select control, the remaining rows were not properly holding their values. For example, if the row number to be deleted was "x", the "x+1" row occupies the Xth row place, but x+1th row's drop down value becomes lost and resets to "-Select-" value (Default Value). This was caused by the setOptionAndCaption API setting default caption instead of default value for the option tag. To rememdy this, the DS_setDefaultValue API has been updated.
SR-117855 · Issue 171394
Resolved NPEs during case creation
Resolved in Pega Version 7.1.7
If a null pointer error was generated during the case creation process, all subsequent records being processed also generated the error. This issue occurred when adding and later removing work party data, and was found to be related to a stack trace not being generated for the reported issue and an attempt to index a change to a page that's no longer available. To correct this, a code change now handles the condition which caused the NPE (writes an index for a non-existent page and then skips it) then logs information for analysis.
INC-150367 · Issue 606028
Double quotes escaped in entity mapping
Resolved in Pega Version 8.5.2
A usecase where the BOTS created the triage cases from the emails and pushed it to the Workgroup had an intermittent problem where the screen would freeze and no actions could be performed. perform any action on the same. Investigation showed this occurred when the entity text contained double quotes which is caused JSON to break on the client side. This generated an exception during rendering, and other onload scripts failed on load and blocked the entire thread. To resolve this, the system will now avoid the JSON break by escaping double quotes in entity mapping.
INC-146595 · Issue 604789
Initialized entryName for light weight inventory instance
Resolved in Pega Version 8.5.2
When running deployment on a new pipeline created for the next minor version, once the deployment process got to the point of showing aged updates, the “view aged updates” came back as blank screen. Viewing the logs showed the aged update elements come back but were missing the pyName associated with them. Investigation showed that the system did not have support for setting the mEntryName for LightweightInventoryInstance objects. This has been resolved by adding a junit to ensure that getEntryName() doesn't return as null and should be equal to pzInsKey.
INC-150367 · Issue 606030
Double quotes escaped in entity mapping
Resolved in Pega Version 8.4.4
A usecase where the BOTS created the triage cases from the emails and pushed it to the Workgroup had an intermittent problem where the screen would freeze and no actions could be performed. perform any action on the same. Investigation showed this occurred when the entity text contained double quotes which is caused JSON to break on the client side. This generated an exception during rendering, and other onload scripts failed on load and blocked the entire thread. To resolve this, the system will now avoid the JSON break by escaping double quotes in entity mapping.
INC-146595 · Issue 604791
Initialized entryName for light weight inventory instance
Resolved in Pega Version 8.4.4
When running deployment on a new pipeline created for the next minor version, once the deployment process got to the point of showing aged updates, the “view aged updates” came back as blank screen. Viewing the logs showed the aged update elements come back but were missing the pyName associated with them. Investigation showed that the system did not have support for setting the mEntryName for LightweightInventoryInstance objects. This has been resolved by adding a junit to ensure that getEntryName() doesn't return as null and should be equal to pzInsKey.
INC-136188 · Issue 604864
Icon focus indication made more consistent
Resolved in Pega Version 8.4.4
The focus on some main icons across the header in Designer Studio was inconsistent when tabbing through the header. Some icons showed a dotted border, for others the icon opacity changed on focus, and others had no focus style at all. An update has been made to ensure consistent dotted outlines on all header and footer icons on focus. The dotted outlines have also been added for all tabs on the application landing page for Dev Studio for icons such as the delete/ gear on all Repeating Dynamic Layout rows.
INC-174243 · Issue 655887
Links to specifications persist appropriately
Resolved in Pega Version 8.6.1
When linking Rules to Specifications, check-ins of some unrelated rules deleted the link. Investigation showed the deletion happened in the pzHandleLinksPostCheckIn activity, and was caused by an empty parameter page name that caused pcInsKey to not have a value, so all links returned by "Obj-Browse" were later deleted. To resolve this, an update has been made to insure the "Pass current parameter page" option in step 2 of the Connect REST PostCheckIn activity is enabled so that the downstream activity pzHandleLinksPostCheckIn behaves as expected.