INC-201633 · Issue 706557
Reload icon disappears when refresh is ready
Resolved in Pega Version 8.8
After updating the Field Service Mobile App from Pega 8.3 to Pega 8.6, the wait icon continued to be visible even after the refresh was completed. This has been resolved.
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.
SR-D39302 · Issue 507981
Report name in tab uses localization
Resolved in Pega Version 8.2.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.
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.
INC-205938 · Issue 721198
Improved handling for heavy use of PushDailyUserData
Resolved in Pega Version 8.8
The PushDailyUserData agent was causing utility node performance issues due to the amount of data it was fetching from pr_hourly table. To resolve this, an update has been made which will run the agent once per day and chunk large data.
INC-221019 · Issue 725148
Modified timestamp query used by ClusterAndDBCleaner
Resolved in Pega Version 8.8
The job pyClusterAndDBCleaner was failing with the error "ORA-01861: literal does not match format string". This was traced to the sub-activity pzClearOldQueueProcessorBrokenMessages which was not able to remove broken items with encryption in an upgraded environment due to an incorrect timestamp format passed to the Oracle database. This has been resolved by modifying the query to use a timestamp built using INativeSqlBuilder which will include only the information necessary for the deletion of the item.
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-D26785 · Issue 495892
Corrected error when persisting temporary work object
Resolved in Pega Version 8.2.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.