SR-C49342 · Issue 400585
Check added to resolve teradata empty batch error
Resolved in Pega Version 8.2
ExecuteBatch in Teradata was failing if there were no calls to addBatch prior to it, a different behavior than is seen in other databases. This has been corrected by adding a condition to check if there are any statements added to the batch before executing the batch.
SR-C78179 · Issue 417562
Helper text/tooltip field returned to the view API
Resolved in Pega Version 8.2
Previously, the helper text, format type and Read/Write classes were not passed to the view API. Because these fields are needed to understand correctly what type of field to render and execute basic input validations at the front end side, the helper text value will now be provided as a tooltip.
SR-C78227 · Issue 418102
pxCheckbox label returned from the User Experience API
Resolved in Pega Version 8.2
While calling the API to get the view of the screen as a JSON format, pxchecbox type of controls were not returning the label of the field. This has been fixed with the addition of a checkbox to the list of labels from modes.
SR-C74176 · Issue 419496
AdminUser login corrected for WebLogic
Resolved in Pega Version 8.2
After a successful deployment of Pega on WebLogic 12c Application Server, the server started up without problem and the login page appeared as expected. When attempting to login to the application using the administrator account, the login failed and displayed the error "java.lang.IllegalArgumentException: Header:Location Cannot contain CRLF Charcter" in the browser. This as traced to the URL not being generated correctly due to the padding in the encoding rejecting any CRLF character in the URL, and has been corrected.
SR-C76155 · Issue 415814
Class structure tree correctly repaints when scrolling in Chrome
Resolved in Pega Version 8.2
When expanding the Class Tree Structure and then selecting a class relatively low down in the list, the screen was not repainted after scrolling back up when using the Chrome browser. It was possible to force a repaint of the tree structure by clicking on an item in it. This was traced to the app explorer tree-grid (cell) having section includes which used deprecated free-form layouts (which are table based). To resolve this issue, the app explorer leaf node has been converted to display in dynamic layout and app explorer child nodes will repaint even after expanding to a child level.
SR-C78857 · Issue 416253
Hover text no longer blocks agent selection
Resolved in Pega Version 8.2
Show smartinfo was rendering the information on top of the target dynamic layout, hiding the entire content of the layout. To fix this issue, Show SmartInfo has been reconfigured as on hover of node label instead of dynamic layout.
SR-C77533 · Issue 416617
Added null check for ApprovalFlowName in pre-processing activity of "pzApprovalPreProcessing"
Resolved in Pega Version 8.2
When a "pyApproval" flow action was configured in one of the assignments of a case Type for Approval action by the manager, the error message "The Flow Action pre-processing activity pzApprovalPreProcessing failed: The reference .pxFlow().pyFlowParameters.pyApprovalSectionName is not valid. Reason: Empty subscripts are not valid for the element : pxFlow" appeared when the Approval section was displayed. To correct this, a null check has been added for an empty ApprovalFlowName in step 1's second property set and transition step.
SR-C79762 · Issue 419157
Decision table decision shape produces correct connector
Resolved in Pega Version 8.2
After adding a decision shape and making its type "Decision Table", the connector that was automatically built showed the condition type as "Result", but incorrectly labeled it as a When rule. This was traced to a missed use case in the decision related connectors, and has been corrected.
SR-C77106 · Issue 416869
API modified to prevent potenial security issue with JSON objects
Resolved in Pega Version 8.2
A potential security issue was found where the Pega API allowed a different JSON object to be posted back than had been retrieved. This has been corrected.
SR-C75278 · Issue 415735
Extension added to wrapper activity to allow skipping completed assignments
Resolved in Pega Version 8.2
The withdrawal of the pyPopulateCaseContentsWrapper activity rule from the PegaCardSd ruleset caused the wrapper activity in Pega-EndUserUI to be utilized instead, but that activity included a different behavior which resulted in the Completed Assignments checkbox being set as 'true' during processing instead of staying 'false' unless checked by user. This resulted in additional assignments showing when previously only open assignments would show as default. In order to correct this, a new extension "DT(pyPopulateCaseContentsWrapperExtension)" has been provided to set the required fields in order to skip fetching the completed assignments. To utilize this, set the pyShowCompletedAssignments property to true in the extension DT to hide the assignments.