SR-C8725 · Issue 351894
Check added to ensure pyRuleSetName is not empty
Resolved in Pega Version 8.1
An extra condition has been added to the existing db-query which checks if a ruleset is locked to now also ensure pyRuleSetName is not empty. This will prevent a blank ruleset value from being passed in.
SR-C8735 · Issue 356715
Updated log error for hotfix commitment fail
Resolved in Pega Version 8.1
If no catalog file is found after committing hotfixes, the System Scan fails with no error message to the user even though the display of Committed/Uncommitted hotfixes is not updated properly. The message "Could not run System Scan - there is no Catalog on the system" appeared in the logs after the list of commits, but it was not clear what this indicated. The wording of the logged error has now been updated to clarify that the Committed/Uncommitted list of hotfixes has not been updated.
SR-C8776 · Issue 369407
Added explicit cleanup of non-serializable objects in the Connect-SOAP ParameterPage
Resolved in Pega Version 8.1
In investigating an application continuously logging error messages for Serialization, it was found that Connect-SOAP execution leaves non-serializable objects in the ParameterPage, which in-turn caused this the error logging upon requestor passivation. To resolve this, code has been added to remove the pyServiceClient, soapHdr, and activityParamPage parameters from the ParameterPage after use.
SR-C9001 · Issue 353898
Column alias checks added for import
Resolved in Pega Version 8.1
As a followup to a corrected issue for an export not including a column alias list, an import missing a column list alias has been fixed as well. The code will check for the presence of aliases, do a pattern match to check if aliases exist for view, and if they are found then aliases will be added for view generation during the import process.
SR-C9139 · Issue 352594
XSS filtering added to searched filter values
Resolved in Pega Version 8.1
ListViewHeader has been updated to apply XSS filtering to searched filter values.
SR-C9145 · Issue 355278
DNode dataflow generation exception changed from warning to FAIL
Resolved in Pega Version 8.1
The DataFlow-Execute generated code has been updated to create a PRRuntimeException in case of error so the activity step will change its status to FAIL instead of warning.
SR-C9313 · Issue 355576
Data-schema-only upgrade fixed to include operator upgrade
Resolved in Pega Version 8.1
After encountering issues accessing an application, Update Existing Applications had to be run from the wizard after upgrade even though it should have run by default when doing this type of upgrade. This was traced to an implementation error in the data-schema-only upgrade activity which accidentally omitted the operator upgrade step, and has been fixed.
SR-C9426 · Issue 350602
BIX extract rules preserved during bulk check-in
Resolved in Pega Version 8.1
BIX Extract rule filters were being stripped off on bulk check-in. This was due to the pyRDPage which was used for holding the filter conditions in the extract rule not being present in the thread performing bulk check in, and the issue has been corrected.
SR-C9536 · Issue 354488
Check added to ensure fresh app data for delta sync
Resolved in Pega Version 8.1
When the application data was updated on the web (server side), the changes were not reflected on the phone app (client side). When an application login and delta sync were performed on the mobile device, the changes made on the server side still did not show up. The changes made to the web application did show up if the mobile cache was cleared and a new login was started. This issue was traced to an implementation error where an editable data page once loaded on clipboard was always packaged as-is even when things had changed in the DB. To correct this, a check has been added to remove the stale datapage and fetch a fresh version when doing datapage packaging in pzDataSyncPackager.
SR-C973 · Issue 349954
Move report shortcut shows consistent categories
Resolved in Pega Version 8.1
When opening a Report in the Case Manager Portal, the Analyze Performance category is first in the out of the box implementation. However, when attempting to move one report from a different category, the Analyze Performance category was not shown in drop-down This was caused by different field values being used to display the category label in the browser and category dropdown, which led to them being localized differently in the display on the right ( "Analyze Performance") and the dropdown ("Performance analysis"). To correct this, the field values have been updated to make them consistently localized.