INC-226764 · Issue 745051
Performance improvements for save-as
Resolved in Pega Version 8.8
Performance issues were seen when using save-as for rules such as Declare expression, When rules, activity, etc. This was traced to a very large number of extra database queries that were being executed while building the Declarative Cache. To resolve this, an update has been made so the queries used for the Declarative Cache will only be executed when required.
INC-157448 · Issue 638923
Latitude and longitude populated for CreateWork history
Resolved in Pega Version 8.6.1
After enabling geo location in the casetype rule, when the case was created using the Create menu option from either Dev studio or Manager portal the Latitude and longitude values were set on the pxRequestor page and were available in the Case Audit history in the Map control. When the same case was created using CreateWork action configured on a button, it did not log the latitude and longitude values in the case Audit history. Investigation showed this was caused by a 'when' condition in the AddWorkHistory activity which checks the requestor page for latitude value and which had a null value when a createWork action was used to create the case. To correct this, the template metadata of the form will be populated with latitude and longitude values from pxRequestor page to be used in the latitude and longitude hidden fields.
INC-167388 · Issue 651306
Values treated as strings for offline data transform concatenate
Resolved in Pega Version 8.6.1
When using a Data Transform to construct a URL using multiple properties that contain values with a leading or trailing "0", the "0" was trimmed when the corresponding mobile JS code was generated using pega.process.expression.getValue("pyWorkPage.PlanData.SegmentID", "pyWorkPage.PlanData") . This was traced to the offline property type assuming that any numbers-only string should be treated as a number, so the data transform concatenate was converting “0001” to 1. To resolve this, the value will be treated as a string when being evaluated in an offline data transform.
INC-215582 · Issue 712287
Cosmos calendar icon handles allow entry set to no
Resolved in Pega Version 8.8
When using the Cosmos theme, the Calendar icon became disrupted when "allow text entry" option was set to "no". This has been resolved.
INC-215046 · Issue 714673
Deleting case in create stage returns user to home/Dashboard
Resolved in Pega Version 8.8
When using a multi-step form in Create Stage, performing a Cancel + Save&Close, then re-opening the case and using a Cancel + Delete, the result of the cancelation is not shown and the user is not returned to the Home/Dashboard screen. This was caused by an issue where the specific AJAX container was not closed, and has been resolved by modifying the pyCaseActionAreaButtons to execute the pyCloseCase local action when clicked to close the case.
INC-196186 · Issue 725413
Check added for repeating dynamic layout submit context
Resolved in Pega Version 8.8
The postprocess of a local action was not executing when the local action was in a table that contained a repeating dynamic layout, and a null pointer exception was generated. Investigation determined that when a repeating dynamic layout was used inside a grid, the submit action on the layout was incorrectly happening in the context of the grid. To resolve this, a check has been added to determine whether the repeating dynamic layout is inside a grid so the correct context is used.
INC-215671 · Issue 719074
Support added for special characters in XML stream rules
Resolved in Pega Version 8.8
When using an XML Stream rule, node values were encoded for a broader set of characters than was required to create properly formed XML. Special characters were converted to ASCII characters when setting the XML to a property with Property-Set-XML. When the mode of the element was changed from Standard to Literal XML, the special character was retained but the element tag itself was missing. This has been resolved by adding a new "XML" encoding format in StreamBuilder. In ResponseTag.appendUnformattedValue(), use the XML mode when resolving to "NORMAL" format and the JSP base class is "Rule-Obj-XML". In StreamBuilderTools, the system will not encode '+' symbols when in XML mode.
INC-212433 · Issue 724512
Clarified SLA calendar error message
Resolved in Pega Version 8.8
If a calculated SLA date is out of calendar end date range, the error "Perhaps the business calendar of year XXXX is missing" is generated. When the provided start date is not the business day and the SLA was calculated by using a custom activity using addTime, isBusinessDay and pxGetSpecifiedTimeOnDate function, this message showed the current year calendar. When checked in the tracer the exception was thrown with the correct year calendar, but when the exception was written as an alert the message was changed and provided the misleading error on the screen. This has been resolved by addressing the misleading error message.
INC-164308 · Issue 634409
UseNoCacheHeaders default expiration set to "0"
Resolved in Pega Version 8.6.1
When the prconfig/HTTP/UseNoCacheHeaders/default was set true it used the value "Expires: Thu, 01 Dec 1994 16:00:00 GMT". This has been updated to the more commonly used setting "0".
INC-172521 · Issue 651552
Email template content visible in user application
Resolved in Pega Version 8.6.1
An issue was seen with email templates functionality where the body content given during the email template creation was not visible when the template was used in the application by an end user. This was a missed use case for recent security updates, and has been resolved.