SR-C56774 · Issue 409916
Removed double encoding on unicode local action parameter
Resolved in Pega Version 8.1.2
After enabling Unicode based rulenames using DSS, a Repeating table layout event action could not call a Unicode based local action even when an event action on a Dynamic Layout Section could call it. This issue occurred when the name of the flowaction had Unicode characters like Japanese; the open local action was not able to open the modal when launched from a grid because the Location parameter used by the grid was being double encoded. To correct this, the system will avoid the double encoding by passing the true parameter to actionURL.toQueryString for subsequent encoding by asyncrequest's toURL.
SR-C57879 · Issue 406005
Updated parameter handling for SECU0001 alert for accuracy
Resolved in Pega Version 8.1.2
In the SECU0001 alert, some fields contained incorrect values pertaining to a previous HTTP request, not the one that caused the alert, causing misleading information to be logged and sent to PDC. This was found to be an issue where when unexpected properties were found, the alert was being thrown from an early stage of processing, i.e., during inputProcessing where the current activity had not yet been set to the requestor state and therefore the currentactivity was not there in the stack frame. This has been addressed by getting the activity name from the HTTP request parameters and updating the diagnostic information with it so the alerts will be accurate.
SR-C59018 · Issue 407438
Resolved chart page lookup failure for Express Portal
Resolved in Pega Version 8.1.2
In the Express portal, exceptions were generated when clicking on a chart in the case volume report. This was caused by a lookup failure: when the activity doUIAction was called (after drill down), the pyReportContentPage was getting deleted. This has been corrected by setting the property pyRetainPage to true within the displayReport activity to keep the pyReportContentPage from being deleted in frameless portals.
SR-C60087 · Issue 406620
Failure status set correctly for WL to WL bulk WO transfer
Resolved in Pega Version 8.1.2
When a work object that was part of a bulk transfer was being moved from one operator's work list to that of another operator, a blank status was appearing if the work object was resolved by the originating operator before it was submitted. This was caused by a missed use case for setting error messages and has been corrected by updating pzBulkProcessItemsInHarness.
SR-C61154 · Issue 411074
Improved DB stability and retry for issues with RetryContext$ExceptionForDatabase
Resolved in Pega Version 8.1.2
The agent was crashing when there was a report using a pr_read_from_stream for the 'where' clause combined with a PostgreSQL version with 'on pr_read_from_stream'. This has been addressed by improving the stability of the database and adding code to better handle reconnect and retry when there is a database problem.
SR-C62241 · Issue 405942
Error handling corrected for Actions/Refresh menu actions
Resolved in Pega Version 8.1.2
When using the ACTIONS / REFRESH menu action on a case that had a required property, the busy indicator appeared and remained on screen, blocking interaction with the portal until the browser was refreshed. The error "pzpega_ui_harness_deferred_ts_1342430166!!.js:1969 Uncaught TypeError: Cannot read property 'stopPropagation' of undefined at Object.stopPropagation" appeared. This was traced to a fault in the error handling and has been corrected by modifying "pzpega_control_actions_refresh.js" so the event will be passed as parameter in the "pega.u.d.submitWhenFail()" call and the "SubmitInProgress" value will be set in context in pzpega_ui_doc_submit.js.
SR-C62434 · Issue 410619
Optimize Schema Index Creation updated to use Admin Datasource when available
Resolved in Pega Version 8.1.2
When configured according to the Pega Installation Guide, the SQL Server base user did not have the ALTER privilege enabled on the data schema. The Optimize Schema Index Creation was using the base user datasource "jdbc/PegaRULES" instead of the admin datasource "jdbc/AdminPegaRULES" even though an admin connection was available. This was an oversight during development, and has been fixed by modifying NoDBAUtils.java to use an admin connection if one is available. In addition, a clarification has been added to the UI to alert the user that an optimization job has been scheduled rather than completed.
SR-C62835 · Issue 408361
pzReindex defaults to true during branch merge and initial save
Resolved in Pega Version 8.1.2
When using Declare Indexes intended to be fired when a KYC rule type was saved, merging a KYC rule type from a branch to a ruleset which contained the rule resulted in the declare indexes not firing from Rule-pyMergeInstance. If the branch was merged into a ruleset which did not contain the KYC rule, the Rule-pyMergeInstance fired the declare index rules as expected. This was an issue with using Declare Indexes in an unexpected way: Declare Index works only when a property that is tracked is changed, and merging a branch rule to base ruleset does not change any tracked property. However, there was a Force Reindex happening when the saved instance had a different pzInskey than one that already existed in the db. This occurred when the rule was merged to new ruleset where the pzInskey in the DB would be null, and was expected behavior. In order to ensure Declare Indexes fire during a merge, pzReindex will be set to true in the Merge Wizard before saving the rule while doing branch merge. It will be reset/set to false after the rule has been merged and saved to avoid the additional overhead of triggering re-indexing every time the rule is saved afterwards. Further enhancements will be made in an upcoming release regarding parameter handling in templatized UIs.
SR-C64783 · Issue 407089
Corrected handling for SAML logoff
Resolved in Pega Version 8.1.2
On SAML logoff, the error "There has been an issue; please consult your system administrator; Status:fail ... No certificate found in truststore" appeared. Investigation showed this was an issue with the aliasing of certificates and signing that led to the requestor not being terminated for that logoff response. To correct this, when Pega receives a logout request which is invalid, it will terminate the session instead of throwing a PRRunTimeException.
SR-C65239 · Issue 411326
Check added to resolve nested grid component mismatch
Resolved in Pega Version 8.1.2
When using a nested repeating grid with expand pane option and expand multiple row options, running a screen flow resulted in a component mismatch error when moving from one assignment to another. This was traced to a limitation in the implementation that sometimes caused the parameter of the outer and inner grid to become corrupted or affect the wrong grid. In this case, the parameters startIndex and recordsInCurrentPage were resulting in a numberformatexception which in turn caused the component stack mismatch error. To fix the issue, an empty check has been added for startIndex and recordsInCurrentPage in the grid generation code.