SR-D23723 · Issue 503088
pxGenerateExcelFile updated for handling blank dates
Resolved in Pega Version 8.2.4
When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format.
SR-D42670 · Issue 510183
Force order added to inner join when running a Rules Resolution filter
Resolved in Pega Version 8.2.4
After upgrade, D_getResolvedWorkStatuses was not loading properly due to a Report Definition that used a Filter by Rule Resolution option timing out on the SQL Server. When the Filter by Rule Resolution option is selected in Report Definition, it will generate a rule resolution query with an inner join which can cause a time out on the SQL Server while it tries to find out the join order for tables with multiple joins. To resolve this, the SQL server will provide a Force order, merge inner join hint option by way of an added DSS reporting/useForceOrderHint. Additionally, reporting/useMergeHintForRRquery should be set on Pega-Reporting to set things up for using the Merge Inner join hint in the query.
SR-D32035 · Issue 504705
Save Button for Delegated rules is displayed correctly
Resolved in Pega Version 8.2.4
The save button for delegated rules was displayed in a truncated shape. This has been corrected by removing the split-left style from all of the buttons that are intended to be standalone and not have a drop-down actions menu.
SR-D35734 · Issue 504478
Escalation updated to ensure assignee is notified of missed deadline
Resolved in Pega Version 8.2.4
The Passed Deadline SLA Actions to send email to the owner were not triggered as configured in SLA rule form. To correct that, pzMapEasyEscalationParams steps 3.4.10 and 3.4.11 have been modified to support "NotifyAssignee" for the passed deadline.
SR-D4559 · Issue 486555
Normalized type attribute namespace for Weblogic compatibility
Resolved in Pega Version 8.2.4
After upgrading from Weblogic 12.1.3.0 to Weblogic 12.2.1.3, the namespace in the generated Request XML for some elements was appearing as null/blank. This has been resolved by normalizing the type attribute namespaces' option in Connect-SOAP.
INC-
184212 · Issue 677287
Updated AgentName handling for QueueItemID
Resolved in Pega Version 8.7.1
A report was showing as scheduled but no mail was received when it was supposed to run. Investigation showed this was due to the reports being corrupted, leading to the flow skipping the necessary Queue-For-Agent method. While there was a workaround of doing a "Save As" to create a new version of the report, this has been addressed by setting the agentName before saving to the database to handle missing agentName cases and ensure pyAgentname is always populated when pzQueueItemID is not empty.
INC-172836 · Issue 655462
Added check for attachment upload for filename ending in $
Resolved in Pega Version 8.7.1
Attempting to upload a file to external web storage was failing if the filename's last character was $. This was traced to the system attempting to decode the name, and has been resolved by adding a check to see if there are at least two characters after $. If there are none, the decode step will be skipped.
INC-198029 · Issue 695562
Check added for empty SendAs in MSGraph
Resolved in Pega Version 8.7.1
When using MSGraph, logging showed the errors "Could not parse the address into InternetAddress Objects, falling back to parse with the regex" and "Unable to use the configured "Send As" email address from Records. Will fall back to 'first' recipient of incoming email." This has been resolved by adding a check for a blank SendAs field.
INC-199320 · Issue 696941
Corrected duplicate record error message
Resolved in Pega Version 8.7.1
When inserting a duplicate record in a grid, the error was shown at the harness level instead of the record level. This was traced to the error messages being removed from the step page, and has been resolved by updating the system so messages will not be cleared if the same value is being set.
INC-199341 · Issue 694712
Content-type values made consistent
Resolved in Pega Version 8.7.1
The content-type for service APIs was returned as 'text' for 401 errors when using a custom authentication type instead of the parent-type/child-type format such as text/plain, text/html, application/json, etc. This has been corrected.