SR-C71877 · Issue 411406
OperatorSkillCountint calculation corrected
Resolved in Pega Version 8.2
The pxOperatorSkillCountInt in the operator profile was increasing each time GetNextWork was run. This was caused by a calculation error, and has been corrected by resetting .pxOperatorSkillsCount value every time SetWorkInfo is invoked.
SR-C55309 · Issue 393858
OperatorSkillCountint calculation corrected
Resolved in Pega Version 8.2
The pxOperatorSkillCountInt in the operator profile was increasing each time GetNextWork was run. This was caused by a calculation error, and has been corrected by resetting .pxOperatorSkillsCount value every time SetWorkInfo is invoked.
SR-C69948 · Issue 414251
Corrected JSON for eventType DisableOperators in the security event log
Resolved in Pega Version 8.2
An event entry in PegaRULES-SecurityEvent.log was generating invalid JSON. This was traced to eventType DisableOperators (not disable operators) containing a message attribute with unescaped double quote characters surrounding the operator names. This has been fixed.
SR-C75056 · Issue 414109
Corrected JSON for eventType DisableOperators in the security event log
Resolved in Pega Version 8.2
An event entry in PegaRULES-SecurityEvent.log was generating invalid JSON. This was traced to eventType DisableOperators (not disable operators) containing a message attribute with unescaped double quote characters surrounding the operator names. This has been fixed.
SR-C80753 · Issue 419246
Native calendar control works for Firefox on Android
Resolved in Pega Version 8.2
When using Firefox with 'Use native control on mobile' checked, attempting to enter a date into the DateTime field highlighted the mm field but the date selector did not open and keyboard entry was not recognized. This was traced to the native calendar for date time control not opening in Firefox on Android. To correct this, type checks for date, time and datetime-local have been added to the isTextBox function in pzpega_ui_events_infra js.
SR-C62820 · Issue 404256
Fixed dropdown value reset on Microsoft Edge 41 browser
Resolved in Pega Version 8.2
When using the Microso9ft Edge 41 browser, any value selected in a dropdown was getting reset to the placeholder. Also, if there was a dropdown with required validation, then after the selection was made a reset happened and fired a validation message. This was traced to the selectedIndex of dropdown not getting updated properly in Edge if the option was added dynamically with selected attribute, and has been fixed by setting selectedIndex to dropdown in constructOptions function of pzpega_ui_dropdown.js.
SR-C56980 · Issue 399535
Validation corrected to honor Read-Only designations
Resolved in Pega Version 8.2
Validation was happening on Read-Only fields due to pyReadonlyValidation not being honored in all editable cases. This has been corrected.
SR-C66998 · Issue 409280
Thread name implementation fixed for FCM use with micro DC
Resolved in Pega Version 8.2
When attempting to invoke a remote case in the Interaction Manager portal via FCM with the Customer Service for Insurance application which uses micro DC, the case was not invoked and an empty screen was displayed. Invoking the case from the interaction portal resulted in a JavaScript error. Invoking the case from a WSS or directly from the Create button in Designer Studio worked correctly. This was traced to a recent change to the implementation for generating the thread name. Because of this, CRM apps could not load the Federated cases via micro DC. This has been fixed through changes in "pzFCMMashupGadget" to replace the slash with underscore for the FCM thread.
SR-C57545 · Issue 396123
Corrected retrieval of externally-stored PDF attachment
Resolved in Pega Version 8.2
After generating a PDF using the out of the box activities GenerateEForm and AttachEForm, the message "Failed to load PDF document" was displayed with a Reload button when trying to open the attachment. This was traced to an implementation error when CMIS/WebStorage/Repositories was updated that neglected to modify AttachEForm to match extra properties that were added to AttachFile. This caused issues when storing an attachment in an external storage system that was skipped in AttachEForm. To correct this, the Link-Attach file has been modified to properly to indicate where the attachment is being stored when it is stored externally.
SR-C55337 · Issue 402516
Removed duplicated parameter encoding from Create Work action string generation
Resolved in Pega Version 8.2
Multibyte characters such as Japanese or Chinese passed as parameters to the Create Work action of a button were being encoded/decoded twice. This resulted in parameters being incorrectly interpreted in the newly created Work. To correct this, the parameters will not be encoded during the action string generation for Create New Work, and the necessary encoding will be handled only by SafeURL.