SR-B14905 · Issue 284489
Handling added for unexpected BLOB forms during multi-tenant initialization
Resolved in Pega Version 7.3
The PegaRULES engine was failing to initialize if it encountered a BLOB that was corrupt, null, empty, abruptly small sized, or less than 4 characters long when iterating through Data-Admin-Tenant records. An explicit check has been inserted to resolve this, which will throw a bad record exception with more information before trying decrypt.
SR-B2362 · Issue 274142
Corrected newline comparisons for pega.comparePages
Resolved in Pega Version 7.3
When mapping an external table partially to PRPC class, updating the table with Obj-Save caused the un-mapped columns to be updated to null. This was due to the comparePages API not doing an appropriate comparison whenever a property in one of the pages had a new line as a CR ("\r\n") and in the other page had new line("\n"). This has been corrected.
SR-B36880 · Issue 294350
Fixed SmartInfo positioning
Resolved in Pega Version 7.3
When any action like Refresh section, Post Value, or set value was configured before the Show SmartInfo, the smartinfo was suppressed. This was because the TargetElement was coming as stale and positioning the smartinfo based on a stale element resulted in it not getting displayed. This has been fixed by adding code to update the latest target element before positioning the smartinfo.
SR-D73260 · Issue 536889
Multiselect control support for offline-enabled iOS app
Resolved in Pega Version 8.1.8
After a custom mobile application for iOS was built and was running on iPad for an offline-enabled user adding a multiselect control into a section as part a flow caused the screen to hang when a save or submit was performed. This has been resolved by enhancing support for offline multiselect submit with the addition of pzpega_ui_template_multiselect_capsule to offline static bundle.
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-B38867 · Issue 297937
VBD loads based on collection start date
Resolved in Pega Version 7.3
An application querying VBD without a time range forced the loading of all IH records, causing performance issues. To lower the impact of such queries, VBD will now use the Start Date configured on the VBD Data Source landing page as the starting point for loading IH records. This will be enforced for queries and Eager partition loading. Note that IH Sync has NOT been modified, and will continue to copy & aggregate all IH records. This enables the start date to be adjusted backward if needed.
INC-162649 · Issue 639398
DSS added for handling missing attachments
Resolved in Pega Version 8.6.1
When an S3 repository was configured as storage, some cases were not coming up in search and exception errors were seen in logs for a deleted attachment after every system restart/re-indexing of the search. Investigation showed these case objects were in the broken queue for pyFTSIncrementalIndexer due to a null pointer error encountered when indexing the attachment, and that the attachments were available in the repository but could not be read from the attachment repository during indexing. To resolve this, a new DSS setting has been added which allows selecting one of two behaviors: - Pega-SearchEngine indexing/distributed/fail_on_missing_attachment_file = true : broken item is generated, but with a meaningful error message. This is the default behavior - Pega-SearchEngine indexing/distributed/fail_on_missing_attachment_file = false: case is indexed, but without the problematic attachment. Error message is printed out to the logs.
SR-B10103 · Issue 279865
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-B10103 · Issue 279869
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-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.