SR-A96539 · Issue 264614
Report Definition parameter passing improved for grids
Resolved in Pega Version 7.2.2
When run report was configured on a grid, the Data-Click attribute for a Report definition action with the parameter of type Pagename.Prop inside the grid did not generate properly. The parameter passing has been improved to address this issue.
SR-A96539 · Issue 265411
Report Definition parameter passing improved for grids
Resolved in Pega Version 7.2.2
When run report was configured on a grid, the Data-Click attribute for a Report definition action with the parameter of type Pagename.Prop inside the grid did not generate properly. The parameter passing has been improved to address this issue.
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-A99155 · Issue 253246
Mobile dirty page handling corrected
Resolved in Pega Version 7.2.2
When the "X" (Close) icon was clicked in the Mobile Create Opportunity/Lead/Contact form and then the cancel button in the prompt popup was clicked, the same page returned and the app went into infinite loading mode. This was caused by a missed use case; when the document is found to be dirty and user decides to stay on the page, the code just returned. This has been fixed.
SR-A76763 · Issue 251569
Ensured Dirty pop up appears for mobile log off
Resolved in Pega Version 7.2.2
While closing a dirty form on a mobile device, the warning popup was not shown while logging off. A check has been added to control_actions so logging out will return if dirty to resolve this.
SR- · Issue 270969
Mobile Client Cache populated with pyWorkPage info
Resolved in Pega Version 7.2.2
While creating a PegaSurvey question using the simple question rule form, the product was not saving the selected response option to the "Map answer to property" property on the Answers tab of the simple question rule form. It was working online, but on a mobile device (both online and offline) it was failing to save that property to the Client Cache. This was an error with the properties of pyWorkPage defined in pyDefault with empty values not getting packaged, and the API has been updated to correct this.