SR-C91898 · Issue 435422
Resolved Rich Text Editor display in popup windows
Resolved in Pega Version 8.2.2
The Rich text editor was not displaying in popup windows although it did display otherwise. Investigation traced this to the harness context APIs used in "pega.contro.IRTE.init" (pzpega_control_richtexteditor.js rule) returning rteTextArea as null, leading to the RTE scripts failing to bind the ckeditor dom. This has been fixed by replacing the harness context APIs with ones better suited to this use.
SR-C94950 · Issue 433175
Rule lock is released after alternate approved operator rejects it
Resolved in Pega Version 8.2.2
When using the rule check-in approval process, if a rule check-in candidate was rejected by an approved operator other than the one who checked it in, the lock on the original rule was not released. This has been corrected so the lock is released after the rule is rejected in the case worker portal.
SR-C89716 · Issue 431991
Rule-Connect-SOAP error fixed for WAS/JBOSS environments
Resolved in Pega Version 8.2.2
After upgrade, SOAP webservice was failing with the error “Couldn't create OMElement from string value for the activity InvokeAxis2 in class Rule-Connect-SOAP". This occurred on sites using a WebSphere/JBoss environment, and was traced to an issue where the WAS classloader was loading its default jar at the same time the Pega classloader was loading the same jar into JVM. This has been resolved.
SR-C91750 · Issue 429616
Summarized report after editing shows Count as expected
Resolved in Pega Version 8.2.2
When creating a report with a number of fields and summarizing it in the report browser, the summary gave proper counts. However, after clicking on "edit report" and then running summarize on the same column, the generated report gave the Sum of the number column instead of the Count. To resolve this, the implementation used to update a hidden value for the dropdown has been set to initialize to the Count option.
SR-C91501 · Issue 428971
Support added for base64Binary type in the SOAP envelope
Resolved in Pega Version 8.2.2
In order to support the sending of files more than 10 MB in size as a SOAP attachment, a condition has been added to populate base64Binary type as a multipart message in the SOAP envelope. This allows a text node with binary content to be optimized for xop/MTOM.
SR-C91907 · Issue 433771
Thread context preserved when processing a case in interaction
Resolved in Pega Version 8.2.2
Thread context was not being preserved correctly when a case was opened from an interaction. This has been corrected.
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.