SR-B12215 · Issue 281902
Cancel button fixed for pzTabbedScreenFlow7 harness
Resolved in Pega Version 7.3
The Cancel button was visible on the modal template of the Data import Wizard but was missing on the pzTabbedScreenFlow7 harness. This has been fixed.
SR-B12256 · Issue 281696
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-B12345 · Issue 281568
Custom Validator support restored to Workformstandard
Resolved in Pega Version 7.3
Recent refactoring changed the behavior of Workformstandard. In order to support custom edit validate rules defined as part of the application to be executed on client-side, the custom validators HTML fragment has been restored to Workformstandard with correct pre-checks.
SR-B12369 · Issue 282877
Select button accessibility update
Resolved in Pega Version 7.3
Further refinements have been made to accessibility enhancements which will maintain focus on a select button after posting/submitting if a hidden input is present.
SR-B12374 · Issue 282127
Resolved StaleThreadError in LogHelper
Resolved in Pega Version 7.3
Repetitive stale thread errors were appearing in LogHelper. A check for thread destruction has been added to resolve this.
SR-B12374 · Issue 287614
Resolved StaleThreadError in LogHelper
Resolved in Pega Version 7.3
Repetitive stale thread errors were appearing in LogHelper. A check for thread destruction has been added to resolve this.
SR-B12451 · Issue 283057
Added case type propagation for layered applications built with NA wizard
Resolved in Pega Version 7.3
After creating an application on top of another using the New Application wizard and selecting the case types which need to be included the new application, not all of the cases and classes that should be present were shown. This was an issue with the correct pagelist not being checked while populating case types in the layered application, and code has been added to ensure all the case types of an existing application will come to a newly created application if the new application is built on top of an already existing application.
SR-B12474 · Issue 282553
BIX extraction config documentation updated
Resolved in Pega Version 7.3
When using command-line BIX 7.1 to extract records and write them to a secondary database, it appeared that some of the records got skipped. This was actually expected behavior: as the records got updated while the extract was running, those particular updated records got skipped as they did not fall into the time range that user was passing. To eliminate this confusion, the log message has been clarified. In addition, the information in the Guide indicated that if bix/useHistoryClasses was set to true, the generated query should always use the history table and not the actual work object table. However, it was not made clear that the BIX code does not use this option for explicit command line arguments. Therefore, the following text has been added to the BIX documentation under "Configuring the extraction environment" -> "Configuring optional prconfig.xml settings": Including class instances added during a batch run To ensure that class instances added to the Pega Platform database after a batch run begins execution are included in the extract, add the following property:
SR-B12474 · Issue 282643
BIX extraction config documentation updated
Resolved in Pega Version 7.3
When using command-line BIX 7.1 to extract records and write them to a secondary database, it appeared that some of the records got skipped. This was actually expected behavior: as the records got updated while the extract was running, those particular updated records got skipped as they did not fall into the time range that user was passing. To eliminate this confusion, the log message has been clarified. In addition, the information in the Guide indicated that if bix/useHistoryClasses was set to true, the generated query should always use the history table and not the actual work object table. However, it was not made clear that the BIX code does not use this option for explicit command line arguments. Therefore, the following text has been added to the BIX documentation under "Configuring the extraction environment" -> "Configuring optional prconfig.xml settings": Including class instances added during a batch run To ensure that class instances added to the Pega Platform database after a batch run begins execution are included in the extract, add the following property:
SR-B12581 · Issue 282710
Documentation correction for setupDatabase.properties naming
Resolved in Pega Version 7.3
The install, upgrade, and update guides on the PDN referring to the setupDatabase.properties file properties gave erroneous name formats for the schema name properties. All instances in the documentation referring to pega.rules.schema have been changed to the correct format of rules.schema.name, and all instances of pega.data.schema have been changed to the correct format of data.schema.name.