INC-198555 · Issue 720899
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-225788 · Issue 728057
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-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-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.
SR-C89619 · Issue 429575
Custom section filters retained during refresh
Resolved in Pega Version 8.1.4
Filtered values were not retained on refresh when filtered using a custom section. This has been resolved.
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.
SR-C90467 · Issue 429609
Validations are correctly run on rescheduled reports
Resolved in Pega Version 8.1.4
When using the OOTB schedule report functionality, UI validations were bypassed if the existing schedule was deleted and the report was rescheduled. This has been corrected by updating the Review harness to display the Perform harness when clicking Update.
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.