SR-B35863 · Issue 294534
Mobile visibility condition fixed
Resolved in Pega Version 7.3
A section with visibility condition expressions on two properties was not displayed on mobile when the conditions were satisfied. The root cause for the issue was two change trackers being created for the same thread, which caused an override of the tracker properties. To solve this, the isSingleTracker API in change tracker has been modified to count the number of trackers instead of using a stored variable.
SR-B3591 · Issue 277488
Unit Test Case for DataPage localized for comma decimal indicators
Resolved in Pega Version 7.3
When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.
SR-B3591 · Issue 278006
Unit Test Case for DataPage localized for comma decimal indicators
Resolved in Pega Version 7.3
When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.
SR-B35931 · Issue 293471
prpcUtils readme updated for importing to Oracle
Resolved in Pega Version 7.3
The readme regarding importing to an Oracle database has been updated to reflect the current state of prpcUtils.
SR-B35963 · Issue 292315
pyID displayed in Show relevant Records
Resolved in Pega Version 7.3
Class keys were not displayed on select picker when accessing relevant records. This was due to an misplaced 'when' condition, and has been fixed.
SR-B35963 · Issue 292466
pyID displayed in Show relevant Records
Resolved in Pega Version 7.3
Class keys were not displayed on select picker when accessing relevant records. This was due to an misplaced 'when' condition, and has been fixed.
SR-B35965 · Issue 302489
Fixed copy from data page with optional data mapping
Resolved in Pega Version 7.3
When 'Optional data mapping' was used on a pageList property with the 'copy from data page' option enabled, data was not getting populated to the PageList if the filtered result was page type. This was traced to an issue with optional data mapping in a keyed data page, and has been resolved by changing the function to add the indexed page instead of directly using the FilteredClipboardProperty.
SR-B35965 · Issue 302490
Fixed data page copy with optional data mapping
Resolved in Pega Version 7.3
Copying from a data page with optional data mapping was not populating the PageList as expected when the filtered result was page type. This was due to missing clipboard handling when the data page was sourced by VL and the keyed result was a single page. To correct this, the indexed page will be copied instead of the FilteredClipboardProperty directly.
SR-B35965 · Issue 302490
Fixed data page copy with optional data mapping
Resolved in Pega Version 7.3
Copying from a data page with optional data mapping was not populating the PageList as expected when the filtered result was page type. This was due to missing clipboard handling when the data page was sourced by VL and the keyed result was a single page. To correct this, the indexed page will be copied instead of the FilteredClipboardProperty directly.
SR-B35987 · Issue 296514
Improved backwards compatibility for migrated rules with Declare Expressions
Resolved in Pega Version 7.3
The current activity pzUpdateConditionsList did not have backward compatibility for "AND" and "OR" operators in rules created with older version of Pega Platform that allowed the use of "And" and "Or". This has been resolved by adding a check for equalsIgnoreCase when converting "And" to "&&".