SR-A23665 · Issue 248776
Percentage calculated by control carried into Excel export
Resolved in Pega Version 7.2.1
If a Report Definition calculated the percentage by using the control, the percentage would display in the report browser but 0.00% would be displayed in the Export to Excel. The step page for the control being executed at display time and export are different, so the activity is unable to get the ".pySummaryCount(1)" from the step page. To fix this, pzGetHTMLPropertyValue has been modified so it acts on the step page of the property rather than the primary page the function was executed against.
SR-A97401 · Issue 265625
DASS validation can be switched from ERROR to WARN
Resolved in Pega Version 7.2.2
An enhancement has been added to allow optional switching of the validation of the column type mismatch to WARN as a save-time error/Guardrail warning instead of ERROR. This is based on the new DASS function 'reporting/validateColumnTypeMismatchAs', and the owning ruleset is 'Pega-Reporting'. Note : Even though save-time and run time validations are skipped using this DASS, the query may fail if the database does not support varchar and decimal comparison.
SR-A93826 · Issue 264612
Corrected Field level audit issue
Resolved in Pega Version 7.2.2
Field level auditing was creating two extra "TrackSecurityChange_Change" entries when a new item was added to a Page List at the same time an existing item was removed. It was also updating audit incorrectly the item value was changed for one row at the same time another row was added. This has been fixed by modifying the Memo audit functions to update the values correctly on save when an entry or row is added/edited and other is removed.
SR-A87322 · Issue 260290
Enhancement to display custom properties during editing based on when
Resolved in Pega Version 7.2.2
It was assumed that if pyShowCustomProperties returns false, only the custom properties are shown while editing a report in the data explorer. This was not always true based on checkout privileges, and was therefore inconsistent with the name of the when rule. In order to meet expectations for filtering, pzPrepareReportExplorerFieldNames and runReport have been updated to reference a new 'when' rule called pyReport_ShowCustomProperties. This function will filter the properties as expected based on the available when rule and will reference pyShowCustomProperties for backwards compatibility reasons.
SR-B36689 · Issue 292880
Performance improvements for CaptureInteraction without VBD
Resolved in Pega Version 7.3
CaptureInteraction was slow when not using a VBD server due to a call to the function GetVBDService that fired even when there was no intention to use VBD and it was not configured. This was an unintentional side effect of code that listens for VBD being ready in case it is in mid-initialization or cluster nodes are restarting. To improve performance, GetVBDService has been modified to avoid waiting for the VBD cluster if VBD is disabled using DSS prconfig/initservices/vbd/default = false.
SR-B40038 · Issue 298378
Column alignment with filter icon fixed for Chrome and IE
Resolved in Pega Version 7.3
When a grid was configured with filtering and 'Freeze Grid Header' option was enabled, at runtime the column header did not align as expected with the filter icon when using Chrome or IE. In IE, the anchor element for filter icon needs to have height set to render properly. In Chrome, the oflowDiv gets a height which caused the problem. To resolve the issue, the addHeightToFilterIcon function in ui_grid JS has been modified to consider freeze header cases.
SR-B8696 · Issue 279855
Support added for FCM GetNextWork
Resolved in Pega Version 7.3
When using Federated case management (FCM) to get next work, the work object pulled was not assigned to the operator. This was due to the implementation of FCMR not supporting the moving of workbasket assignments to worklist through get next work. To support this use, the following functions now accept extra parameters as last param: FCMRGetNextWork FCMRGetNextWorkItem FCMRProbeNextWorkItem This will enable distinguishing between normal GNW and federated GNW, and it is possible to override any py rule call MoveToWorklist.
SR-B54906 · Issue 313350
Column calculations fixed for RD exported to Excel
Resolved in Pega Version 7.3.1
When exporting a report definition that contains calculated columns to Excel, the columns were either blank or 0% for each row even though the correct calculated values appeared in both the HTML preview and the PDF export. Additionally, date formatting was not applied in the Excel export. This was due to legacy code inserted in an earlier version of Pega to repair Export to Excel; the fix is no longer necessary since the exporting function was reworked, and has been removed.
INC-142248 · Issue 601766
Added safe check for ActivateTabs
Resolved in Pega Version 8.3.5
After configuring a data transform action for a close icon to set a requestor level data page value and a parent-level dynamic layout was configured with a refresh when condition to track this Data page property, pzMicrodynamicContainer was throwing a null pointer exception after this refresh occurred indicating the tag name passed to isRegularTarget function was invalid. This has been resolved by adding a safe check to ensure that activateTabs is called only for tab based Ajax containers.
INC-134497 · Issue 578360
Corrected mobile data transform format handling
Resolved in Pega Version 8.5.2
An intermittent issue was seen in the mobile app where data was not propagated properly because a Data Transform failed. The error "Failed to run data transform fs_work_task_plannedtask_settaskdetailsfromparent TypeError: sourceProperty.getValue is not a function" was generated. This was traced to a difference in the generated data transform format where a success scenario considered “Problem” as a page, whereas a failure case considered the “Problem” as a property and the getValue() operation failed. This has been resolved.