SR-C16229 · Issue 357687
Check added to SQL generation to exclude BOM
Resolved in Pega Version 8.1
When using the facility System Upgrade > "Upgrade Applications Schema" from Designer Studio to generate a SQL file (as opposed to running directly from Designer Studio), the downloaded SQL was found to contain the Byte Order Mark sequence (0xEF,0xBB,0xBF) at the start of the file. This byte sequence caused the DB2 command line client to fail. This has been corrected by adding a check that will set 'aIncludeBOM' flag to false for SQL file generation.
SR-C16281 · Issue 358133
Null check added for filterOutWithdrawnCandidates
Resolved in Pega Version 8.1
During RUF resolution, encountering a candidate that was outside of the current RSL generated an Null Pointer Exception. This has been corrected by adding a null check in filterOutWithdrawnCandidates. If the ruleset spec is null, the candidate will be removed from the list.
SR-C16365 · Issue 356219
Data Schema upgrade documentation clarified
Resolved in Pega Version 8.1
In order to eliminate confusion, portions of the Update and Upgrade guides relating to data schema upgrades have been clarified to differentiate "upgrade schema" and "temporary upgrade schema".
SR-C16479 · Issue 356880
Ruleset version check added to pzPackageParagraph activity
Resolved in Pega Version 8.1
The pzPackageParagraph activity was fetching Paragraph versions from different rulesets instead of only the highest rulesets. This caused performance issues on installations with large numbers of paragraph rules. To correct this, an 'if' check has been added to filter the Paragraph rules which belong to rulesets of lower hierarchy in rule resolution.
SR-C16490 · Issue 356910
Tuned layout visibility conditions
Resolved in Pega Version 8.1
In order to ensure the visibility conditions on layout are honored as expected, code has been added to avoid evaluating expressions from dom elements during the initial rendering of the screen.
SR-C16548 · Issue 360113
Fixed UDF calls schema prefix
Resolved in Pega Version 8.1
UDF calls were being prefixed with the schema name of the class rather than schema name in which the AllOf/OneOf functions are stored. To correct this, the UDF will instead be prefixed using the schema name of the PegaDATA database where the functions/UDFS are installed.
SR-C16693 · Issue 359290
Column name shows in filter section RD of drilldown report
Resolved in Pega Version 8.1
The Column name in the drilldown filter was displayed as a function in the 'column source' (of the main report definition) in the drilldown report, but the name was not provided in the 'column name' column in the query tab of the main report definition. This has been corrected.
SR-C16751 · Issue 360165
Code fixed for harness pyCMReports
Resolved in Pega Version 8.1
An error in the code was causing the report browser (harness pyCMReports) to fail if it was generated by the pxgetRRContentForRB activity. This has been corrected.
SR-C16853 · Issue 357442
Introduced property made visible in reports
Resolved in Pega Version 8.1
The date 'Introduced' property was hidden in reports; this has been made visible.
SR-C16897 · Issue 359392
Property validations messages check box added for read-only
Resolved in Pega Version 8.1
Property validation messages were not displayed on the pxDisplayText(Formatted Text) control when using read-only. To allow this, a 'Show validation messages in read-only mode' check box has been added to the formatted text presentation tab.