SR-D72672 · Issue 536389
Security updated for CreateOperator
Resolved in Pega Version 8.5
In order to improve security, CreateOperator in Pega-ProCom will require authentication to run with pxCanManageUsers privilege.
SR-D69927 · Issue 537480
Cleanup added for staging directory
Resolved in Pega Version 8.5
Temporary files from imports and exports (from DevOps) were filling up the staging area disk space because there was no automatic process for cleaning up these local files. This has been resolved by adding an enhancement that will clear the directory on Engine Startup and any time ParUtils.setStagingDirectory gets called to initialize the staging directory.
SR-D76492 · Issue 549969
Added check for test case creation when Cross-site scripting security enabled
Resolved in Pega Version 8.5
Test case creation was failing. Investigation showed that when the "Cross-Site Request Forgery" security setting was enabled, the CSRF token and Browser fingerprint were not included in AJAX calls, and the Ruleinskey was not getting passed. This has been resolved by adding a check to evaluate whether security measures are included or not when making a server call from AJAX, and including the tokens required when appropriate.
SR-D79397 · Issue 546416
Rule-Utility-Function references updated with library information
Resolved in Pega Version 8.5
The "changeSystemName” operation failed. This was traced to the function “getLocalizedValue” (Rule-Utility-Function) being saved into the PegaFS library due to runtime resolution based on the function signature even though the actual Rule-Utility-Function from “Pega-Rules” ruleset needed to be picked in this case. To ensure the correct ruleset is picked, Rule-Utility-Function references have been updated with library information to resolve the resolution collision scenario.
SR-D52138 · Issue 537506
Property setting corrected for On Join and Exclusion shapes in Expression Builder
Resolved in Pega Version 8.5
The properties for the defined page did not appear when using the type-ahead feature to select properties for the On Data Join and Exclusion shapes in Expression Builder. This was an issue related to the property being referenced for setting the context in the expression builder, and has been corrected.
SR-D67316 · Issue 541205
Cross-site scripting protection for PegaRULESMove_Skimming_Query
Resolved in Pega Version 8.5
Cross-site scripting protection has been added for input parameter toRSV of the activity PegaRULESMove_Skimming_Query.
SR-A103203 · Issue 276928
SQL alias function getLastDayofYear repaired
Resolved in Pega Version 7.3
After upgrade, the SQL alias function getLastDayofYear generated an error. This was due to missing format conversion for the date value parameter, and has been corrected.
SR-A86522 · Issue 272062
Event Late triggers expanded
Resolved in Pega Version 7.3
If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.
SR-A86522 · Issue 272065
Event Late triggers expanded
Resolved in Pega Version 7.3
If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.
SR-A91979 · Issue 261380
referencePropertyLink will be directly copied if autopopulate disabled
Resolved in Pega Version 7.3
A run-time failure occurred due to a reference to an AP property failing to copy properly during objOpenByHandle. This was because autopopulation is disabled in objOpenByHandle, causing the source property to be returned as null when page-copy lost the reference information. To resolve this, when autopopulation is disabled the referencePropertyLink will be directly copied from the source page to the target page without trying to resolve the reference property's source.