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.
SR-C29541 · Issue 374052
Password API repaired for refactoring locked rulesets
Resolved in Pega Version 8.1
Due to recent changes in the ruleset password comparison API, entering the correct password failed after attempting to refactor some string in the application when one or more of the rulesets was locked. The logic for the password comparison has been corrected to resolve this.
SR-C29642 · Issue 373082
Fixed harness rendering errors while using localization
Resolved in Pega Version 8.1
When using a language pack, trying to save a work object generated an error due to an incomplete translation involving hidden values in a perform harness. This has been fixed by replacing the hidden fields in pyCaseHeaderButtons section with a pyHarnessHiddenValues section include.
SR-C29742 · Issue 386203
Added check for JSON array when setting context for data transform
Resolved in Pega Version 8.1
When incoming JSON for a data transform had a null property, the data transform failed with a Null Pointer Error. This was due to the system assuming the root context to be null, which works for JSON but not for an Array of JSONs. To correct this, a check for topLevelArray has been added to ensure the system has the correct context of the current JSON Object.
SR-C29885 · Issue 370756
pxMatchScore handling modified to run with UDFs disabled
Resolved in Pega Version 8.1
An activity was created to check for duplicates using "SeekCases" as part of process for the identifying them. This activity internally evaluates the case match rule to calculate the match score and runs a report definition that populates the duplicates. However, if UDFs were disabled in the environment, pxMatchScore was used internally and threw an error during the case match rule execution because pxMatchScore property was reading from the blob column. The resolve this, the setting of the pxMatchScore filter condition for the virtual RD in the pyDuplicateSearchCases has been removed from the activity and pxMatchScore will be set in the FUA instead.
SR-C29964 · Issue 369856
Null check added for cpFilter
Resolved in Pega Version 8.1
a Null Pointer Exception error involving pxRetrieveReportData activity has been corrected by adding a null check for cpFilter.