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.
SR-D24651 · Issue 495766
Proper assignment instructions sent when transferring
Resolved in Pega Version 8.4
Assignment instructions were not getting added properly when transferring to Workbaskets. Because both .pyInstruction and Param.InstructionNote are set in call Reassign (to workbasket), the same instruction value was being given twice. To resolve this, step 8 (Call Reassign) of Work-.pyReassignAssignment has been modified and will not send the InstructionNote param as instruction is already updated on the newassign page with the instruction value on reassign page in the previous step (step 7).
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.
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.
SR-D39302 · Issue 507982
Report name in tab uses localization
Resolved in Pega Version 8.4
After creating a field value with field name as pyCaption to localize the report definition name, the title in the report definition tab was not translated. This was traced to Step 1 of the activity displayReport using an old localization function, and has been resolved by changing the localization of document title to use pyCaption.
SR-D39972 · Issue 513461
UpgradeOnOpen updated to use property set
Resolved in Pega Version 8.4
After upgrade, using the revalidate & save wizard on MapValue rules (Rule-Obj-MapValue) generated null pointer exceptions in the tracer file and rules failed with bad status. This was traced to changes made in the Java step of UpgradeOnOpen that used the getReference() method, and has been resolved by updating the UpgradeOnOpen activity in the Rule-obj-Mapvalue class to use property set.
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-D26785 · Issue 496445
Corrected error when persisting temporary work object
Resolved in Pega Version 8.4
When persisting a temporary work object using the Persist case shape, the internal assignment handle was not updated to include the work object's ID. Subsequent attempts to access the internal assignment (such as the "Edit" button on the Review Harness) resulted in errors. Investigation showed that when a temporary case was persisted, pyInternalAssignmentHandle was not getting recalculated after pzInsKey was updated. To resolve this, the configuration on the edit button has been modified to use .pxFlow(pzInternalCaseFlow).pxAssignmentKey which is what pyInternalAssignmentHandle declare expression was also returning.
SR-D47583 · Issue 518040
IsMobile 'when' configurations are properly displayed in mashup preview
Resolved in Pega Version 8.4
Given two layouts configured based on the 'when' rule pyIsMobile, the mashup preview did not work in the mobile form factor. This was only an issue with App Studio preview of a mashup and did not have an impact on the enduser use of the mashup, and the same mashup code viewed on mobile/desktop worked as expected. Investigation showed that the 'when' rule was evaluated correctly for the application level, but in mashup it was evaluated to false even when opened in mobile view from App studio. The Rule-Utility-Functionchecks to see if an overridden useragent has been specified and if it has, then it uses it for the preview in App Studio, however in mashup the userAgentDetails did not contain any of the satisfying conditions under which the condition might be returned as false. The issue in this case was traced to the Rule-Utility-Functionneeding to handle the scenario of Mashup Preview by checking if the thread was from the mashup preview, and that has been implemented.