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.
SR-C29110 · Issue 369501
Added visibility conditions to display of Import/Export screen for pzZipMoveExport
Resolved in Pega Version 8.1
Non-Developer/System administrator users were able to view the Application Import/Export screen despite insufficient privileges. This was a missed use case around the pzZipMoveExport privilege, and has been fixed by adding a visibility condition on sections so that export-related landing pages will be shown when there are required privileges.
SR-C29147 · Issue 369498
Context Not Defined error tuned for capture responses
Resolved in Pega Version 8.1
ContextNotDefinedErrors were thrown on capture response even when one of the models executed in the original decision matched all identifiers. For example, given Model1, with predictor Age Model2, with predictors Age and income Model3, with predictors Age, income and gender When a response is sent to ADM with Outcome and just Age, a Context Not Defined error was logged for Model2 and Model3. This behavior has now been updated to only log an error when a response doesn't provide values for the context keys of ALL model rules it relates to. The error message will also be updated to reflect this.
SR-C29307 · Issue 369458
Reference tracker tracks references to the page list properties in non-auto-generated sections
Resolved in Pega Version 8.1
In certain cases reference tracker would miss complex property references, especially when a primary page had nested embedded pages and page lists. This has been resolved by changing the underlying reference tracker implementation to be independent from the page structure. The new implementation is more robust and 100% compatible with DSM clipboard pages.
SR-C29360 · Issue 370557
Improved error messaging and logging added to listener startup/stop
Resolved in Pega Version 8.1
The message returned to the UI by com.pega.pegarules.management.internal.system.operations.ListenerCommandExecutorOnRemoteNode#executeCommand was previously of the format "Failed to execute" + commandName + " on node %s". In order to make this error message more meaningful, the command name will return the simple name of the path rather than the full path. In addition, more comprehensive logging has been added to listener remote execution operations in case of errors.
SR-C29360 · Issue 373809
Improved error messaging and logging added to listener startup/stop
Resolved in Pega Version 8.1
The message returned to the UI by com.pega.pegarules.management.internal.system.operations.ListenerCommandExecutorOnRemoteNode#executeCommand was previously of the format "Failed to execute" + commandName + " on node %s". In order to make this error message more meaningful, the command name will return the simple name of the path rather than the full path. In addition, more comprehensive logging has been added to listener remote execution operations in case of errors.