SR-A91955 · Issue 260732
Filter icon made accessible
Resolved in Pega Version 7.2.2
When the Enable accessibility add-on was checked, the filter icon was not selectable. This has been corrected.
SR-A94690 · Issue 261686
Report Editor displays Associations
Resolved in Pega Version 7.2.2
When using a custom activity to display properties in the data explorer, the "More" link is not displaying the associations when added. This was an error in the logic which determined whether pyReportEditorProperties exists for the class or not, and has been fixed in pzGetCustomPropsForTreeGrid.
SR-A77395 · Issue 255085
DB2 external mapping values used for filtering
Resolved in Pega Version 7.2.2
When using the "External Mapping" feature in a class to map column names to different property names in DB2, the filter conditions in a report definition rule either generated incorrect SQL in the report viewer for "Select Values" or the error "There was a problem getting a list" appeared. This error was caused by the SQL query using the property name instead of the column name, leading to external mapping for the properties not being considered. The pzGetAvailableValues activity has been modified to get the correct column name based on external mapping.
SR-A99040 · Issue 268520
Cleared email field in FieldMarketer campaign remains blank
Resolved in Pega Version 7.2.2
If the Email field of a FieldMarketer campaign was cleared and saved, closing and then reopening the session filled the email field with the Operator ID, which is not a valid email address. This was traced to Operator Email always defaulting to OperatorID if empty, and the activity has now been modified to not set the email field if empty.
INC-102005 · Issue 556731
Child case ID prefix preserved
Resolved in Pega Version 8.4.2
When configuring a case as a child case in App Studio, the case ID prefix was cleared out of the field on the Settings tab for the case type. Investigation showed that when the child case was added to the parent case in App studio, pzaddcasetypetoapp was called but the parent activities did not pass the CaseID parameter of the child case type. This caused the CaseID prefix of the child to be null and displayed as blank in the Settings and Application. This has been corrected by ensuring the system will get and set the parameter value.
INC-119754 · Issue 561523
Corrected 'when' rule context for GetCaseDetails
Resolved in Pega Version 8.4.2
The Pega REST API Get Method /cases{CaseID} failed if the Child Case was set with Manual instantiation using a 'when' rule. This was traced to the 'when' rule being resolved using @baseclass instead of the class of the case type, and has been resolved by updating the pzGetCaseDetails activity to evaluate the 'when' rule on the case page.
INC-120608 · Issue 573001
Temporary case creation from Cosmos resolved
Resolved in Pega Version 8.4.2
Creating a temporary case in Cosmos Portal was not working. Investigation showed that the pySkipCreateHarness and pyCreatesTemporaryObject properties were not populating properly on the D_StartingFlows data page, which was traced to the way openSelectedColumns API handles non-exposed columns. To resolve this, the system has been updated to use the openEngine API for opening starting flows if the pySkipNewHarness or pyCreatesTemporaryObject property values are null.
INC-121435 · Issue 563877
Handling added for null requiredskillcount on assignment
Resolved in Pega Version 8.4.2
If the property pxRequiredSkillCount was blank on an assignment when moved to a workbasket, it was never presented for Get Next Work. To resolve this, handling has been added which will change the null to 0 so the assignment is properly queued.
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.
INC-128087 · Issue 572452
Temporary case creation from Cosmos resolved
Resolved in Pega Version 8.4.2
Creating a temporary case in Cosmos Portal was not working. Investigation showed that the pySkipCreateHarness and pyCreatesTemporaryObject properties were not populating properly on the D_StartingFlows data page, which was traced to the way openSelectedColumns API handles non-exposed columns. To resolve this, the system has been updated to use the openEngine API for opening starting flows if the pySkipNewHarness or pyCreatesTemporaryObject property values are null.