SR-C28579 · Issue 384591
Delegated data types show correct tab header name
Resolved in Pega Version 8.1
When the delegated rules were opened from the case manager portal via configuration page in a multi DC portal, the tab name was shown as insname of the data type class. This was caused by the "pyInsHandle" property being configured for the name parameter for the landing page action. To correct this, the system will use "pyOriginatingLabel" instead of "pyInsHandle" in the pzDelegatedRulesGrid section to display the rule label.
SR-C28586 · Issue 377237
Error with fetching prompt value fixed
Resolved in Pega Version 8.1
When property was configured with declare expression and its read only value was given as 'Display text of selected options', it showed the standard value instead of the prompt value. This has been corrected with code changes to get the prompt value of the given configuration.
SR-C28586 · Issue 373798
Error with fetching prompt value fixed
Resolved in Pega Version 8.1
When property was configured with declare expression and its read only value was given as 'Display text of selected options', it showed the standard value instead of the prompt value. This has been corrected with code changes to get the prompt value of the given configuration.
SR-C28597 · Issue 369290
Logoff fixed for No SLO URL Authservice
Resolved in Pega Version 8.1
Recent changes made to Code-Security.Logoff to handle NO SLO URL defined in AuthService resulted in logoff not occurring properly. This has been fixed.
SR-C28672 · Issue 371101
Timing issue fixed with switchLocale refresh
Resolved in Pega Version 8.1
When using a function call to have a section refreshed so that it shows in Spanish, the section instead loaded in English and did not change. This was traced to a timing issue: the pega.clientTools.switchLocale method is asynchronous, and immediately refreshing Sections and Harnesses after the asynchronous call may not have time to reflect the changes. To resolve this, a callback mechanism has been introduced in the pega.clientTools.switchLocale method.
SR-C28691 · Issue 371875
Waterfall segment issues fixed
Resolved in Pega Version 8.1
After upgrade, issues were seen with waterfall segments with more than 10 groups in a set: 1) While deleting a criteria in a group, the control went to the top and did not come back. This has been fixed by adding code to get the name attribute using getAttribute().2) While moving groups up and down, the control went to the top and it was necessary to scroll down to find the rule. This was due to Menu options containing the refresh parent section request which was losing the focus. Code has been added to set the focus on the control from the point where the menu is getting launched.
SR-C28691 · Issue 371980
Waterfall segment issues fixed
Resolved in Pega Version 8.1
After upgrade, issues were seen with waterfall segments with more than 10 groups in a set: 1) While deleting a criteria in a group, the control went to the top and did not come back. This has been fixed by adding code to get the name attribute using getAttribute().2) While moving groups up and down, the control went to the top and it was necessary to scroll down to find the rule. This was due to Menu options containing the refresh parent section request which was losing the focus. Code has been added to set the focus on the control from the point where the menu is getting launched.
SR-C28801 · Issue 374737
Decimal validations fixed for offline mobile case
Resolved in Pega Version 8.1
On a mobile device using offline case it was possible to use multiple entries of grouping_separator without generating an error, but the Presentation configuration of Text Input control did not allow more than one separator in Google Chrome and Microsoft Internet Explorer . Example:"11,22" - worked "11,22.11" - generated error "11.22.22" - generated error "11,22,22" - generated error As a result it was possible to enter values as "12,3,3,3,3,3,3,3." or "12.3.3.3.3.3,4" and submit without any error and the Client Cache would be populated with the expected value "11111.76,null,null,null,null,null,777" , but after sync the clipboard contained "11111.76,null,,null,,null,777" This was due to the present client side validations not supporting validations based on locales, and a new regex expression has been added to pzpega_validators to fix invalid decimal number patterns like 45,,,,5434 , 45....5423 , 43.3,2354 , 54,.42324, etc.
SR-C28801 · Issue 375348
Decimal validations fixed for offline mobile case
Resolved in Pega Version 8.1
On a mobile device using offline case it was possible to use multiple entries of grouping_separator without generating an error, but the Presentation configuration of Text Input control did not allow more than one separator in Google Chrome and Microsoft Internet Explorer . Example:"11,22" - worked "11,22.11" - generated error "11.22.22" - generated error "11,22,22" - generated error As a result it was possible to enter values as "12,3,3,3,3,3,3,3." or "12.3.3.3.3.3,4" and submit without any error and the Client Cache would be populated with the expected value "11111.76,null,null,null,null,null,777" , but after sync the clipboard contained "11111.76,null,,null,,null,777" This was due to the present client side validations not supporting validations based on locales, and a new regex expression has been added to pzpega_validators to fix invalid decimal number patterns like 45,,,,5434 , 45....5423 , 43.3,2354 , 54,.42324, etc.
SR-C28980 · Issue 370302
Performance improved for screen rendering and checkbox action in Microsoft Internet Explorer
Resolved in Pega Version 8.1
After upgrade, Screen rendering and checkbox action was slow in the Microsoft Internet Explorer Browser. To improve performance, the following updates have been made: 1) Conditionally skipping multiple flex resizes on harness resize event. 2) Replaced $ calls in getCorrectPropertyElemFromDOM() with native querySelector. 3) Grid's getScrollParent() (~200ms) was erroneously comparing element’s scrollWidth with scrollWidth (instead of clientWidth) each time. 4) ui_inspector.js was making multiple attempts to get the closest element. The results are now cached. 5) In client expr evaluation, getAllRefreshableTargets() queries for the entry were handled three times. The query is fired only once now and the results are cached.