SR-C49089 · Issue 388092
File input handling added to trigger file browsing popup
Resolved in Pega Version 8.1
When the 'Browse' icon received focus in the operator ID rule with tab navigation, pressing the 'Enter' key did not open the file browsing popup. This was due to the Enter event not working with file input, and a check has been added for file input in pzega_ui_events to allow it as an enter key event.
SR-C49089 · Issue 388866
File input handling added to trigger file browsing popup
Resolved in Pega Version 8.1
When the 'Browse' icon received focus in the operator ID rule with tab navigation, pressing the 'Enter' key did not open the file browsing popup. This was due to the Enter event not working with file input, and a check has been added for file input in pzega_ui_events to allow it as an enter key event.
SR-C49097 · Issue 389781
Added missing tooltips for JAWS to read "+" and other buttons in Operator ID and Access Group rules
Resolved in Pega Version 8.1
A few buttons like "+", "Open", etc., were being read by JAWS as unnamed buttons in operator ID and Access Group rules. This was due to missing Tooltips, and has been corrected.
SR-C49124 · Issue 391107
Resolved null stream error on mobile
Resolved in Pega Version 8.1
When clicking on certain events quickly one after another on mobile, the error "Failed to load stream: null" appeared. Analysis showed ActionQueue has timeout logic which unblocks the Queue after 2 seconds. Due to this, the next action in the queue was executed before the first one was done and ended up modifying the variable of the first action. To resolve this, the timeout has been removed and pega.process.engine.ActionQueue.complete(); will be called as required.
SR-C49133 · Issue 387543
Scheduletaskprocessor amended with exit activity to release locking
Resolved in Pega Version 8.1
Scheduled guardrail reports were not emailed, and exception appeared regularly referencing "Error locking scheduled task : PX-ST-1 close scheduling window to release lock." Investigation showed the activity pzscheduledtaskprocessor was lacking an "Exit Activity" condition, and this issue has been resolved by updating the activity step to check for proper activity exit.
SR-C49274 · Issue 388984
Expiry dates displayed in Authentication Service Rule SSO certificate
Resolved in Pega Version 8.1
Inconsistent behavior was seen in the Authentication Service rule SSO certificate expiry information between Pega versions. Previously, the system displayed Expiration Dates on the Authentication Service rule form after selecting the signing/decryption certificate, whereas after upgrade the expiry dates were not getting displayed. This was an error resulting from enhancements made to support different keystore types (Upload, File Reference, URL Reference, Data Page source) and introduce Keystore cache: during these modifications the "pzGetCertificateExpiry" activity was not modified to get the certificate from Keystore Cache instead from DB. This has been fixed.
SR-C49837 · Issue 388774
ListName now available as drop down option for Cassandra Connect method parameter
Resolved in Pega Version 8.1
An enhancement added to allow the Cassandra Connector GET operation to return multiple rows by querying on clustering keys and/or secondary index was missing the ability to use pyListName as a result page parameter. This has been corrected.
SR-C49906 · Issue 389638
Unreachable nodes kept on the services landing page for clarity
Resolved in Pega Version 8.1
Trying to start or create and start a Capture Activity DF was failing with a timeout error because the services landing page did not display a node if it was not available on pr_sys_nodes table (which can be the case after cleanup or truncation of that table). This created conflicts on stream service since it acts different on different numbers of nodes being available. To fix this, the system has been modified from relying on the sys_status_nodes table to get information about unreachable nodes to instead now assume it used to be a service node if it's on the list of nodes. and keep the unreachable status.
SR-C5015 · Issue 362314
Passivated queue cleared for dismissed window
Resolved in Pega Version 8.1
If there were open active tabs in the portal work space and the window was closed with the browser 'close' icon instead of logging off, the active threads related to that session were not properly terminated and would reappear if the browser window was reopened. The system has now been updated to ensure that the queue will be properly cleared in this scenario when using <env name="Initialization/PersistRequestor" value="Never"/>.
SR-C5022 · Issue 354557
Check added to Optimized Locking for assignmentkey
Resolved in Pega Version 8.1
When two users tried to acquire an assignment at same time in a system using Optimistic locking, an assignment processing error occurred. This was traced to the assignment key validation not being done while checking for ValidAssignment. When Optimistic locking is used, a prompt is shown to the current user working on the assignment if another user opened and worked on the same assignment simultaneously. A refresh button is shown to resolve conflicts and show the review harness. Existing logic takes care of completion of an assignment, but in this case the assignment is the same but has moved from workbasket to worklist. On click of Refresh, 'RefreshOnConflicts" is checking with the existing change logic and since assignment still exists it was trying to preformAssignment with the old assignmentkey(workbasket) which is not valid. To correct this, a new condition has been added to RefreshOnConflicts in the Pega-ProcessEngine ruleset to check if existing assignment is valid or not. If it's not a valid assignment, the system will open the review harness rather than processing the assignment.