SR-D5196 · Issue 444423
Hardcoded prweb reference removed from the REST connector to enhance flexibility
Resolved in Pega Version 8.1.6
The DASS for pegarobotics/RobotManagerHostDomain allows specifying the instance where Robot Manager is hosted. Previously, connect-REST pzInvokeRoboticAutomation contained a reference to the resource path {RobotManagerHostDomain}/prweb/PRRestService/robotics/v1/automations which forced the use of prweb. In order to add flexibility, the hardcoded prweb reference has been removed from the REST connector resource path, and the pegarobotics/RobotManagerHostDomain) DASS's default value has been updated to include 'prweb' in it. Local sites should update DASS accordingly to point to an updated URL with prweb if needed.
SR-D28985 · Issue 498016
Improvements made to Excel data import handling for decision tables
Resolved in Pega Version 8.1.6
On importing an Excel file into a decision table, the values modified in Excel were getting updated even though the rule was checked in after the import. Investigation showed that the API which handled converting the imported Excel file for use on the clipboard was defaulting to save actions if the rule was not checked out or in private edit before the import. In order to prevent future issues, the following changes have been made in this area: The "Import" button will be enabled only after clicking on checkout button, and discarding the checkout will also discard any imported values. When checkout for the rule set is disabled, only the save option will be displayed on the decision table. When the import button is visible and enabled, imported values will not be preserved if Actions -> Refresh is used before saving. When rulesets are disabled, the decision table can only be private edited and at that time the save and import buttons will be visible. When private edit is visible, the import button will be in a disabled state.
SR-D16433 · Issue 499296
Exception handling added for upgraded custom decision tables
Resolved in Pega Version 8.1.6
After upgrade, the status fail message "There has been an issue; please consult your system administrator" appeared with a blue screen in the Run window when attempting to run a Decision table from Actions-> Run option. This impacted the ability to create unit test cases. Analysis showed the issue occurred for any decision table where "Evaluate All rows" was enabled and list properties were used in Actions if there was no value for the list property after the execution of decision table. This was traced to a NullPointerException in a RunRuleFromPage activity in a customized in PUnit ruleset, and was caused by having list properties in the actions of a decision table that had not been populated during rule execution. Exception handling has been added to resolve this.
SR-D20950 · Issue 489656
Removed unnecessary commit from case creation with exception
Resolved in Pega Version 8.1.6
If a case had an exception when it was being created using the case creation API, it was sent to the problem flow functionality which performed a commit (All defer items) in the same interaction after it it performed a commit with error handling. This resulted in an Exception 3273 message. To resolve this, the unnecessary commit has been removed.
SR-D11909 · Issue 488672
Secure and httponly attributes added to Pega-Perf cookie
Resolved in Pega Version 8.1.6
A vulnerability test identified the Pega-Perf cookie as not having any attributes for secure and httponly. This has been resolved.
SR-D8650 · Issue 475299
Handling added for null sort order in file import metadata
Resolved in Pega Version 8.1.6
A NullPointerException was seen while fetching the sort order of indexes during a file import. This was caused by a null being returned for an index that did not have the sort order in the metadata, and has been resolved by adding a null check; if the metadata of the index returns "null" as sort order, then the order will be set to "A".
SR-C88015 · Issue 427061
Null check tuned for hotfix bulk import
Resolved in Pega Version 8.1.6
If a hotfix contained any changes to rules, the import failed with a null pointer exception.This was traced to a null bulk object. Investigation showed that if debug logging was enabled on ESBulkIndexerEmbedded, the system was attempting to get a value off of customBulkRequestBuilder, an object that could potentially be null but that was not subjected to a null check until after the debug statement. This has been resolved by adding a conditional within the debug statement to output a different message if the builder is null, preventing this issue from occurring.
SR-C93572 · Issue 440080
Search initialization logic updated to ensure consistent node member information
Resolved in Pega Version 8.1.6
The search function was intermittently failing across nodes after restart. Investigation showed that this was due to inconsistent results from search initialization cluster logic using Hazelcast APIs to tell whether or not a given node was part of a Pega cluster. To resolve this, the logic has been updated to rely on ES APIs instead of Hazelcast cluster membership to determine offline nodes.
SR-D23170 · Issue 493024
Elasticsearch will ignore tokens for not-analyzed fields
Resolved in Pega Version 8.1.6
When performing re-index, many warnings were thrown indicating a workitem could not be indexed. Investigation showed that this was related to work objects that have very long text stored in text type property because Elasticsearch has limit for token length equal to 32766 bytes. To resolve this, an ignore_above property has been added for not-analyzed fields which will cause Elasticsearch to ignore the token.
SR-D15520 · Issue 497156
Exported formatting corrected to display security scan line found detail
Resolved in Pega Version 8.1.6
Running a Rule-Security-Analyzer scan using a pyUnsafeURL regular expression and RSA provided items found, but the exported results did not contain line found detail. Investigation showed this was caused by the results being converted to an HTML table when the result itself contained HTML tags, resulting in broken HTML generation. To resolve this, the results will be sanitized for display as HTML.