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.
SR-B14432 · Issue 286451
Editability check added to asterisk symbol (mandatory field expression) display
Resolved in Pega Version 7.3
Sections using conditional read-only and editable modes displayed the mandatory expression (asterisk symbol) in both modes. To correct this unexpected behavior, the GenerateLabelCellContent RUF has been updated to check whether the control is editable and only generate the asterisk if the result is true.
SR-B14618 · Issue 285696
Resolved operator authentication error causing Dnode remote execution failure
Resolved in Pega Version 7.3
An "unable to authenticate" error was generated and the Dnode remote execution task failed if the operator definition was not found and an empty username was sent for authentication. This has been corrected with additional diagnostics and a check to avoid a forceAuthentication() call.
SR-B14618 · Issue 286786
Resolved operator authentication error causing Dnode remote execution failure
Resolved in Pega Version 7.3
An "unable to authenticate" error was generated and the Dnode remote execution task failed if the operator definition was not found and an empty username was sent for authentication. This has been corrected with additional diagnostics and a check to avoid a forceAuthentication() call.