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.
SR-C12338 · Issue 353057
Corrected code to prevent infinite loop in PegaGadgets
Resolved in Pega Version 8.1
The out-of-the-box Activity : "@baseclass.pzPopulateRecentGadgetList|Pega-Gadgets:07-10-23" contains logic in its Java Step (3) that under certain unusual circumstances caused an infinite loop to occur, locking up the Thread indefinitely. This has been fixed.
SR-C12339 · Issue 386340
ZipFileListOnServer activity modified to only create instances for zip files
Resolved in Pega Version 8.1
When the Hotfix Manager was run on the ServiceExport directory, the Next and Cancel buttons did not render. Analysis showed the system was creating the PRFile instance for all of the files from the directory, and an exception was being thrown when am instance was created for a file that had illegal characters in its name. To correct this, the pzZipFileListOnServer activity has been modified to only create the instances for files which start with "dl-" and end with ".zip".
SR-C12455 · Issue 356026
BIX date property extract to Teradata database fixed
Resolved in Pega Version 8.1
BIX extract was failing when extracting date property to a target Teradata database. To resolve this, DatabaseUtilsCommonImpl.java has bene updated to insert the null value as a varchar instead of Timestamp type.
SR-C12689 · Issue 356526
Improved logic for CorrNew activity email IDs
Resolved in Pega Version 8.1
When there were only two work parties and their email IDs were same, for example using a Bcc address, the formation of email ID string to CorrNew activity included an extraneous quote mark that caused the email to fail. The formation logic has been reworked to resolve this problem.
SR-C12730 · Issue 355808
Data page change detection refactored for improved performance
Resolved in Pega Version 8.1
In order to improve performance, the engine API used to detect changes in a data page has been modified from using a hash comparison via the getJSON sort to using a new lightweight clipboardpagechangeindicator.