SR-B10103 · Issue 279866
Improvements in Export to Excel of very large files
Resolved in Pega Version 7.3
When exporting a very large (6000+ row) decision table into Excel, the process was very slow and the lack of a progress or busy indicator created the impression that the system was not responding. To resolve the processing issue, the code has been optimized to create lesser style objects. A busy indicator will also be displayed until the file starts download to indicate the operation is in progress.
SR-B10667 · Issue 283291
IOS HC app login updated to better handle sync conflicts
Resolved in Pega Version 7.3
Intermittent HC iOS login failures or app crashes were accompanied by the error 'Client Store synchronization failed.' To resolve this, web-login has been updated to handle cases where login failure occurs while a sync is in progress.
SR-B10826 · Issue 283698
Widget descriptions localized for Case Manager
Resolved in Pega Version 7.3
Localization has been added to the widget descriptions for "Team Worklist" and "Welcome to Case Manager".
SR-B12207 · Issue 285722
Corrected Org text field handling for templated mobile sections
Resolved in Pega Version 7.3
Given a section pyWorkSummary_Mobile with a text input field called Organization, the organization name was shown correctly in the Declare_crmOrg page but on the UI it was displaying 'Org Not Found'. This was caused by recent section template changes that caused the object to be rendered on the wrong thread, and has been fixed.
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 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-B13431 · Issue 283632
Mobile App description localized in PegaExpress
Resolved in Pega Version 7.3
The descriptions for Pega API and Pega Mobile SDK were not being localized in Pega Express due to limitations in the accepted characters. This has been fixed.
SR-B13431 · Issue 283681
Mobile App description localized in PegaExpress
Resolved in Pega Version 7.3
The descriptions for Pega API and Pega Mobile SDK were not being localized in Pega Express due to limitations in the accepted characters. This has been fixed.