SR-B14169 · Issue 293161
BIX documentation updated for using pxExtractDataWithArgs
Resolved in Pega Version 7.3
The section of the BIX documentation that describes the use of pxExtractDataWithArgs with an agent has been updated to specify that the agent should be set to Advanced mode unless specifically creating queue items that are needed for Standard mode.
SR-B14212 · Issue 298395
Reference properties will iterate over copies to avoid conflicts with concurrent changes
Resolved in Pega Version 7.3
Concurrent Modification Exceptions were occurring in Reference Properties scenarios where backreferences were modified somewhere in the call stack while the system was looping through them. To avoid this, the system will iterate over copies of the references.
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-B14732 · Issue 296513
Resolved error with DateTime property comparison crossing daylight savings time
Resolved in Pega Version 7.3
If an operator was using time zone "Europe/London" and locale "en_US", an error occurred when comparing two dates if the property type was DateTime and one of the dates selected in Date range fell under daylight savings time. The error did not occur if the property was of type Date. The addCalendar RUF has been updated to resolve this issue.
SR-B14732 · Issue 296847
Resolved error with DateTime property comparison crossing daylight savings time
Resolved in Pega Version 7.3
If an operator was using time zone "Europe/London" and locale "en_US", an error occurred when comparing two dates if the property type was DateTime and one of the dates selected in Date range fell under daylight savings time. The error did not occur if the property was of type Date. The addCalendar RUF has been updated to resolve this issue.
SR-B14905 · Issue 284489
Handling added for unexpected BLOB forms during multi-tenant initialization
Resolved in Pega Version 7.3
The PegaRULES engine was failing to initialize if it encountered a BLOB that was corrupt, null, empty, abruptly small sized, or less than 4 characters long when iterating through Data-Admin-Tenant records. An explicit check has been inserted to resolve this, which will throw a bad record exception with more information before trying decrypt.
SR-B15463 · Issue 287079
New Application operator mapping refinements
Resolved in Pega Version 7.3
When using the New Application Creation wizard, the newly created operators were unexpectedly mapped to the same access group even though the access groups contained different roles. This has been corrected with changes in the pxPrepareApplicationDemoUsers and pxPrepareClonedAccessGroup activities to set transient properties for the original access group name as well as for use in lookup by demonstration users.
SR-B15497 · Issue 286469
Styling corrected for last row in tree grid sourced from RD
Resolved in Pega Version 7.3
Tree grids sourced from report definitions had their last row set to the class "grandTotal" instead of "gridRow", causing them to get incorrect styling. This was caused by a missed cleanup for this use case when removing the GrandTotal class from support in RD, and has been fixed.
SR-B15497 · Issue 295707
Styling corrected for last row in tree grid sourced from RD
Resolved in Pega Version 7.3
Tree grids sourced from report definitions had their last row set to the class "grandTotal" instead of "gridRow", causing them to get incorrect styling. This was caused by a missed cleanup for this use case when removing the GrandTotal class from support in RD, and has been fixed.
SR-B15663 · Issue 289919
Trend chart drilldown made consistent with chart display
Resolved in Pega Version 7.3
Trend chart drilldown did not match chart display due to issues with time zone being converted on the chart display but not on the the drilldown. When drilling down into a datetime group, the value of that group was used to create a single filter that matched the group (e.g., "Day of [.DateTime] = 20170101"). This caused the filter to match that time based on the server's time zone settings, not the user's (e.g., if the server was using GMT, then days always began at midnight GMT, so a user could drill down into a single day and get results spanning two days). To correct this, FusionChartDataGeneration.normalizeDateCal no longer localizes for the user's time zone if the time unit is larger than an hour, e.g. day or month units won't be normalized.