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-B13785 · Issue 284733
Added tenant ID check for batch thread in MT environment
Resolved in Pega Version 7.3
When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.
SR-B13785 · Issue 284743
Added tenant ID check for batch thread in MT environment
Resolved in Pega Version 7.3
When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.
SR-B13785 · Issue 278965
Added tenant ID check for batch thread in MT environment
Resolved in Pega Version 7.3
When attempting to build a Hybrid Container app in the mobile tab (landing page) in tenants, the build did not complete. The same build did work correctly in the main requestor. The issue was traced to a missing tenant ID if a secondary instance had been written to the database by a background thread, and has been resolved by explicitly checking and if necessary adding the tenant ID to PRThreadwhen using batch thread in a BuildServer client.
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.