SR-D32655 · Issue 510343
Enhancement added to hold Change Tracker values until UI is loaded
Resolved in Pega Version 8.3.1
Sporadically, an agent attempting to answer a queued call within 10 seconds received a loading screen. By the time the load completed, the next agent had already taken the call. This is a scenario where based on a change, the agent was trying to refresh something on the UI (a section or harness) which was not yet loaded/present on the UI. To address this use case, an enhancement has been added to hold the change tracked values and handle them once the UI is loaded. The new function pega.ui.ChangeTracker.prototype.handlePendingCTChanges in pzpega_ui_changetracker.js is used to handle the pending CT changes. A hook has been added in the pzpega_ui_doc_lifecycle js file to invoke the above function once the UI is loaded.
SR-D35266 · Issue 509480
Check added to postOpenAssignment to support Ajax Container use
Resolved in Pega Version 8.3.1
After configuring an 'OpenAssignment' action on a begin button and giving the target as 'Dynamic Container', it worked as expected to open the assignment in a new tab on the Platform, but did not work from the Customer Service interaction portal. This was traced to the Customer Service portal using MicroDC to display the cases in the work area, which was not within the scope of the Ajax Container. Additional checks have now been added to the postOpenAssignment function to support this use.
SR-D35268 · Issue 506684
Max results limit increased for open-rule-advanced query
Resolved in Pega Version 8.3.1
An issue with the results list of a class instance query being clipped in the autocomplete drop down was traced to an old limit that was put on to restrict the number of results shown in open-rule-advanced. This limit has now been increased in the open-rule-advanced control.
SR-D40762 · Issue 510368
ReloadSection passes event object explicitly
Resolved in Pega Version 8.3.1
After upgrade, 'replace current-model' was not working when used in a section with a link control that had an onClick event that was intended to launch a local action. Investigation showed that the link control was not working in the latest Google Chrome version, and this has been corrected by passing the event object explicitly to the reloadSection function in PZPEGA_UI_DOC_SUBMIT.js
SR-D41984 · Issue 510011
Added handling to correct '&' displayed as '&' in custom tab name
Resolved in Pega Version 8.3.1
When using a data transform and custom properties to set the tab title, clicking on a link containing "&" in the label opened a tab name which included "&" instead of "&". This has been resolved by modifying the handleGadgetLoad method in the pzpega_ui_dynamiccontainer file to handle the Cross Scripting FIlter and display the character.
SR-D42701 · Issue 510921
Cross-site scripting security added for Case Manager
Resolved in Pega Version 8.3.1
Cross-site scripting security has been added to the Document features in the Case Manager portal.
SR-D48887 · Issue 512944
Read-only text inputs remain read-only after browser refresh
Resolved in Pega Version 8.3.1
Read-only text inputs were changing to editable after a browser refresh. This was traced to work done to better handle a displayOnPage GET request that was sent with all of the parameters in the parameter page (data-model) that was causing a 400 Bad Request due to the browser URL length limitations. That issue was resolved by removing the parameters which are not actually required for the displayOnPage GET call during the refresh case; to resolve this issue, the readonly parameter for displayOnpage action has been restored and will be passed.
SR-D43141 · Issue 512433
Support added for iFrame Mashup resize when using SPA
Resolved in Pega Version 8.3.1
After upgrade, issues were seen with an iFrame holding a Mashup not resizing as expected. This was traced to the use of an SPA portal inside mashup, and has been resolved by explicitly invoking the doharnessResize API to set proper height on iframe when using SPA.
SR-D43468 · Issue 511642
Includes() function changed for Microsoft Internet Explorer compatiblity
Resolved in Pega Version 8.3.1
The complete screen was not loading due to "includes()" not being supported in Microsoft Internet Explorer , resulting in a console error and the flow breaking. To resolve this, ".includes()" has been changed to indeOf.
SR-D44546 · Issue 512598
Corrected opening collapsible rows with modal action inside a nested pane grid
Resolved in Pega Version 8.3.1
After expanding the second level of a collapsible row in a table and then collapsing the row back down again, trying to expand other rows in the table did not work and the error "Unable to get property 'target' of undefined or null reference" appeared on the console. This was an issue with a modal action configured inside a nested pane grid that was attempting to call a target key on an undefined object, and has been resolved by explicitly checking for the existence of the 'event' object before calling the 'target' key on it.