SR-C75536 · Issue 425013
Corrected agent scheduling issue for different server time zone
Resolved in Pega Version 8.3
When a server timezone and the agent schedule used different time zones, a server restart with cleared extract marker resulted in BIX agents no longer running automatically due to the next run showing as scheduled in the past. This was traced to the method used to compare start date time, and has been resolved.
SR-D3144 · Issue 438160
Corrected agent scheduling issue for different server time zone
Resolved in Pega Version 8.3
When a server timezone and the agent schedule used different time zones, a server restart with cleared extract marker resulted in BIX agents no longer running automatically due to the next run showing as scheduled in the past. This was traced to the method used to compare start date time, and has been resolved.
INC-186654 · Issue 669115
GetStatusChanges performance improvements
Resolved in Pega Version 8.7
Performance issues were seen when running the GetStatusChanges report. This was traced to the filtering methods used, and has been resolved by updating the report definition and enhancing the filtering conditions.
INC-139849 · Issue 598127
Sorting icon visible for table in Cosmos on Google Chrome
Resolved in Pega Version 8.5.2
Tables were not showing any sort icon / indicator in the column header when using the Cosmos Theme in Google Chrome. This was only occurring in apps created with the Cosmos theme, and was caused by the sort icon for a non-optimized table using display flex, resulting in the position of the icon being displaced. This was a missed use case of having a non-optimized table in Cosmos, and has been resolved by removing the non-optimized-related CSS code.
INC-213217 · Issue 714194
Updated context handling for executing data transforms in dataflows
Resolved in Pega Version 8.6.5
When performing a sort operation in a data transform on a page list and invoking the Data transform through a Data flow, a java.lang.UnsupportedOperationException was generated on the sort step even though the data was correct. Investigation showed that the dataflows were using a different execution context than the context used for regular activity execution. An update has been made to ensure the correct context is being used while executing data transforms in dataflows.
INC-172124 · Issue 651293
Improved Operator ID selection in Mobile Logs Retrieval section
Resolved in Pega Version 8.7
Data-Admin-Operator-ID.pzOperatorsByApplication returns only the first 500 operators, which is insufficient for large-scale use. There was a workaround of turning off paging for this report definition and setting maximum records to a bigger value, but this caused potential performance issues when opening very large users list. To resolve this, an autocomplete control will now be used to select Operator ID in the Retrieve Device Logs section of Mobile Channel. When part of an operator ID is typed into this control, the first 100 best results are shown and may be selected.
SR-D3655 · Issue 438566
Resolved UI issues with TextArea control
Resolved in Pega Version 8.3
Two issues were seen with TextArea after upgrade: 1) The UI flickered when using a section where a checkbox click caused a TextArea to appear; and 2) When 'size to content' was specified for height in the TextArea, the area became unresponsive when the content was reduced. These issues have been corrected by setting height to auto instead of 0px while updating the text area height.
SR-D10820 · Issue 482682
RDL checkboxes appear properly in minimized window
Resolved in Pega Version 8.3
Checkboxes in RDL were not appearing properly in Microsoft Internet Explorer when the window was minimized if a dynamic layout of type inline quadruple was used. This was traced to the responsive breakpoints of a format overriding the styles for custom checkboxes, and has been resolved by updating the checkbox controls for responsive breakpoints to use a min-width and min-height instead of auto.
INC-171257 · Issue 651734
Expanded results for Proposition Filter Relevant Record Properties
Resolved in Pega Version 8.7
Previously, a maximum of 500 records were returned from pr_data_tag_relevantrecord when using Edit Parameters for the report definition proposition filter rule. In order to accommodate more complex needs, an update has been made to use the D_pxGetClassDataModel data page to fetch all the records and make them available in the dropdown.
INC-191159 · Issue 682362
Validate topics based on all topics in channel instead of default language
Resolved in Pega Version 8.7
if a 'When Rule' was used in Email Receiver to provide some conditions, it was not possible to use topics from the dropdown which were trained with training data in prediction studio. This was a missed use case, and was traced to validation being based on the default language topics. To resolve this, the data page has been modified from getting default language topics to getting a union of topics. The datapage for default language topics has also been withdrawn.