INC-220928 · Issue 739155
Added handling for Node Level Data Pages not loading automatically
Resolved in Pega Version 8.8
After update, the MQ listeners were not starting. This was traced to the Global Resource Setting references in the listener rules that utilize data page lookups; MQ listeners started as expected when they were hard-coded with the values present on the data page. Investigation showed this was caused by the activity running in an unauthenticated context, and has been resolved by allowing the app requestor to skip authentication.
INC-216727 · Issue 730957
Inline error message consistent for currency field
Resolved in Pega Version 8.8
After update, an inline validation error triggered on a currency field inside of a text box disappeared when the page was scrolled back to the top. This was traced to the display_removeErrorImage function being called from validation_ValidateFieldOnEvent due to an “onBlur” event, and has been resolved by removing the onblur for a number of decimal type to prevent clearing the validation messages at field level on tab out.
INC-220985 · Issue 728989
IsPropositionActive property retained during save-as
Resolved in Pega Version 8.8
When the action treatment was saved-as from a lower version to higher version, the treatment DDR form was missing the attribute "pyPropositionactive" property in the higher version. This was traced to the pyIsPropositionActive property being removed by the PreSaveAs activity of the DDR rule because it was considered not relevant for a non-proposition type decision data. This has been resolved by adding handling for the pyIsPropositionActive flag.
INC-230579 · Issue 742038
Inline error message consistent for currency field
Resolved in Pega Version 8.8
After update, an inline validation error triggered on a currency field inside of a text box disappeared when the page was scrolled back to the top. This was traced to the display_removeErrorImage function being called from validation_ValidateFieldOnEvent due to an “onBlur” event, and has been resolved by removing the onblur for a number of decimal type to prevent clearing the validation messages at field level on tab out.
INC-183530 · Issue 668470
Null check added for missing compiler path
Resolved in Pega Version 8.7
After upgrading from Pega 7.3 to Pega 8.6, libraries were not loading correctly and a java error was seen. This was traced to the compiler default path values not getting picked from DSS / settings->compiler->Default paths, which was caused by a null value for the DASS setting in the systemSettings map. To resolve this, a null check has been added and an update has been made to use getEngineDynamic to ensure this setting is picked on node startup.
INC-193767 · Issue 683299
Handling updated for validating properties with a FieldValue
Resolved in Pega Version 8.7
Running a report which included a property calculated by a Declare Expression generated an excessive number of log messages indicating "Error occurred while executing forward chaining on page 'pyReportContentPage.pxResults". Degraded system performance, stack overflow, and other similar issues were seen. This was traced to an infinite loop that resulted from a missed use case for a Report Definition with a Target property of a Declare Expression with FieldValue, and has been resolved by disabling autochain while validating properties with a FieldValue.
SR-D18879 · Issue 500643
Logic update made to PrepareColors to resolve calculation ambiguity
Resolved in Pega Version 8.4
When a Report Definition was summarized, the executed report showed a graph for multiple categories but generated the error "No data to display" if given a single category. This was traced to an ambiguity in the Java syntax of the Rule-Utility-Function pzPrepareColors that led to a NegativeArraySizeException on a customer's environment. To resolve this, parentheses have been placed around a ternary operator to ensure the correct order of operations.
SR-D33359 · Issue 505774
SelectAll properly applied to only the page selected
Resolved in Pega Version 8.4
In repeating grid, applying SelectAll on one page resulted in it being applied to the next page as well even though all records in the other page were not selected. Investigation showed that on change, the 'when' condition added to refresh the list was always false. To resolve this, the condition in section pzBulkProcessingCheckbox which refreshes the list once the checkbox is changed has been removed.
SR-D42437 · Issue 513649
Pulse @mention will avoid triggering search request if no suggestion list is available
Resolved in Pega Version 8.4
Search threads were causing requestor Lock Exceptions due to poorly optimized queries sent to ElasticSearch when a Pulse mention was attempting to look up a person (e.g. "@"+typing) and the search of case objects to match to that search were performing poorly. To resolve this, an update has been made to avoid triggering requests if the suggestions list is not available for the search query.
SR-D45828 · Issue 518021
Added variable null check to resolve refresh condition on dynamic layout not working
Resolved in Pega Version 8.4
Given a setup where a parent section had several section includes, one of which had a property that was set to refresh and disable another section when the property changed, on change the refresh action was not working and hence the disabling did not work. Refreshing the browser corrected the behavior. Javascript errors were noted on the console. This has been resolved by adding a null check on the variable to avoid exceptions.