INC-218463 · Issue 726502
Common TransformerFactory method added for greater compatibility
Resolved in Pega Version 8.8
In Service-SOAP, mapping request headers and parameters to the clipboard (instead of mapping to a Parse XML rule) resulted in blank values on the primary page of the service activity when using the IBM WebSphere Liberty app server. In this case, instantiating the JAXP TransformerFactory object using the com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl parameter resulted in a transformer that serialized the XML to an empty string instead of the correct XML. To resolve this, an update has been made to make a common TransformerFactory method to ensure IBM JDK in WAS deployments function as expected.
INC-207210 · Issue 704137
Empty check added to OpenRuleAdvanced
Resolved in Pega Version 8.8
A blank screen was displayed when attempting to open a requirement set rule in Dev Studio. This was a missed use case while updating the OpenRuleAdvanced control to handle BAC compatibility, and has been resolved by adding an empty check in addition to the existing null check along with an 'if' condition to check for pyActivity input.
INC-227714 · Issue 730395
Empty check added to OpenRuleAdvanced
Resolved in Pega Version 8.8
A blank screen was displayed when attempting to open a requirement set rule in Dev Studio. This was a missed use case while updating the OpenRuleAdvanced control to handle BAC compatibility, and has been resolved by adding an empty check in addition to the existing null check along with an 'if' condition to check for pyActivity input.
INC-213308 · Issue 712076
Fallback added for missing fileName in MultipartHTTPResponse
Resolved in Pega Version 8.8
Given a multipart/form-data response with multiple attachments, when there was no explicit fileName header provided for a body part, the engine skipped processing the part and no data was present on pyRequestAttachmentPage. This has been resolved by adding a fallback in HTTPClientUtils#handleMultipartHTTPResponse() so that if no fileName is present, the 'name' parameter of the Content-Disposition header field will be used.
SR-C65239 · Issue 411325
Check added to resolve nested grid component mismatch
Resolved in Pega Version 8.2
When using a nested repeating grid with expand pane option and expand multiple row options, running a screen flow resulted in a component mismatch error when moving from one assignment to another. This was traced to a limitation in the implementation that sometimes caused the parameter of the outer and inner grid to become corrupted or affect the wrong grid. In this case, the paramters startIndex and recordsInCurrentPage were resulting in a numberformatexception which in turn caused the component stack mismatch error. To fix the issue, an empty check has been added for startIndex and recordsInCurrentPage in the grid generation code.
INC-227819 · Issue 735349
Improved browser compatibility for ContentDisposition header
Resolved in Pega Version 8.8
When files were downloaded from a Sharepoint repository by clicking on the link, the filename was appended by a unique case instance ID or a sequence number to avoid duplicates. This caused a workflow disruption due to the reupload considering the file to be new rather than updated. This was traced to an issue with the usage of the ContentDisposition header which should have set the default file name: as created, the method was not compatible with Google Chrome on Microsoft Windows and was ignored. This has been corrected by updating the ContentDisposition header to set the default file name correctly when using supported browsers.
INC-228060 · Issue 741140
Added control for displaying Ajax popup alert for optimized iOS table
Resolved in Pega Version 8.8
When using an application on iOS with a section that contained at least 3 tables with 'optimize code allow' set to true, refreshing caused the error "AJAX request failed. Reason: communication failure" to be displayed. When a refresh is triggered, ongoing AJAX requests are cancelled, and the WebKit (OS provided) behavior is to display the "AJAX request failed" alert. To control this behavior, a check has been added for the flag pega.u.d.showAjaxFailureMessageMobile when displaying the alert popup. The default behavior is set to false and will not show the alert. To display the alert, set pega.u.d.showAjaxFailureMessageMobile = true in userworkform. The additional fieldValue "AJAX request failed" of type pyMessageLabel is created to allow configuring a custom message.
SR-C67870 · Issue 407162
Added evaluation client thread name check to Change Tracker
Resolved in Pega Version 8.2
The Change Tracker was intermittently not working as expected between main DC and micro DC div when trying to use a change in microdc context (specifically an update to D_Interaction.InteractionHeaderRefreshDateTime) to refresh the document in the main DC. In order to ensure consistent updating, a check has been added for the current thread name while executing evaluate client conditions.
SR-D61560 · Issue 539472
Support added for multiselect control with SmartTip for iPad
Resolved in Pega Version 8.1.8
When using a multiselect list control to a lproperty with Smart Tip configured, choosing one item on an iPad and then trying to tap or drag down the vertical scrollbar caused all listed items to disappear. To resolve this, the multiselect control has been updated to handle the popover exit on smart popover hover along with arrow key navigation support for tablets.
INC-220137 · Issue 721896
UpdateDateTime casing corrected in filters
Resolved in Pega Version 8.8
When using Job Scheduler with MS/SQL, the error "Cannot find either column 'mktdata' or the user-defined function or aggregate 'mktdata.pr_read_from_stream', or the name is ambiguous." This was traced to a casing issue and has been resolved by updating the pxupdatedatetime property to pxUpdateDateTime in Filters F1 and F2.