SR-127372 · Issue 194363
Fixed ColorPicker control event firing
Resolved in Pega Version 7.1.8
ColorPicker controls associated with a Property which has a default value and configured with an OnChange refresh were not updating when a new color was chosen and instead required an explicit refresh. This was found to be two problems: If there is a value for the property, the background color was set on the inner div and not being replaced when update occurred. Since the color was also being set in the outer div, the inner div setting was unnecessary and has been removed. For the update itself, the processDialog API was not firing the change event upon submit of the modal dialog, but if the event was fired then it implicitly had a refresh added in the markup and was refreshing the section twice. To correct this, the change event is fired from the processDialog API instead.
SR-127388 · Issue 193584
Corrected handling of radio buttons in repeat grids with page groups
Resolved in Pega Version 7.1.8
In the generate radio group, when the radiobuttons control was placed in a repeat grid bounded with page group, the ID attribute of the radio input tag was not in the group and was being generating uniquely, causing the buttons to not hold their value when one was updated. To correct this, the regular expression pattern in pzgenerateradiogroup has been modified to include the page group as well as the page list.
SR-127470 · Issue 192220
Autogenerated CSS for harness skin fixed
Resolved in Pega Version 7.1.8
When using the autogenerated CSS of a skin in a harness, the tags generated for input types were not applied. This was due to the CSS being incorrectly formed, which has been corrected
SR-127491 · Issue 193606
Resolved runtime error when editing complex grid cells
Resolved in Pega Version 7.1.8
When using grid edit mode inline on a grid with a section inside a cell that includes a checkbox and a 'when' condition, a runtime error appeared when the cell was clicked. This was an issue with the wrong reloadElement being passed in the editRow() API, and this has been corrected.
SR-127513 · Issue 196780
JS error resolved for date control in custom filtering section
Resolved in Pega Version 7.1.8
The Date Picker icon on a custom filter section was not opening the calendar popup unless the clear filter button was clicked. This issue occurred when a summarized report included a chart and had the 'Hide summary data' display option enabled, and was caused by an error in the HTML div function for the popover that used the same name for multiple embedded forms. This has been resolved.
SR-127684 · Issue 194461
Fixed Microsoft Internet Explorer 9 freeze with grid row numbering
Resolved in Pega Version 7.1.8
Attempting to Wrap Up an interaction after viewing a section using a repeat grid with row numbering ON using Microsoft Internet Explorer 9 was causing a browser freeze. This was traced to an API issue where the incorrect frame handling was called for the grid, and has been updated.
SR-127710 · Issue 193207
Code updated for multiple select inside a grid using Microsoft Internet Explorer 9
Resolved in Pega Version 7.1.8
Multiple select inside a grid was not allowing the section to be saved when using the Microsoft Internet Explorer 9 browser. This was due to a JavaScript incompatibility with Microsoft Internet Explorer 9, and the code has been updated.
SR-127754 · Issue 192902
Modified TransferAssignment to pass SLA parameter with Reassign
Resolved in Pega Version 7.1.8
Assigning the work object configured with an SLA from workbasket to worklist using the out-of-the-box Transfer flow function before the Goal/deadline was reached caused the SLA escalation action to not be triggered when the deadline expired. This was due to the UpdateSLA parameter not being sent when Reassign was called as a post processing activity of the Transfer flow action. This flow action has been deprecated in later releases and replaced by the new flow action pyTransferAssignment, and the ReassignAssignment activity has now been modified to pass the updateSLA param while calling Reassign.
SR-127806 · Issue 195855
Sort by ID enhanced to handle custom ID formatting
Resolved in Pega Version 7.1.8
Sort by ID was not working correctly for workbasket/worklist if the workID was in the format String-Number-Number and not in expected format of either String-Number or String-Number-String. The Pega-RULES:compareWorkIDs function responsible for sorting the workID assumed the ID would be in this format because it used pxRefObjectInsName - an internal property that could not be overridden. However, it was possible to create another property in the "Assign-" class of a custom rule set that could be updated with the value of pxRefObjectInsName by iterating it through the list, and then it could be configured in a grid as sortable row which could further be sorted through a custom sort function. An enhancement has been added to the compareWorkIDs function to handle IDs in the String-Number-Number format with additional handling for 2 part vs. 3 part IDs.
SR-127809 · Issue 192785
Stage processing refined for casetype launch
Resolved in Pega Version 7.1.8
If SLA was configured for the case type (case wide SLA) it caused the exception "Reconcile inconsistency in stage processing" once the SLA was triggered. This error also occurred when the flow was run on a modal dialog. This was caused by the pxStageFlowID not being set on the pxFlow of the custom flow being called from the SLA. Any flow started backdoor -- via activity, SLA, subprocess, etc -- should not be considered part of the stage processing, and the code has been updated to ensure flows that are not started in the context of the casetype or stage are no longer logged as part of stage history and do not go into stage flow end processing.