SR-C15942 · Issue 358749
REST Connector Wizard Datamodel logic update
Resolved in Pega Version 8.1
The REST Connector wizard was failing to generate all the properties due to a problem with the DataModel generation. This has been corrected by adding two different Boolean properties in the property info map to separately tag request and response processing.
SR-C16004 · Issue 357445
Corrected additional instance being added when clicking on Dynamic Layout row with helper classes
Resolved in Pega Version 8.1
When adding helper classes (custom CSS) on a Dynamic layout or any others that use this feature, two instances were added when clicking on the row and not on the "+" icon. This happened when the layout had some action attached to it and that layout had children whose width was small (and there is no action attached to it) so that there was a lot of space remaining in the layout. In this case, actions were being appended to the queue twice, one from processBehaviorsOnElem call from processBehavior and another processBehaviorsOnElem call from processOtherBehaviors. To correct this, pzpega_ui_events .js has been modified to only call processOtherBehaviors when dynamic layout is used.
SR-C16062 · Issue 372412
ProcessAction will update pageName based on pyWorkPage
Resolved in Pega Version 8.1
A link which was configured to open a local action in overlay and then render a button which again referred to a menu in overlay was only working intermittently. On click, of some of the actions in menu worked while some resulted in a activity status error. This was traced to the method used to update the pageName in the "ProcessAction" activity, and modifications have been made to update pageName only if the primary page is "pyWorkPage".
SR-C16122 · Issue 358344
Removed irrelevant Primary page properties
Resolved in Pega Version 8.1
Irrelevant properties were appearing on the primary page while using Address Map control. This was traced to an improper function call and has been corrected.
SR-C16126 · Issue 388052
XMLCipher.java implementation adjusted for updated JDK8
Resolved in Pega Version 8.1
Errors were seen when using the decryption feature of SOAP services To resolve this, the Pega implementation of XMLCipher.java has been adjusted to correlate to recent updates made to JDK8.
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.