SR-D24880 · Issue 494172
CEP bucket size increased to 1 minute
Resolved in Pega Version 8.2.3
Frequent DSM Data Flow Errors were observed in production nodes with very high event rates. This was traced to the default bucket size for CEP being 1 second for a 31 day window, which was not sufficient to handle high volume use which may create an event strategy window large enough to hit the Cassandra column size limit. In order to resolve this, the default bucket size has been increased from 1 second to 1 minute.
SR-D23992 · Issue 494758
Null check added to handle portal refresh when first launched
Resolved in Pega Version 8.2.3
After configuring a button / dropdown in caseworker portal header with 'Refresh current action' onclick or onchange action, an exception appeared if the refresh harness was triggered and the Refresh did not happen. This was traced to the refresh harness happening after portal launch and before any DC action occurred. The portal 'history.state' is null at launch, meaning there was nothing to refresh. To handle this corner case, a null check has been added for the history state to avoid console errors.
SR-D23490 · Issue 496575
Interface changes made to avoid unexpected workitem deletions when removing stale locks
Resolved in Pega Version 8.2.3
Attempting to delete lock instances of work objects by directly opening the lock item found through navigating to (Dev Studio) App > Classes > System-Locks actually resulted in deleting the work item instead of just the lock. This was due to System-Locks being uniquely identified by the WorkItem that they belong to rather than having their own specific key. This meant that clicking on one of the instances caused the system to respond by presenting a "default RuleFormLayout section" which included a delete button keyed to the actual workitem, but this was not made explicitly clear in the interface. In order to prevent unexpected item deletions, the table has been replaced with a link to the proper System-Lock interface, specifically the "My Locks" window.
SR-D26589 · Issue 496720
Logic updated to populate pagelist data on uploaded multi-sheet Excel files
Resolved in Pega Version 8.2.3
When trying to use the activity pxParseExcelFile on an Excel file containing three sheets where each sheet had a different pagelist, the properties mentioned in sheet 1 were populated on upload but the remaining sheets only showed the error message "Could not get clipboard property for reference Work Queues.". This was caused by an error in Row index handling for the additional sheets, and has been resolved by updating the logic to populate the data in the clipboard.
SR-D23340 · Issue 497606
Calendar begins with Saturday in the Arabic locale
Resolved in Pega Version 8.2.3
When using the Arabic locale, the week was not starting on Saturday as expected, but was showing Thursday as the first day. This has been corrected.
SR-D28985 · Issue 498015
Improvements made to Excel data import handling for decision tables
Resolved in Pega Version 8.2.3
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-D27994 · Issue 498436
Chart fixes for localization and filtering
Resolved in Pega Version 8.2.3
A problem was seen with a chart where the column was a date and its labels were not localized even though the values were displayed in the data grid correctly. This was resolved by updating the pzMultiSeriesData XML Stream to generate the series name attribute with the localized value. An issue with a drill down report pulling the data for entire criteria on click of specific set even though the summary view or clicking on the report data worked correctly has been fixed by adding an enhancement for using the aggregate column as a filter on drilldown with "Is not null". Additional work was also done to resolve an issue of a broken case causing the chart not to render when the aggregates were in an unexpected order.
SR-D24083 · Issue 498487
Guardrail warning removed for setting filter by format on RD sourced grid
Resolved in Pega Version 8.2.3
After upgrade, use of the 'filter by format' (Configuration on table layout column) for grids sourced with report definition caused confusion in that the option now exists to either to see the value or the formatted value in the filter panel. Previously, a grid layout would show a date format in both the column of a grid and the filter of that column, but the filter changes produced a date format on the column within the grid but the date time format applied on filter of the column. This behavior change will be reflected in updated documentation. In addition, there is a workaround to recreate the old behavior by changing the column 'Date assigned' from a filter by value to format, but a moderate guardrail warning was created when filter by format was set on any column of a grid sourced to a report definition. This has been removed: when filter by format is selected, no guardrail warning will be displayed in design time.
SR-D27041 · Issue 499046
Manual value group addition support available
Resolved in Pega Version 8.2.3
In a test case created for a data transform containing a value group property, that value group property could be added by clicking the + sign in the left pane of the test case, but a value group property could not be added manually by clicking the add row button. This has been resolved by adding support for manually adding value list/value groups. The activity steps which were using @java function have also now been replaced with a getproperty function.
SR-D28496 · Issue 499080
Corrected exceptions report appearing on user screen
Resolved in Pega Version 8.2.3
When "Break on all exceptions" was enabled, the exceptions report was visible on the end user screen when using IE11. This has been resolved with updates to the 'pzpega_ui_dynamiccontainer' and 'pzpega_ui_doc_tabsupport.js' files.