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.
INC-138348 · Issue 599771
Added parameter skipPropertyEvaluation to handle CSS in email HTML
Resolved in Pega Version 8.2.8
While sending an email with custom HTML appended to the email body, a "+" sign in the body was causing the correspondence generation to fail. Investigation showed that if there were CSS classes with braces in the message body, the braces were being removed and replaced via "+" symbol in step 21 of CorrCreate activity. To resolve this, a new Boolean parameter skipPropertyEvaluation has been added in the CorrCreate activity to handle the decision to either evaluate the logic or not, and the pre-requisite will be to resolve all the property references before calling this activity so custom CSS braces { } will be honored when the message body is sent.
INC-141751 · Issue 596137
DragAndDrop attaching large file properly disables 'X'
Resolved in Pega Version 8.2.8
When a large file was attached using the DragAndDrop feature, the 'X' icon/button was not disabled. This made it possible to click 'X' and perform other actions during the upload, which caused the screen to freeze and required a browser refresh to continue the work. This was traced to incomplete work done on large file uploads, and has been resolved by ensuring the busy Indicator shown will be applied to the complete screen to avoid any other actions being performed.
INC-142667 · Issue 595125
Updated file attachment name limit error handling
Resolved in Pega Version 8.2.8
When attaching a file with a name more than 59 characters long, a warning was displayed stating the character limit of 59 but submitting the file did not throw an error. This was traced to error messages not being set on the primary page where the flow action was launched, allowing the modal to be submitted even though it has errors. This has been corrected.