Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

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.

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".

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us