SR-B13020 · Issue 283559
Upgrade App Schema generates unique index name IDs
Resolved in Pega Version 7.3
Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.
SR-B13020 · Issue 283078
Upgrade App Schema generates unique index name IDs
Resolved in Pega Version 7.3
Upgrade Schema index was not incrementing the system-generated index name properly, resulting in duplicate names and a failure to execute new recommendations. This was an issue with duplicate indexes being generated through the UpgradeApplicationSchema Landing Page when the hash truncation matched indexes incorrectly. This has been resolved by using both the table name and the index name to ensure unique IDs.
SR-B13647 · Issue 291863
Security Policy updates to handle big strings
Resolved in Pega Version 7.3
The implementation of a "one of" Access Control Security Condition that took the list from a Data Page was failing SQL construction due to the string exceeding 4000 chars. To resolve this, support has been added to SetClob() for page references, changes have been implemented in for the AllOf and OneOf functions, and a new property 'pyParameterValueUpdated' has been added to the Pega-RulesEngine.
SR-B13647 · Issue 291683
Security Policy updates to handle big strings
Resolved in Pega Version 7.3
The implementation of a "one of" Access Control Security Condition that took the list from a Data Page was failing SQL construction due to the string exceeding 4000 chars. To resolve this, support has been added to SetClob() for page references, changes have been implemented in for the AllOf and OneOf functions, and a new property 'pyParameterValueUpdated' has been added to the Pega-RulesEngine.
SR-B13931 · Issue 286184
BIX extract Inskey error fixed for nested page lists
Resolved in Pega Version 7.3
BIX Extract was failing with the message "Inskey of the corrupt Instance" if it encountered nested page lists. To resolve this, the PropertyReferenceImpl.filter() method will add missing elements in cases with nested pagelists.
SR-B14109 · Issue 292263
Fixed autocomplete for strings containing plus sign
Resolved in Pega Version 7.3
Autocomplete was not working properly when a search string contained the '+' sign. When the search input was passed to the DB, the + sign was changed to + in the query and therefore did not return any results. This was due to the parameter being encoded twice as it was passed from autocomplete to the grid infrastructure, and has been resolved by preventing the unneeded encoding.
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.