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.
SR-B12636 · Issue 284032
CSS updates to improve Microsoft Internet Explorer 11 and Chrome case type label text wrap
Resolved in Pega Version 7.3
The case type labels descriptions were chopped off in Microsoft Internet Explorer 11, while in Chrome, descriptions were intact but labels appeared below the check box. To resolve this, code for a new format for checkboxes called Bold has been added to the style sheet for application config wizard overrides. This updates the case type and data type sections to use a caption for the checkbox instead of two separate controls (checkbox + label) to handle wrapping of label to next line. The updated skin also contains overrides to use an ie-flex-fix class to handle text wrapping issues in Microsoft Internet Explorer 11 due to Flexbox layouts not working properly in that browser.
SR-B12636 · Issue 280290
CSS updates to improve Microsoft Internet Explorer 11 and Chrome case type label text wrap
Resolved in Pega Version 7.3
The case type labels descriptions were chopped off in Microsoft Internet Explorer 11, while in Chrome, descriptions were intact but labels appeared below the check box. To resolve this, code for a new format for checkboxes called Bold has been added to the style sheet for application config wizard overrides. This updates the case type and data type sections to use a caption for the checkbox instead of two separate controls (checkbox + label) to handle wrapping of label to next line. The updated skin also contains overrides to use an ie-flex-fix class to handle text wrapping issues in Microsoft Internet Explorer 11 due to Flexbox layouts not working properly in that browser.
SR-B12714 · Issue 294429
String comparison logic updated for complex property references
Resolved in Pega Version 7.3
Running a report that has a single page property (.Address.pyCountry) generated an error and the report shows no results. It worked correctly if the column is removed or a filter was added on instances that have .Address.pyCountry not null. This was an issue related to string comparisons, and has been resolved by updating the logic for parsing of complex references in UDFs.
SR-B12737 · Issue 283588
Resolved harness error after using pagination 'load more'
Resolved in Pega Version 7.3
After using the Pagination 'load more' option and clicking on any of the newly loaded items, a blank harness was opened. This was traced to missing change tracking data for the newly loaded rows, and has been corrected.