INC-165256 · Issue 657038
Improvements for Offer Eligibility rules loading time
Resolved in Pega Version 8.6.1
After opening the Proposition filter/Action rule and clicking on Add Criteria, the pxAnyPicker drop down load was taking an excessive amount of time. Performance improvements have been made by adding a precondition at step 2 to avoid data page refresh for specific scenarios when it is not required.
INC-175207 · Issue 655555
Added handling for DSM Services stuck in leaving status after database outage
Resolved in Pega Version 8.6.1
During a database outage, the heartbeat would fail and DSM services would eventually try to enter safe mode and stop. As the first step they would try to change the state to LEAVING, but because the database was down saving the LEAVING state failed and the exception was not handled correctly. This resulted in the rest of the stop operation logic not being executed and the service being stuck in LEAVING. To resolve this, an update h as been made to ensure the service goes to LEAVING_FAILED if anything fails during the stop operation including when setting state to LEAVING_FAILED. The state LEAVING_FAILED will get flushed to the database eventually when it comes back up. This will allow the aggregation service to start from the LEAVING_FAILED state and recover by itself after a database outage.
SR-D65112 · Issue 541147
Added support for imported rules to populate bixreportpage
Resolved in Pega Version 8.1.8
Extract rules were not holding the filter criteria after upgrade while performing save-as (for the first time) of the imported rules from the previous version. Criteria were held when the filters were created in the new version. This was caused by BIX extracts created in earlier releases (7.x) not having bixreportpage included. When an environment was upgraded to 8.x versions, opening an extract required the bixreportpage to be populated with Report Definition metadata including the filters defined in the actual extract. Although the filters from the original extract were converted to filters that are acceptable by ReportDefinition, they were not being added to bixreportpage on opening the extract. To resolve this, the system has been updated to copy the filters back to bixreportpage on opening the extract in the upgraded environment.
SR-B36254 · Issue 293924
Removed error appearing on multiple tabs
Resolved in Pega Version 7.3
On a multiple tab scenario when client side validation was triggered on a specific tab ad that layout was under a tabbed repeat in a section, a warning icon appeared on other tabs as well. This is due to marking for tab repeat not being supported at this time: in these conditions, the system will skip the marking error.
SR-B36260 · Issue 296921
Fixed mobile native control submit clearing property/date
Resolved in Pega Version 7.3
When the "native control on mobile" option is checked for a date-time property, a runtime error on submit cleared the property value/date value. To correct this, if the datetime property gets any error messages on submitting the screen, the response of the datetime control will not generate the Value or overwrite it.
SR-B14688 · Issue 289060
Parameter added to consider production rulesets while checking rule resolution
Resolved in Pega Version 7.3
After creating a portal for admin users and adding it to a production ruleset that in turn had been added to the appropriate application and access group, adding the portal to the access group unexpectedly generated the error "Portal name: is not a Valid Record for use by this Rule." This was due to the system not considering production rulesets while checking rule resolution, and the parameter pyUserPreproductionrulesets has been added to the validate activity to handle this.
SR-B30423 · Issue 287970
Event Strategies enhanced for rolling windows
Resolved in Pega Version 7.3
incorrect counts were being created intermittently by Event Strategies used with a rolling window due to timing issues. To resolve this, the Event Strategy rule has been enhanced to better handle sliding time windows where intervals between incoming events are longer than the option value "Store state every N seconds" (given in the advanced settings of New: Data Flow Work Item).
SR-B30423 · Issue 280138
Event Strategies enhanced for rolling windows
Resolved in Pega Version 7.3
incorrect counts were being created intermittently by Event Strategies used with a rolling window due to timing issues. To resolve this, the Event Strategy rule has been enhanced to better handle sliding time windows where intervals between incoming events are longer than the option value "Store state every N seconds" (given in the advanced settings of New: Data Flow Work Item).
SR-B30426 · Issue 287706
Event Strategies enhanced for rolling windows
Resolved in Pega Version 7.3
incorrect counts were being created intermittently by Event Strategies used with a rolling window due to timing issues. To resolve this, the Event Strategy rule has been enhanced to better handle sliding time windows where intervals between incoming events are longer than the option value "Store state every N seconds" (given in the advanced settings of New: Data Flow Work Item).
SR-B36567 · Issue 296311
Full year date data made available to Excel for consistency
Resolved in Pega Version 7.3
Inconsistencies were seen in the handling of the year field on dates using Date or pxDateTime as a control, at times displaying the same input as 01/01/1917, 01/01/17, and 01/01/2017. To fix this, the date format in pzExport_Date_RD control has been modified from DEFAULT_DATE_SHORT to DEFAULT_DATE_SHORT_YYYY so the full year component is available for Excel.