SR-C91927 · Issue 431509
ValidateSurveyStream updated to ensure validation runs on a named page
Resolved in Pega Version 8.2.2
After creating new survey rules, trying to re-validate and save in survey-specific rules was failing to re-validate in standard/personal edition. This was an issue with the ValidateSurveyStream activity running on an unnamed page: in this activity, the stepPage name is set to a parameter and passed to datatransform for the processing of the rule. Since the steppage was unnamed, an exception was thrown. To resolve this, steps have been added in the ValidateSurveyStream activities for question, question group, and survey that will copy the primary page into the named page and pass it as a parameter.
SR-C90467 · Issue 429608
Validations are correctly run on rescheduled reports
Resolved in Pega Version 8.2.2
When using the OOTB schedule report functionality, UI validations were bypassed if the existing schedule was deleted and the report was rescheduled. This has been corrected by updating the Review harness to display the Perform harness when clicking Update.
SR-C86952 · Issue 428815
Viewing screen capture attchments no longer requires Microsoft Internet Explorer/Silverlight
Resolved in Pega Version 8.2.2
Previous versions of the Pega Platform required the use of the Microsoft Internet Explorer browser with Silverlight to access old attachments added using the screen capture feature. In order to support multibrowser compatibility, the system has been updated to use javascript functions to display these images so IE/Silverlight are not required.
SR-C89969 · Issue 431207
Webchat error fixed for Operator Template with User access role
Resolved in Pega Version 8.2.2
While running Webchat in an external application where the interface had any operator selected as an "Operator Template" with a User access role, the error "The chatbot is experiencing problems; If the issue is related to your current case, you can withdraw it by typing cancel" appeared. This was traced to an issue with creating/modifying instances of the class Data-NLP-Report-Summary, which is done in the Interaction API via pxSaveNLPSummary. To resolve this, the class has been added to the PegaRULES:User4 role so that any user access group can have write access to this class.