SR-B47917 · Issue 304886
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-B47958 · Issue 303935
Resolved page group copy error
Resolved in Pega Version 7.3
A WrongModeException occurred while copying a page group due to incorrect clipboard handling for the page mode. This has been fixed.
SR-B51793 · Issue 308487
Extended options for creating Context URI
Resolved in Pega Version 7.3
In order to facilitate the use of Amazon Web Services, an enhancement has been added to extend the methods available for forming Context URI. Previously, Pega Platform mandated both X-Forwarded-Host and X-Forwarded-Proto be present when using HTTP extension headers. The new feature adds HOST support when X-Forwarded-Proto is present without X-Forwarded-Host. The URL will consider X-Forwarded-Proto for protocol (http or https) and take the host name from host header. This change works for any reverse proxy or load balancer, as long as they emit X-Forwarded-Proto and preserve the HOST header.
SR-B5308 · Issue 275351
Special characters correctly encoded in downloaded filenames
Resolved in Pega Version 7.3
While downloading an attachment file containing special characters in file name, the file was getting saved with ASCII codes. This was caused by the file name being encoded in download operations, and has been fixed by providing the encoding type as UTF-8 in the content disposition header for the sendFile() method.
SR-B5560 · Issue 276633
Corrected page passivation for parameterized data pages
Resolved in Pega Version 7.3
A null-pointer exception error was generated when performing findPage() on a parameterized Data page after the page/thread was passivated and restored. This was traced to a situation where a page with meta data was not correctly saved while passivating due to a failed condition check on last update time, and has been resolved with changes to the EditDataPageHandler to update the access time whenever page is loaded from findDataPage() method.
SR-B5672 · Issue 280747
Corrected and improved calculations for multiple page Business Calendars
Resolved in Pega Version 7.3
The Business Calendar time zone was not correctly populated when a second page was added to the calendar. This was due to the new page using the operator time zone instead of the business calendar time zone, and has been fixed. In addition, the difference calculations for calendar processing have been improved for greater accuracy.
SR-B5672 · Issue 283549
Corrected and improved calculations for multiple page Business Calendars
Resolved in Pega Version 7.3
The Business Calendar time zone was not correctly populated when a second page was added to the calendar. This was due to the new page using the operator time zone instead of the business calendar time zone, and has been fixed. In addition, the difference calculations for calendar processing have been improved for greater accuracy.
SR-B5813 · Issue 276080
DuplicateProperty checked on enqueue
Resolved in Pega Version 7.3
The enqueue() method of PRQueueManager was not honoring the "pyDuplicateProperty" value of the existing queue items which have a higher pyMinimumDateTimeForProcessing. To correct this, QueueManagerImpl has been modified so the enqueue() method uses an overloaded version of next() method which is intended to ignore pyMinimumAgeForProcessing when checking for duplicates.
SR-B613 · Issue 273665
Null check added to RecalculateAndSave
Resolved in Pega Version 7.3
A null-pointer exception occurred during an index operation within the deferred save in RecalculateAndSave due to the context page being null during declare index processing. A null check has been added for the context page to resolve this.
SR-B6244 · Issue 277566
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: