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-B14129 · Issue 284313
JSON mapping updated to support page list class given as string value
Resolved in Pega Version 7.3
Connect Rest was not parsing the value of the Boolean property "isEligible" returned as part of a JSON response or mapping it on to the clipboard. This was traced to the unexpected scenario of the string "$ANY" being used as class for a page list and inside a pagelist Boolean property. To support this use, the JSONMappingUtils.java file mapObjectToPage method has been modified to handle the Boolean property before the generic else if condition.
SR-B14153 · Issue 284939
Only relevant records shown for work objects in select property picker
Resolved in Pega Version 7.3
The select property picker for all work objects with record identifiers was showing all records whether or not they were relevant. This was an issue where show relevant was being set to false when record identifier and show relevant was true in pyGetCategoryItems for all classes, and has been corrected by skipping this step for work object classes.
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-B14210 · Issue 284725
Autocomplete updated to handle null resultcount from data page
Resolved in Pega Version 7.3
The autocomplete control was not rendering a list supplied by data page results due to the pxResultCount being null in the results of the datapage. The count size calculation in the autocomplete function has been reworked to resolve this.
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-B14288 · Issue 289182
Command line BIX extract works as expected for -l option
Resolved in Pega Version 7.3
When a BIX extract was generated using rule XML of the extract rule (-I) from the command line, the manifest generated had "pxExtractIdentifier" in an unexpected format. The command line option has now been modified to generate the extract with the correct pzInsKey of the rule.
SR-B14331 · Issue 287641
pzSUS Param properly URLEncoded
Resolved in Pega Version 7.3
The Tomcat 8+ server was rejecting DWA URLs due to characters such as {,} that it considered to be unsafe. These characters were introduced by pzSus key in the URL, and these values will now be encoded for the browser to resolve these issues.
SR-B14416 · Issue 289018
Fixed double actions on repeat layout
Resolved in Pega Version 7.3
In a Grid Repeat Layout, actions added on the event 'Enter' were automatically added to event 'Click' and resulted in double actions at the runtime. This was an issue with the system incorrectly setting the pyKeyCode in pzGridActionSets Activity, and has been fixed.
SR-B14420 · Issue 296416
Thread locking implemented to handle multiple thread potential on a data flow
Resolved in Pega Version 7.3
When attempting to activate data flow runs from different threads depending on the status of the run, the threads detected that the data flow was not running and triggered the run activation simultaneously. This caused multiple threads to run when only one was expected to be executed. To avoid this, a lock mechanism has been implemented that will prevent multiple threads from triggering a run at the same time if the run is already being executed by a different thread. Those that fail to trigger the run will generate and log an exception indicating that status.