SR-A8538 · Issue 222591
RepeatIndex generation improved
Resolved in Pega Version 8.1
Controls in a triple layout included in a row repeat did not have matching unique IDs and label for attributes. This was due to incomplete generation of the repeatindex for the ID, and has been fixed.
SR-C4920 · Issue 347563
Grid Header checkbox behavior modified for consistency
Resolved in Pega Version 8.1
Unexpected behavior was seen when clicking on the Checkbox present in Header: all other checkboxes changed their state (which was expected), but if the the Readonly checkbox was checked it was also changing the state the first time (which was not expected). After this first state change, the read-only checkboxes were not changing state (which is correct behavior). Previously, the behavior of Select All / CheckAll checkboxes was as follows: If the SelectAll / CheckAll checkbox is checked - Individual checkboxes are checked only when they are NOT disabled If the SelectAll / CheckAll checkbox is unchecked - Individual checkboxes are unchecked irrespective of their DISABLED state The behavior has now been changed as below: If the SelectAll / CheckAll checkbox is checked - Individual checkboxes are checked only when they are NOT disabled If the SelectAll / CheckAll checkbox is unchecked - Individual checkboxes are unchecked only when they are NOT disabled
SR-C7762 · Issue 350154
Commas removed from filter values to resolve validation errors
Resolved in Pega Version 8.1
When using a Grid layout configured in a section rule, clicking the Filter option and entering a comma separated value in the "To" field in a decimal-type column resulted in an "Invalid numeric range" option message. No error was seen if comma separated values were entered in both the "To" and "From" fields. Because the checkRangeFilter() function in ui_grid.js uses parseFloat() API to extract the decimal content entered in the search boxes, decimals after commas are ignored and validation failed due to the fields not matching. This issue has been fixed by implicitly removing any commas entered by the user.
INC-131151 · Issue 572831
Resolved empty body for Reject email
Resolved in Pega Version 8.2.8
When using the pzEmailActions Section in Correspondence for Approve/ Reject functionality via email, there was no reply body in the email for Reject Option. This was due to the flow action for the Reject email being different than that of the Approve email, and has been resolved.
INC-131385 · Issue 573453
Swagger APIs updated
Resolved in Pega Version 8.2.8
The Swagger File APIs have been updated to ensure swagger document files generated meet specifications for editor.swagger.io .
INC-134370 · Issue 577633
Expanded Grid locking updated
Resolved in Pega Version 8.2.8
When using pyDashboadMyWorkList to show the cases of an operator with Master Detail in Read Only mode, the system was acquiring a lock on the expanded work object. To resolve this, the following changes have been made: - In activity Assign-pyAcquireObject, If the parameter bRODetails is true, do not call acquireWorkObject and do obj-open-by-Handle to get assignment and work page in pyAcquireObject activity. - In activity acquireWorkObject, the parameter skipWorkLock has been removed as acquireWorkObject should always acquire the lock.
INC-134557 · Issue 585646
Dropdown populated with parametrized data page source
Resolved in Pega Version 8.2.8
When configuring dropdowns or autocomplete controls with parametrized data page as a source in a section, the parameter configuration values and parameter names were not sent in the JSON created by the DX API view. This has been resolved by adding parameter support for DataPages in Dropdown, Autocomplete, and Radio buttons.
INC-134709 · Issue 579436
Updated endpoint Cross-site scripting protection
Resolved in Pega Version 8.2.8
Cross-site scripting security has been updated for Endpoints in Display activities.
INC-135161 · Issue 580934
Upload with "Select File" works in Microsoft Internet Explorer
Resolved in Pega Version 8.2.8
When using Microsoft Internet Explorer, uploading a document was failing on the first try when using the "Select File" button. The second attempt worked as expected. This was an intended consequence of work done to enable attaching the same file after deleting it, and was related to Microsoft Internet Explorer calling an "onChange" which caused the "pzAttachFileDDFileList" section which is used to display the attachments uploaded to not be properly refreshed. This has been resolved by updating the pzMultiFilePath control handling of the success and failure of the upload function call.
INC-136383 · Issue 584518
Delegated SLA rule allows "Notify party"
Resolved in Pega Version 8.2.8
When modifying an SLA that had been delegated to an access group, setting the perform action to "Notify Party" did not present an option to select a user to notify. Attempting to submit the change resulted in the error "pzGoalCorrName—Value cannot be blank" and the rule was not saved. This was a missed use case with the delegation of SLA when notify party was used. and has been resolved.