SR-D564 · Issue 438145
Removed job for column population when it is not needed
Resolved in Pega Version 8.3
While optimizing the data type class properties, the column population job failed with the exception "ERROR - Exception in column population ... column pc1.pzinskey does not exist". Although there was no impact from this error, the SQL exceptions in logs could cause confusion. This has been resolved by updating the system so that if the table has no pzinskey or stream columns, no job will be queued for column population.
SR-D6555 · Issue 457242
Access When check added for pyStartCase privilege
Resolved in Pega Version 8.3
If a privilege was defined in the pyStartCase flow rule and the access role to object assigned a privilege based on 'Access When' (not production level), the user was not able to start a case. This was traced to the havePrivileges RUF passing an incorrect primary page to evaluate the privileges in combination with the 'access when'. To resolve this, the engine API will call tools.getAuthorizationHandle().havePrivilege for each privilege until it finds a match.
INC-123033 · Issue 561388
Updated logic for delegating when the RARO exists
Resolved in Pega Version 8.4.2
When trying to delegate a Data Type, the validation error "Update Record Failed: This record is non-versioned and already exists and can not be moved to a different ruleset" appeared. Because data type delegation is dependent upon the existence of a RARO for the delegated data type, when delegating the ruleset of the RARO to accessgroups with the same roles the code was attempting to update the RARO. Updating the RARO determines if the Ruleset of the RARO is unlocked. If the ruleset is locked, then the logic attempts to select a new ruleset, but the RARO cannot be moved to a new ruleset. To resolve this, the logic has been updated so that if the RARO exists, the system will not try to create a new instance.
SR-D93112 · Issue 554909
Added backwards compatibility for migrated when rules
Resolved in Pega Version 8.4.2
After upgrading from v6 to v8, the 'when' rules were replaced with "" in a custom decision tree. In 7.2 and earlier releases, the Rule-Obj-When function alias had its param name as "strName"; this was changed to "blockName" in later versions of Pega. To handle backwards compatibility, the pzEmbedUpgradeToHarnessBased activity has been modified to read the strWhen param value from pyCallParams and set it to blockName params correctly under pyFunctionData.pyParameters data model, conditionally only for Rule-Obj-When function alias.
SR-D65174 · Issue 560603
SetInterval will increase when AQD delay is defined
Resolved in Pega Version 8.4.2
With a 5000ms delay in place, executing scenario test cases resulted in errors such as values sporadically not being entered in their respective fields when the test was run, test runs that failed even though the data was entered as expected, or the submission of a test case assignment (Next button) executing the next step before the new screen was loaded. Investigation showed this issue was occurring when the system encountered a slower machine and a delay in loading pages, and was traced to the executor not waiting long enough due to the implicit setInterval of 8 seconds. It was possible to add a local delay in AQD settings for slow pages, but the system-set setInterval interfered with this delay. To resolve this, changes have been made to the executor module where setInterval is invoked that will increase the setInterval time when AQD delay is defined, so that setInterval will not interfere with a locally-set AQD delay.
INC-175630 · Issue 653863
Application selections only announced when visible
Resolved in Pega Version 8.7
The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.
INC-127077 · Issue 564109
Busy indicator appears when uploading via Select
Resolved in Pega Version 8.4.2
After upgrade, the “loading symbol” (busy indicator) was not appearing while uploading large attachments using the Select button. This was a missed use case in recent changes to related to AsyncUpload, and has been resolved.
SR-D18332 · Issue 490989
Enhancements added for scrolling when an overlay is present on the screen
Resolved in Pega Version 8.3
When scrolling the screen with the autocomplete window open, the autocomplete window became disjointed with its field. This has been addressed with an enhancement to improve the visual experience. With these changes, the overlay will be launched at the place where the mouse pointer is located. Earlier, the overlay was launched at the starting of the element on which the launch overlay was configured. Previously, if the parent element was scrolled the overlay used to remain at the same position. With the new changes, the overlay will be attached to the parent element when it is scrolled. In the third use case, when the content was launched dynamically, there used to be a scrollbar in the parent viewport as the viewport expanded. With the new changes, the viewport will remain the same and the dynamic content in the overlay will now have a scrollbar.
INC-195387 · Issue 681673
HandleResponses updated for use with optimized campaign
Resolved in Pega Version 8.7
After updating from Pega 8.4, responses were not processed in the pxHandleResponses Data flow if the "pyCampaignOptimization" flag was set to true. This was traced to a missed use case for an optimized campaign, and has been resolved by modifying the condition in HandleResponses.
SR-D90711 · Issue 553092
Portal harness maintained when opening email link
Resolved in Pega Version 8.4.2
When an email link was opened (pxOpenAssignmentLink), the portal harness was replaced with the case Perform harness. This has been resolved by ensuring the 'flex' CSS class is added for the portal harness div when using pyMobileSnapStart and a top navigation portal.