SR-D8754 · Issue 497378
Tracer issues resolved for Google Chrome browser
Resolved in Pega Version 8.1.6
Tracer was running in the background even after the tracer window was closed. Attempting to run a Tracer in this condition resulted in an error indicating the Tracer was being run by another operator and should be restarted, and in the Dev environment, attempting to start a Tracer once it was closed resulted in the message "Cannot launch multiple Tracer sessions for a requestor." Investigation found that the Tracer session was not being closed when the tracer window was closed because the browser specific method intended to do so was not being called. This was found to be an issue caused by the Google Chrome browser changing the signature of the method, and has been resolved by updating the method name in the TraceMain HTML rule.
SR-D7138 · Issue 494666
Updated taxonomy rule to correct obj-open
Resolved in Pega Version 8.1.6
After using Taxonomy -> Create model -> Apply to Text Analyzer and then using the Training data to add additional messages to the model, an error that Mandatory parameters were missed appeared. This error was traced to a condition where changing the taxonomy rule caused the system to execute an incorrect obj-open. This has been corrected.
SR-D28184 · Issue 497167
Verbose debug logging removed from LockUtils
Resolved in Pega Version 8.1.6
Verbose debug logging that had been added to the "LockUtils" class to print when the lock was acquired or released and include the associated stacktrace has now been removed as it interfered with diagnosing locking issues when threads were getting blocked.
SR-D3034 · Issue 439708
Corrected reference to Hierarchical table in tree grid modal section
Resolved in Pega Version 8.1.6
Given a table on which row editing opened a modal dialog containing a section with a Hierarchial table, after the modal dialog window was opened and closed without changes, attempting to open it again produced a blank screen. The error "The reference PackagesPage.Packages(2)(1) is not valid. Reason: unexpected character '(' at position 24, expected dot" was logged. This was an edge case where a grid was opened in a modal dialogue from a tree grid. In this case, the parameters passed from the parent grid corrupted the logic to calculate the Automation ID and caused the reference page to be constructed incorrectly. To resolve this, a try catch block has been added to read the reference from 'tools.getActiveName()'.
SR-D16540 · Issue 489183
Removed duplicate error message seen when opening a case owned by another
Resolved in Pega Version 8.1.6
Duplicate error messages appeared when opening a case assigned to another operator. This was traced to there being two different sections that each would call the error message, pyNoIDMain or pyNoIDHeader, and this has been corrected by removing the error section from pyNoIDMain.
SR-D15970 · Issue 485233
Handling added for runtime exception on upgrade due to inaccessible external schema mapping
Resolved in Pega Version 8.1.6
If a system used external schema mapping, attempts to upgrade were failing with the error "Caused by: com.pega.pegarules.pub.database.ConfigurationException: Unable to obtain data source "java:comp/env/jdbc/PegaRULES", as it is undefined". This was traced to configuring external DADNs which were not accessible from the server where the upgrade was being run: an upgrade will fail if it cannot connect to an external datasource even if no changes need to be made to that datasource. However, because a PRRuntimeException was unexpectedly being thrown instead of a Database Exception, the exception was not properly caught and handled. This has been corrected.
SR-D14161 · Issue 490596
Cross-site scripting protection added to decryptURLString
Resolved in Pega Version 8.1.6
In order to secure against Cross-Site Scripting attacks, decryptURLString will return a blank string instead of plain text if it is not given valid encrypted text.
SR-D10545 · Issue 483628
Minimum width set for stage names to ensure all are properly displayed
Resolved in Pega Version 8.1.6
The chevron displaying stage names was not showing the complete stage name in Microsoft Internet Explorer and Google Chrome when there were more stages due to each stage not having its own width set. This has been resolved by adding a minimum width for the stages.
SR-C93292 · Issue 432663
Inline error messages linked to input for accessibility
Resolved in Pega Version 8.1.6
In order to support accessibility for server side inline messages, the controls have been mapped to the error message div and an aria-describedby attribute has been added for the same. This allows JAWS to read the error message specific to the control where the error occurs.
SR-D25306 · Issue 499529
Corrected multiplying errors on dirty flag
Resolved in Pega Version 8.1.6
The error message "Value cannot be blank" was appended on the screen every time the browser gave a dirty flag and OK was clicked. This was due to the context for the error message not being set correctly after toggleErrorMessage, and has been corrected.