SR-D15469 · Issue 487523
Export to Excel formats the DateTime filter for localized values
Resolved in Pega Version 8.3
When exporting to Excel, filter criteria were given in GMT rather than the localized timezone. This was caused by the implementation of localizeDateTimeString method not formatting the output string for the locale/timezone during export to Excel, and has been corrected to display the localized filter values when the filter values include DateTimes.
SR-D17037 · Issue 487531
Check added for backwards compatibility with Case Type when rules
Resolved in Pega Version 8.3
After upgrade, the When rules present on case type rules (used for skipping stages or showing/hiding stage-wide or case-wide actions) were not executing at run time. This was traced to the introduction of the pySkipOrAllowType property in recent versions, and was only reproducible when the ApplicationRuleset was locked and after upgrade irrespective of whether the condition for when was true or false. To resolve this and enhance backwards capability, a check has been added for the SkipOrAllowType property being empty.
SR-D17122 · Issue 487599
Updated code to resolve PMS variable errors when using the iframe container
Resolved in Pega Version 8.3
After building the iOS application using “Reuse web portal” (under channels & interfaces > layout) and with the default settings application, the Dashboard, My Work, and Pulse sections were not rendered and the error "Can't find variable pms" appeared. This happened only when the iframe container was used, as the pms object (PIMC API) is always injected into top window and does not exists in child windows like iframe embedded in a page. In order to ensure that undefined variable pms does not break the rendering, the code has been updated to use top.pms for all pms occurrences to avoid errors when API is invoked from iframe.
SR-D18690 · Issue 487616
Duplicate check repaired
Resolved in Pega Version 8.3
A case created with one of the "must match" values as blank was not being treated as a duplicate case. This was traced to a check inserted in an earlier release as part of work done to handle a null FirstName value in the 'Case Match' decision rule, and has been resolved by reworking the original solution and including the 'is same' usecase.
SR-D15216 · Issue 487679
Email parameter handling updated for greater backwards compatibility
Resolved in Pega Version 8.3
After a major migration, email failures were seen with the message "Error sending email: To Address not available". This was traced to a difference in handling between the old and new system versions for fetching the details of workparty for the ToParty parameter, and has been resolved by modifying the newer Work-.pzGetEmailFromParty and Work-.pzSendEmail activities to handle party role as well for greater backwards compatibility.
SR-D14005 · Issue 487791
Bteer filtering added for Duplicate schema names in schema tools
Resolved in Pega Version 8.3
The database list drop down was showing duplicate database names. This was traced to Connection Manager managing Data Base configuration differently for corresponding Read Only, Admin and Standard, and not providing the unique database names. This has been resolved by adding support for filtering duplicate names from getDatabaseNames.
SR-D19356 · Issue 487860
Resolved issue for email attachments with '%' in the filename
Resolved in Pega Version 8.3
Send email notification was not able to send mail with uploaded attachments that contained the '%' character in the file name. Without the character '%' the image was uploaded and included without issues. This was traced to the '%' character being encoded twice in the handling, and has been resolved.
SR-D15425 · Issue 487886
Removed extra space from feld value in Audit History
Resolved in Pega Version 8.3
A space was seen for a Field value that was referenced in the instructions Audit History. This was traced to the control adding an extra space if any gaps were present in the code, and has been resolved.
SR-C95250 · Issue 487995
Null check added to resolve non-impacting InvalidParameter exception
Resolved in Pega Version 8.3
Creating a child case from the SLA goal activity using the 'AddCovered' activity generated the message "Exception in queue item: cannot be null or blank". The error "com.pega.pegarules.pub.clipboard.InvalidParameterException: cannot be null or blank" was also seen. However, no functionality impact was observed. This has been resolved by adding a null check to the getPortalName method, and modifying the HarnessUIBuilder.java file to add safe checks for whether 'portalName' is empty or not.
SR-D8390 · Issue 488002
Handling added for runtime exception on upgrade due to inaccessible external schema mapping
Resolved in Pega Version 8.3
If a system used external schema mapping, attempts to upgrade were failing with the error "Caused by: com.pega.pegarules.pub.database.ConfigurationException: Unable to obtain data source "java:comp/env/jdbc/PegaRULES", as it is undefined". This was traced to configuring external DADNs which were not accessible from the server where the upgrade was being run: an upgrade will fail if it cannot connect to an external datasource even if no changes need to be made to that datasource. However, because a PRRuntimeException was unexpectedly being thrown instead of a Database Exception, the exception was not properly caught and handled. This has been corrected.