SR-126110 · Issue 189593
Adjusted custom header SOAP handling
Resolved in Pega Version 7.1.8
When a Soap connector request has custom headers, the values of the headers were blank; the tags were getting populated but with blank values in-between. This as an issue with the configuration under Rule-Connect-SOAP for the recent enhancement AddCustomHeadersToSoapEnvelope, and has been corrected.
SR-128634 · Issue 195936
Enhanced authentication setting carryover
Resolved in Pega Version 7.1.8
An issue was found with calling out-of-the-box authenticated activities from unauthenticated service activities. For example, when the declare page reload was triggered by a SOAP request (e.g. soap request creates new work which refers to the declare page), the report definition failed with an error saying that the requestor was not authorized to execute pxRetrieveReportData. This happened even though the SOAP Service Package and data page load activity had been set up to not require authentication. This authentication conflict was caused by the rule resolution disregarding the initial setting skipping authentication when it encountered the authentication requirement for the pxRetrieveReportData activity. This has been resolved by setting the authentication requirement to be applied to all rule execution in the same requestor.
INC-141322 · Issue 594513
Resolved drill up doubling the filter box
Resolved in Pega Version 8.3.5
When opening a report with a visual graph, clicking on one of the filtered options, leaving this box open (not submitting it) and then clicking on a bar in the visual graph of the report showed the contents of the graph, but then clicking on the report link to go back to the report overview caused a doubled filter box to be displayed. The report would then have to be reopened before being able to continue. The problem was that the value of .pyUI.pyConfigSecToShow was still set to "filter" after the drill down. When the drill back up happened, the report was trying to show the filter configuration section from before but the context was no longer available and it failed. This has been resolved by adding a call to pzCancelFilterLogicChanges in pzDrillUpReport to set the filters to the previous values and reset the value of pyConfigSecToShow.
SR-124760 · Issue 185307
Corrected timing for change action on autocomplete
Resolved in Pega Version 7.1.8
When a Data Transform was configured on an autocomplete to clear properties, the DT fired on load of the section itself and caused inconsistent behavior depending on timing. This was a case of the generation not honoring the "Run data transform" option available in the section include property panel, and has been corrected.
SR-124760 · Issue 186202
Corrected timing for change action on autocomplete
Resolved in Pega Version 7.1.8
When a Data Transform was configured on an autocomplete to clear properties, the DT fired on load of the section itself and caused inconsistent behavior depending on timing. This was a case of the generation not honoring the "Run data transform" option available in the section include property panel, and has been corrected.
SR-126552 · Issue 190069
Exception handling added for link updates in Upgrade Wizard
Resolved in Pega Version 7.1.8
The error 'Unable to save because null' appeared when the activity linkupdateutility was called during post upgrade. This was an exception caused by a missing '#' sign being sought from the pxLinkedRefFrom property of an element in the page list UseCaseFlowShapeLinks, and the handling for that exception has been added.
SR-129423 · Issue 198808
Updated responsiveness for certain dynamic column widths
Resolved in Pega Version 7.1.8
At run time, the width of a dynamic layout in a section was not changed as per the transformation and responsiveness was not working as expected for specific column widths. This was an issue with Skin CSS generation for dynamic layouts in generating column widths when another format was applied at a breakpoint, and has been resolved.
SR-D95495 · Issue 561465
Revised query to resolve VTable initialization error
Resolved in Pega Version 8.4.2
While running an import in a multi-tenant environment, latency and VTable initialization exceptions were seen. This has been resolved by updating the query with a JOIN clause when the SQL query is being built that will allow the import process to run without causing any issues.
SR-126513 · Issue 192544
Edit in Excel now handles 'HTTPOnly'
Resolved in Pega Version 7.1.8
After implementing 'HTTPOnly', Decision Table Edit in Excel was not working. Attempting to use it caused the system to stall for a few seconds while the label color was orange, and then the text color on the button went back to black but no Excel file popped up. This was found to be caused by the lack of a null check in case of HTTPOnly cookies in the edit_in_excel js function, and this has now been added.
SR-128620 · Issue 193739
MapCases error resolved with blank page check
Resolved in Pega Version 7.1.8
The MapCases function was generating sporadic errors at a Wait Shape or after Updatestatus that required a logout/login before it was possible to proceed with the Case. MapCases runs tools.findPageByHandle(coverinskey) which can lead to an empty page being returned by the engine if one exists, leading to this error; a blank page check has been added that will then use the default work page if the cover key is empty.