SR-C81653 · Issue 428450
Calling flow correctly resumed after sub-process completes
Resolved in Pega Version 8.3
If a case was processed via Operator1 and passed as an assignment to a workbasket where Operator2 picked it up and performed a Reject case on it, the process in Flow1 correctly called Flow2, but once Flow2 was processed Flow1 was not resumed. If Operator2 only performed the Reject processing, Flow1 was resumed. To to ensure the correct flow resumption, the location of the pyFirstRun setting in flowMethodBody FUA has been updated.
SR-C84939 · Issue 428565
setTenantName API exposed in the rules alyer
Resolved in Pega Version 8.3
In order to support more efficient message ingestion in a multi-tenant environment, the setTenantName API has been exposed in the rules layer.
SR-C87986 · Issue 428572
Resize handle correctly changed for RTL locale
Resolved in Pega Version 8.3
When the locale was set to RTL, dragging sections to the left caused a resize and dragging sections to the right moved them to the left. This has been resolved by ensuring the resizable handle for workarea is correctly changed when the locale is RTL.
SR-C89675 · Issue 428597
Case name caption security inserted
Resolved in Pega Version 8.3
In order to protect against the possibility of executing malicious JavaScript code by entering an appropriately modified name while adding new case type, pyCaption in menu items has been made HTMLSafe by converting JSON through the GSON library. Additional handling for Firefox has also been added to normalize tabName to properly display Recents.
SR-C91521 · Issue 428628
DX API updated for improved security
Resolved in Pega Version 8.3
Modifications have been made to the DX API to improve system security.
SR-C88236 · Issue 428787
Debug logging added to HTTP API for improved diagnostics
Resolved in Pega Version 8.3
Debug loggers have been added to the HTTP API to provide more complete diagnostics for an error where users are redirected to login screen after providing valid credentials. As a workaround, restarting the node server will resolve the login issue.
SR-C86952 · Issue 428816
Viewing screen capture attchments no longer requires Microsoft Internet Explorer/Silverlight
Resolved in Pega Version 8.3
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-C74784 · Issue 428819
Added file truncation to HCClient.txt to ensure data integrity
Resolved in Pega Version 8.3
When a work object model contained more than two embedded lists, simple save corrupted the JSON in the local storage work object browser. Investigation traced the issue to using the same file without truncating its content. Because the HCClient.txt file in Rule: webwb - pzpega_mobile_settings - js was reused while displaying items in DocumentViewer, writing a smaller amount of data into it than the previous write left orphaned content in the file that corrupted the new data. To resolve this, the file content will be truncated before writing new data into it.
SR-C81077 · Issue 428868
Support added for using OpenMobile app as a Navigation action
Resolved in Pega Version 8.3
After adding a menu item to the pyCaseWorkerNavigation navigation rule that was configured to use the open mobile app action with a mobile app ID of opensignal, the menu item was displayed in the mobile app but clicking on it did nothing for the user and the JavaScript console logged the error "Cannot open mobile app without scheme". The same action worked as expected when called from a button. This was traced to the "OpenMobileApp" action not containing support for being used as Navigation action, and the necessary code for that use has now been added.
SR-C91501 · Issue 428972
Support added for base64Binary type in the SOAP envelope
Resolved in Pega Version 8.3
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.