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.
SR-C30037 · Issue 373310
Currency codes updated
Resolved in Pega Version 8.1
Currencycodes.xml has been updated to reflect the latest changes as per the following document:https://www.currency-iso.org/dam/isocy/downloads/dl_currency_iso_amendment_165.pdf
SR-C30049 · Issue 373668
JAWS properly reads icon column in expand pane
Resolved in Pega Version 8.1
When a grid is configured with Expandable rows master detail, with an icon for the "expand / collapse" icon per row, a column is reserved for the icon. However, when using JAWS table shortcuts, the column header reserved for the icon was read out as blank. This was due to the expand pane header not having the required aria attributes, and these have been added in the GenerateGridHTML function.
SR-C30268 · Issue 370456
Swapped directory find logic for command line prpcUtils
Resolved in Pega Version 8.1
When prpcUtils.sh was invoked using a 'sh' command, such as "sh prpcUtils.sh import",the script execution failed with the error "mkdir: cannot create directory ‘prpcUtils.sh’: Not a directory" and "Build failed, Ant Process returned a non 0 value". This was traced to the script using parameter expansion to find the directory where the script resides, but the expansions were not working as expected when the command was executed in a new shell (sh <command>). To correct this, the script will use the 'dirname' command to find the full path to the directory.
SR-C30344 · Issue 372318
Activity pzCreatePage correctly uses parameter dataTransform
Resolved in Pega Version 8.1
When trying to use the out-of-the-box activity pzCreatePage to create a new page using Run Activity action on click of a button, the page was getting created but the data transform (pyDefault) that was passed as a parameter was not getting applied. This is because the Page-New step in that activity does not use the parameter dataTransform: due to development error, an extra parameter was added that wasn't supported. This extraneous parameter has bene removed, and the page-new method in pzCreatePage is now using the dataTransform parameter.
SR-C30347 · Issue 371804
GridFilterRangeFields increased to allow date ranges of +/- 100 years
Resolved in Pega Version 8.1
Previously, the date filter of columns in tables/grids only allowed navigation for date ranges of +/- 10 years by default. In order to allow more flexibility, the range set in the pzGridFilterRangeFields Section has been increased to support values +/- 100 years.