INC-132590 · Issue 590493
Exported Excel from Decision Table wraps correctly
Resolved in Pega Version 8.6
After upgrade, entries were displayed in a single line on exporting a decision table to Excel despite WrapText cell formatting being set. This was traced to the WrapText cell formatting set under the UpdateGridCells() function being overridden inside an addDataFormat() function callas part of DecisionTableWorkBookConverter.java. This has been resolved by adding the new function "setWorkAreaCellStyles" and calling it after generateWorkbook() function call of super class (AbstractWorkBookConverter.java).
INC-160437 · Issue 629646
Upgrade compatibility enhanced for Pega-ConditionBuilder ruleset
Resolved in Pega Version 8.5.3
In Pega v8.2.5, the Pega-ConditionBuilder ruleset was added as part of the PegaMarketing application. When these enhancements were promoted to a platform ruleset beginning with Pega v8.4, the function names were modified with PZ/PX prefixes due to the corresponding validation standards in place for rules created in platform rulesets. Unfortunately, this introduced an upgrade impact. Due to the function name change, strategies failed when attempting to evaluate the functions configured in the filter component. Eg: @string.ContainsIgnoreCase function is part of the Pega-ConditionBuilder ruleset, which was not available. To resolve this, the following function aliases have been created in this release:ContainsIgnoreCase StartsWithIgnoreCase EndsWithIgnoreCase CompareDateTimeToSymbolicDate
INC-225247 · Issue 729607
SessionTimer correctly working in Mashup
Resolved in Pega Version 8.8
When using the pxSessionTimer in the mashup at section pxCaseActionArea, the timer pop up did not appear. Investigation showed the pxSessionTimer control was not correctly triggering in mashup. This has been resolved by updating the pega.desktop.support.restartTimeoutWarningTimer and closeAllPRPCChildWindows functions and adding the new functionality logOff() which uses the control_actions_logoff functionality.
SR-129171 · Issue 195047
Corrected error in order of operations for Numeral builder
Resolved in Pega Version 7.1.8
The Add function in reporting was not returning the proper result when included in an equation with multiple order of operations. This was an error in the Numeral function builder, and has been corrected.
SR-B35741 · Issue 292129
Corrected thread contention in BAC
Resolved in Pega Version 7.3
A thread contention condition was found in BAC due to the use of maccesscache. That function and the matching clearAccessCache() function are no longer used in Basic ApplicationContext and BasicApplicationContextImmutableimpl to resolve the issue.
SR-A7951 · Issue 218577
Sort filtering updated for Repeat Grid using RD as source
Resolved in Pega Version 7.2
Using the Sort functionality as a filter was not working in a Repeat Grid where records were fetched using a Report Definition. This was due to the property passed to the RD function not being populated while generating unique values in the filters, and parameter values have now been added to the visible list if the column name is a function in pzGetGridColUniqueValues activity.
SR-A98103 · Issue 266253
Scheduled recurring Purge/Archive set to reuse specified start time
Resolved in Pega Version 7.2.2
When scheduled to run every day at a particular time, the Purge/Archive function started later each time. This was due to the function using the Agent running time for the rescheduling, starting the next day at the time it ended. The function has now been modified to use the customer-specified start time instead of calculating the Agent time.
SR-B42262 · Issue 303693
Field Values displayed correctly in mobile dynamic layouts
Resolved in Pega Version 7.3
Dynamic layout headers that reference Field Values were not displayed correctly in the mobile application. This was caused by the getLocalizedValueFromList function not passing activeContext to the resolveParams function, and has been fixed.
INC-132169 · Issue 584760
NativeSQL will use inline rule resolution for core components
Resolved in Pega Version 8.6
After upgrade, nodes were going down with a heartbeat error. This was traced to issues with NativeSQL taking a very long time to generate queries due to the overhead in calling multiple complex functions to resolve rules. To correct this, updates have been made to resolve the standard set of functions used by core components inline in NativeSQL function resolution.
INC-132169 · Issue 584759
NativeSQL will use inline rule resolution for core components
Resolved in Pega Version 8.5.1
After upgrade, nodes were going down with a heartbeat error. This was traced to issues with NativeSQL taking a very long time to generate queries due to the overhead in calling multiple complex functions to resolve rules. To correct this, updates have been made to resolve the standard set of functions used by core components inline in NativeSQL function resolution.