INC-142277 · Issue 601778
Header style inheritance corrected
Resolved in Pega Version 8.1.9
When a header style for a container was explicitly set, any layout underneath inherited that style when using container formats set to 'Use Skin Base Settings'. This has been resolved by increasing specificity for the header title.
SR-D39601 · Issue 509518
RRDisplaySection made available to assist Edge compatibility
Resolved in Pega Version 8.2.4
When the Pega Platform was being used with Microsoft Internet Explorer Compatibility Mode ON, it was not possible to use the select filter gadget due to a browser compatibility issue: enabling the filter condition for the report definition caused the SelectValues button to stick in loading mode when clicked. Changing the Microsoft Internet Explorer Document Mode for Harness pzRRDisplaySection to IE=Edge corrected the issue, but the rule was final. To resolve this, the pzRRDisplaySection has been made available to allow override for customers still using Microsoft Internet Explorer.
INC-136752 · Issue 587728
Adding handling for custom image on S3 storage space
Resolved in Pega Version 8.1.9
When using an S3 repository for Content storage, trying to create a new space with a custom image did not upload the image. Investigation showed that when attachment storage is configured as an external repository, the pyAttachStream property which is used to create the the thumbnail was getting cleaned as part of the saving logic. This has been resolved by adding an update that will hold the attachStream value in a local property before calling attachment save.
SR-D33832 · Issue 503957
Configurability added to SLA Timeliness to allow either 0 or NULL for Unqualified records
Resolved in Pega Version 8.2.4
When using a Report Definition where the count (aggregate function) was used for both the WithinSLA and Past Deadline columns, the correct value was not getting displayed. The correct value was displayed when the sum function was used instead of the count function, but clicking 'value' returned all values despite what value was displayed on the screen. This was a behavior change related to performing a drill down action on a report definition. As per the older behavior, drill down relies on a specific value (NULL) to determine whether a record is a candidate to be shown in the drill down report. From 7.2.1 forward, drilldown relies on value 0 instead of NULL to make the average summarize function work properly, which led to a change in behavior when used with other summarize functions like sum and count. To resolve this, SLA Timeliness related RAFs have been modified to conditionally return either 0 or NULL for Unqualified records based on a DASS config.
SR-C60129 · Issue 402896
Removed default height from pzTimeline_PresentationTab
Resolved in Pega Version 8.1.1
When using Timeline Control, the Default Height in the presentation tab was not being removed when it was changed to be blank and saved. When the control was opened the next time, it defaulted to show Height 300px and remained at that value despite repeated attempts to blank it. This was traced to a default height in the "pzTimeline_PresentationTab" section, and this default has now been removed.
SR-C60129 · Issue 402902
Removed default height from pzTimeline_PresentationTab
Resolved in Pega Version 8.1.1
When using Timeline Control, the Default Height in the presentation tab was not being removed when it was changed to be blank and saved. When the control was opened the next time, it defaulted to show Height 300px and remained at that value despite repeated attempts to blank it. This was traced to a default height in the "pzTimeline_PresentationTab" section, and this default has now been removed.
INC-125334 · Issue 581939
Focus persists for embedded Tab Group layout with section refresh
Resolved in Pega Version 8.1.9
When a Tab Group Layout was configured with multiple sections using multiple input elements including one with a 'Refresh this section' action, using the Tab key to reach the input element, make a change, and hit Tab again caused the focus to reset to the top input element. This has been corrected.
INC-126255 · Issue 580910
Resolved "maximum limit for pending changes" error
Resolved in Pega Version 8.1.9
When attempting to create a work object in a custom way using doCreateNewCase from the Smart investigate layer by using the RMButtonWithoughtWorkCaseNGP section, a popup showed the error “You have reached maximum limit for pending changes. Please commit/cancel one or more changes to continue.” The error did not occur when creating the case using the out-of-the-box Create New Work action. This was traced to the custom configuration creating work object threads that were not destroyed after the work item is closed. To resolve this, handling has been updated for passing dynamiccontainerID and contentID parameters for OpenWorkByURL case. Note that the pzUpdateActionInfo activity must be called in any custom activity before the actual activity is invoked.
INC-133978 · Issue 587697
Overlapping columns fixed in ReportViewer
Resolved in Pega Version 8.1.9
When Report Viewer was used for Report Definition, displaying it on dashboard columns resulted in columns that overlapped each other. This was traced to a resize issue related to the scrolling checkbox and has been resolved.
SR-C64292 · Issue 405249
Corrected multiselect dropdown event handling for IE11
Resolved in Pega Version 8.1.1
When using IE, multiselect dropdowns would work correctly the first time they were displayed, but disappeared on subsequent clicks. This has been fixed by correcting the event handling for IE11.