SR-126576 · Issue 189461
RTE font change behavior smoothed
Resolved in Pega Version 7.1.8
If text present in the RTE was selected and the font family changed, the selected text was getting unselected and cursor was moving out. This has been fixed by modifying cmd_fontName and _selectNode to retain the selection of content in the RTE after changing the font name.
SR-126587 · Issue 191010
Workbasket name updated in Case Manager portal
Resolved in Pega Version 7.1.8
When CaseManager portal was launched and any particular WorkBasket selected, the text "WORK IN XXXXX WORKBASKET" was shown. XXXXX was the WorkBasket name, which was being picked from RuleName(Identifier) instead of ShortDescription. This was unexpected, and has been changed.
SR-126621 · Issue 193287
Localization added for on-click harness tab
Resolved in Pega Version 7.1.8
Localization was not working for the label of a tab containing a harness which was opened by a button. This was was due to the field value not being used for the tab name when it is configured as an on click action for a button, and localization has been added for tabName when the navigation rule is configured as showharness.
SR-126649 · Issue 193881
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-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.