INC-176542 · Issue 668477
Removed unused function to improve Class rule save performance
Resolved in Pega Version 8.6.2
Clicking save on the Policy Class rule was not working correctly or was taking an excessive amount of time to respond. Adding property mapping in the External Mapping tab of the Class rule exhibited the same behavior. Investigation showed there was an infinite loop being invoked in the class ruleform, which was traced to the disableKeyEntries() function. As this function is no longer used, this has been resolved by updating the RF_RuleObjClassScript.js to remove disableKeyEntries and any function calls to it.
INC-179111 · Issue 666017
Toolbar delete handling modified
Resolved in Pega Version 8.6.2
After upgrade from Pega 7.4 to 8.5, the toolbar delete button behavior was different. Previously, the pzRuleFormToolbarDeleteRule section rule invoked RuleFormMain on refresh, but the updated version was calling RuleFormHeader, preventing the deletion of the assignment from the class instance. This was an unanticipated edge case and has been resolved by updating the action in the button to refresh the section RuleformMain instead of header.
INC-180468 · Issue 659923
JAWS correctly reads work group header
Resolved in Pega Version 8.6.2
While creating the groups within the organizational unit, JAWS was reading the name of the frame as "Process Work Area" instead of "Create Work Group" and "enter data" instead of the name of the edit field with edit instructions. This has been resolved by adding a property to the short description label so it contains the instance type that is being created.
INC-182150 · Issue 669852
DSS added to control Pega Version Banner
Resolved in Pega Version 8.6.2
Nuisance errors were being logged related to the application trying to connect to Pega to confirm available versions. This has been resolved by adding the 'when' rule pyShowVersionBanner to pzStudioHomeWrapper which allows disabling/enabling the Version Banner based on the setting used in the DSS ShowVersionBanner. pyShowVersionBanner defaults to true when DSS ShowVersionBanner does not exist.
INC-168290 · Issue 663427
Signature Accept callback fires correctly in offline app
Resolved in Pega Version 8.6.2
Clicking on the Accept button in the Pega mobile signature control was not properly calling the necessary pega.ui.signature.acceptSignatureCallback method. This has been resolved by adding code for the Post Success and Failure callback on Signature accept in the offline app.
INC-171951 · Issue 667123
Signature Accept callback fires correctly in offline app
Resolved in Pega Version 8.6.2
Clicking on the Accept button in the Pega mobile signature control was not properly calling the necessary pega.ui.signature.acceptSignatureCallback method. This has been resolved by adding code for the Post Success and Failure callback on Signature accept in the offline app.
INC-172315 · Issue 664628
Resolved intermittent attachment save error
Resolved in Pega Version 8.6.2
A Flow Action error was intermittently being displayed when saving attachments. This was traced to the activity pzUploadAttachmentToDocument-->Step 25 which uses the step page CallExtensionAct which can cause a page null exception if it is not initialized, and has been resolved by adding a Page-New step to initialize the page.
INC-179175 · Issue 664046
Mobile barcode scan sets value with correct context
Resolved in Pega Version 8.6.2
After implementing a list of items where each has a unique barcode, scanning the barcodes using the mobile app worked correctly the first time but subsequent scans were setting the value on the first element of the list and missing the context of the current scan position. This has been resolved with an update to ensure the scan barcode action sets the value on the correct property when using repeating dynamic layers.
INC-181126 · Issue 663306
Signature Accept callback fires correctly in offline app
Resolved in Pega Version 8.6.2
Clicking on the Accept button in the Pega mobile signature control was not properly calling the necessary pega.ui.signature.acceptSignatureCallback method. This has been resolved by adding code for the Post Success and Failure callback on Signature accept in the offline app.
INC-183559 · Issue 664813
Handling added to process Actions chunks on multiple nodes
Resolved in Pega Version 8.6.2
If the synching of chunks to a node was interrupted, attempting to resume the remaining chunks resulted in a processing issue if the Load Balancer passed the connection to a different node than was used for the first connection. As an example, if chunks were synched to node "A" and the restarted sync saved the remaining chunks to node "B", when all chunks were synced node "B" incorrectly determined node "A" was actually doing the work and skipped the processing of the chunks on node "B". This resulted in queued chunks being left untouched. To resolve this, the logic has been updated to allow multiple nodes to process the chunks.