SR-D55233 · Issue 520721
AJAX container handling updated to use Harness context API
Resolved in Pega Version 8.4
After creating a service case and adding a task to the case, a button configured to refresh the section on a condition worked correctly the first time but did not respond to a second click. This was traced to the tasks being located in two different Ajax containers: in this usecase the condition evaluation logic related to actions was still using the regular DOM API and using the context from the first AJAX container. To resolve this, the system has been updated to use the harness context API pega.ctx.dom.getElementsByName instead of DOM API to resolve the necessary elements from the correct AJAX container.
SR-D32890 · Issue 507595
Report on descendant class instances no longer defaults to using dynamic union
Resolved in Pega Version 8.4
When the instance view of System-Status-Nodes was launched, an error was observed in the log stating that properties weren't optimized in a different class (Pega-Landing-System-HighAvailability). This was traced to the option "Report on descendant class instances" being enabled by default to use dynamic union where applicable, causing that to be applied upon execution of the report definition to fetch the instances. This has been resolved by unchecking the ReportDefinition "Report on descendant class instances" option.
SR-C53680 · Issue 402914
Filter value Autocomplete uses localized text for the 'Case Type' string
Resolved in Pega Version 8.1.1
The Filter value autocomplete field of the Case Manager portal bulk action landing page was not working as expected while using the Japanese locale setting. If the locale setting was English or empty, the filter value was displayed correctly in the autocomplete. This was an issue with comparisons being hard-coded to use the literal text string 'Case Type', which was failing in localization. To fix this, a 'when' rule has been added to compare localized text against pyFilterName and use it in the appropriate rules.
SR-C57025 · Issue 402913
Filter value Autocomplete uses localized text for the 'Case Type' string
Resolved in Pega Version 8.1.1
The Filter value autocomplete field of the Case Manager portal bulk action landing page was not working as expected while using the Japanese locale setting. If the locale setting was English or empty, the filter value was displayed correctly in the autocomplete. This was an issue with comparisons being hard-coded to use the literal text string 'Case Type', which was failing in localization. To fix this, a 'when' rule has been added to compare localized text against pyFilterName and use it in the appropriate rules.
SR-D7323 · Issue 493178
Pin Case to Board updated to use unique IDs for different workpools
Resolved in Pega Version 8.4
When using the Pin Case to Board functionality, it was only possible to find and pin cases in the default/current work pool of the working access group and not any other cases in any other work pools which allowed access to open/search/process. This was due to pyLabel being used to compare if a value entered was valid, which was not a unique key. To resolve this, the pyValidatePinDetails activity in Pega-Ext-Mentions-Documents, Pega-Ext-Mentions-Cases, and Pega-Ext-Mentions-Groups classes have been updated to compare pzInsKey instead of pyLabel to check for validate pin.
INC-142223 · Issue 600456
Mobile List rule correctly removed when case type creation fails
Resolved in Pega Version 8.4.4
When trying to create a new case type, a "Branch ruleset not candidate" error occurred. During this error process, the Mobile List rule that was created did not get removed. As a result, an InstanceAlreadyExists error occurred once the first issue was addressed and the attempt was made to create the case type again. Investigation showed that Mobile related views are created in pxCreateNativeListPageForCase activity but on failure during case type creation they were not rolled back in pzRollbackAndDeleteCasetypeAssets activity. This has been corrected.
SR-D54184 · Issue 519319
Enhancement added to customize the clearing of error messages when performing modal actions
Resolved in Pega Version 8.4
Opening any modal dialog, for example adding a row in Table/Grid layout, cleared any existing validation error messages on UI screen. In order to make this behavior customizable, a flag has been introduced to control the clearing of error messages from primary pages on grid actions. Updates have been made in the ui_grid, ui_grid_dragdrop and ui_repeatlayout JS files to include this flag in activity parameters and the pzdoGridAction activity has been modified to consider the flag.
SR-D54594 · Issue 521635
Enhancement added to customize the clearing of error messages when performing modal actions
Resolved in Pega Version 8.4
Opening any modal dialog, for example adding a row in Table/Grid layout, cleared any existing validation error messages on UI screen. In order to make this behavior customizable, a flag has been introduced to control the clearing of error messages from primary pages on grid actions. Updates have been made in the ui_grid, ui_grid_dragdrop and ui_repeatlayout JS files to include this flag in activity parameters and the pzdoGridAction activity has been modified to consider the flag.
SR-D55461 · Issue 523176
Corrected modal timing issue when deleting Data Transform or Property rules
Resolved in Pega Version 8.4
When deleting Data Transform or Property rules, there were times when the deletion modal only appeared briefly and then the web page turned white, the message "No stream to display" appeared at the top of the web page, and all other content disappeared. This was more frequent when the requestor had been idle, but occurred under other situations as well. This was traced to a timing issue: once the modal action (localaction -modal or flowinmodal) is triggered the event queue should be paused, but in some cases the system was executing the next action in the queue and causing the no Stream to Display error. To resolve this, pega.u.d.bModalDialogOpen will be set to true in the prerender callback instead of success callback. This will set the flag in the pre-rendering logic so that correct modal status will be known to the action processor.
SR-D62361 · Issue 534811
Read-Only harness takes precedence over editable section with when condition
Resolved in Pega Version 8.4
Given a harness which was marked as Read Only and contained sections which were configured as editable based on some conditions, when the condition became true, the section became editable and ignored the read only conditions applied on the harness. Investigation showed that when a read-only 'when' rule evaluated to false, it rendered the layout in Edit mode instead of falling back to the read-only status of parent. This has been corrected by ensuring that when read-only evaluates to false, the system will fall back to the parent read-only status.