SR-126649 · Issue 192252
Documentation updated for column layout controls focus
Resolved in Pega Version 7.1.8
The documentation for column layouts has been updated to clarify that controls in a column layout main region receive focus before controls in the sidebar region receive focus. This is important for understanding the tab order on the page for accessibility users.
SR-126654 · Issue 192199
Context retained for nested grids
Resolved in Pega Version 7.1.8
The base reference was computed incorrectly when RDL is dropped inside a repeating structure, causing local action to be executed in the wrong context. To resolve this, the system has been updated to return null if a RDL row is encountered in getRepeatObject, so that base_ref is calculated from the node where action is invoked.
SR-126679 · Issue 197204
Tree grid alignment resolved for Google Chrome and Firefox
Resolved in Pega Version 7.1.8
When using the Google Chrome and Firefox browsers, tree grid rows were not properly aligned. This was due to legacy code in GenerateGridHTML which was running in quirks and used a different document model in different browsers. The model was no longer necessary due to a change in the generation method, and has been removed.
SR-126679 · Issue 197617
Tree grid alignment resolved for Google Chrome and Firefox
Resolved in Pega Version 7.1.8
When using the Google Chrome and Firefox browsers, tree grid rows were not properly aligned. This was due to legacy code in GenerateGridHTML which was running in quirks and used a different document model in different browsers. The model was no longer necessary due to a change in the generation method, and has been removed.
SR-126719 · Issue 189646
Added fallback keyinfo handling
Resolved in Pega Version 7.1.8
When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the trust store where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.
SR-126719 · Issue 177348
Added fallback keyinfo handling
Resolved in Pega Version 7.1.8
When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the truststore where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.
SR-126719 · Issue 178793
Added fallback keyinfo handling
Resolved in Pega Version 7.1.8
When a SAML assertion response is received in the authentication activity, an error indicated the KeyInfo was missing in the signature. This was caused by a lack of redundancy in the keyinfo handling that caused an exception when keyinfo was not included in the SAML response. Support has now been added to check the certificate in the truststore where the certificate from IDP metadata would have been imported, and there is an added null check in the debug logs.
SR-126730 · Issue 193522
Enabled accessibility for validation errors in modal windows
Resolved in Pega Version 7.1.8
Validation error messages were not being read by the JAWS accessibility function automatically in modal windows. This was due to missing ARIA attributes, and these have been added to the error spans.
SR-126732 · Issue 192781
Corrected button label for JAWS
Resolved in Pega Version 7.1.8
With JAWS accessibility active, when you navigate to a menu button labeled "Other Actions", JAWS says "Menu. To move through items press up or down arrow...O" instead of reading out the title of the button. This was caused by the button being used to show the menu, which added role="menu" to it, and this has been corrected in the button generation RUF.
SR-126746 · Issue 189633
Added schema qualification to BIX / DB2 extract rules
Resolved in Pega Version 7.1.8
When using a Business Intelligence Exchange (BIX) extract rule which included writing the manifest details to external database tables, running the extract rule generated errors for the insert into the pr_extract_summary and pr_extract_details tables. This issue existed both when running from the command line and from the User Interface (UI). This was traced to the extract code not schema qualifying the pr_extract_summary and pr_extract_details tables in the insert statements, so it is expecting those tables to be in the schema of the user who is defined in the Database rule. This has been corrected through code changes for DB2 external databases that includes currentSchema=YourSchemaName in the URL connection to the external database.