SR-C11323 · Issue 352191
Tab header value works for SSO
Resolved in Pega Version 8.1
The Tab header value was not updated with the rule name or Work Object ID when SSO authentication was used with sub-domain URLs. This has been fixed.
SR-C11351 · Issue 356669
RDL FlowAction Section correctly rendered readonly offline
Resolved in Pega Version 8.1
When given a Repeating Dynamic layout in a Section which had the Primary Section and Detail Flow Action configured and the section in Detail Flow Action was configured to display in read-only mode, the layout worked as expected on Desktop and Mobile online, but enabling any case for Offline caused it to not be rendered in read-only mode. This was an issue with how the offline readonly information was being stored, and has been corrected.
SR-C11373 · Issue 353185
Logging enhanced for names of activities
Resolved in Pega Version 8.1
The new logger 'LogActivityExecution' has been introduced to log the names of activities running on the system as Info loggers. To get these info forced log messages, enable 'INFO' on 'LogActivityExecution' logger. This can be done either changing in prlogging.xml or by changing logger settings in Designed studio landing page. The info message will look like: "Activity is being executed - Activity name: 'pyUpdateActiveUserCount', Class name: 'System-Status-Nodes'"
SR-C11499 · Issue 352774
Performance improvement for Mobile use of CaNull Pointer Exceptionrform
Resolved in Pega Version 8.1
Performance issues were seen in the Mobile application while processing work referencing the when rule CaNull Pointer Exceptionrform. This was due to the "CompareTwoValues" expression underperforming for the Boolean comparison case, and performance has been improved by replacing it with an "ExpressionEvaluatesToTrue" expression.
SR-C11712 · Issue 354391
Incremental Indexer Agent skips instances being indexed by updateIndex API
Resolved in Pega Version 8.1
If NRT Indexing and immediate search queries were processing while the FTSIncrementalIndexer was doing an update, they sometimes conflicted and the FTSIncrementalIndexer would temporarily alter the content in the index. This resulted in incorrect search results during the run, though in the end the content would be correct and match the database to give correct results. To address this confusing behavior, an enhancement has been added to prevent instances being indexed by updateIndex API from being overridden by Incremental Indexer Agent.
SR-C11890 · Issue 356754
RDL FlowAction Section correctly rendered readonly offline
Resolved in Pega Version 8.1
When given a Repeating Dynamic layout in a Section which had the Primary Section and Detail Flow Action configured and the section in Detail Flow Action was configured to display in read-only mode, the layout worked as expected on Desktop and Mobile online, but enabling any case for Offline caused it to not be rendered in read-only mode. This was an issue with how the offline readonly information was being stored, and has been corrected.
SR-C11933 · Issue 360570
Template corrected for read-only flow rule properties
Resolved in Pega Version 8.1
Double clicking a component in an open flow rule showed the properties as read-only, but selecting a component and pressing the properties icon allowed editing of the values and the changes were reflected on screen. This was traced to an incorrect template being used while launching the property panel flow action, and has been fixed.
SR-C11958 · Issue 354853
Reduced Mobile login time
Resolved in Pega Version 8.1
After upgrade, logging in on mobile was taking an excessive amount of time if the user had a lot of assignments. Code changes have been made to fix the redundant expression triggering and to optimize the way of getting expression DOM elements. This reduces the execution time for querySelectorAll.
SR-C12199 · Issue 360112
Pass pyFailMessage works to include additional error message on mobile
Resolved in Pega Version 8.1
Using a custom authentication activity to set an error message to be displayed on login screen by using:Param.pyFailMessage = "custom error message" Param.pyChallenge = @java("PRAuthentication.DEFAULT_FAIL_STREAM") worked fine on Desktop but on mobile resulted in the generic "The information you entered was not recognized." message that is hardcoded in pyWeb-login-mobile-authentication.js. This was a missed use case for handling scenarios where additional message error data should be sent in response, and has been resolved.
SR-C12279 · Issue 354259
rule-ruleset-version correctly cataloged to hotfix
Resolved in Pega Version 8.1
While importing DL for the PCS application, rule-ruleset-version was not getting cataloged to the hotfix manager. This was traced to the failure of the pre-installation initial scan. As recent system changes now support non-versioned rules by looking at the save time, the Rule-RuleSet-Name and Rule-RuleSet-Version will both be treated as valid for scanning and cataloging to avoid this error.