SR-B45093 · Issue 301258
Fixed invalid reference for auto-populate
Resolved in Pega Version 7.3
An invalid reference exception was generated while trying to do Property-Ref on two properties inside Auto populate. This was caused by a coding error in a check used to avoid doing a getSourceProperty in case of a reference to a top level page, and has been fixed by modifying the setAsReference API in ClipboardProperty to gracefully handle Autopopulate scenarios.
SR-B45640 · Issue 302810
Resolved ConcurrentModification exception in getclass name
Resolved in Pega Version 7.3
Attempting to getclass name while iterating over values of mPageProperties in expandAllToProperties (in the putPropertyOntoClipboard call) was causing a ConcurrentModificationException that resulted in queues being blocked and loss of synch to the server. In order to more cleanly set the pxObjClass for the classless page-properties, pxObjClass has been added to the lookupDictionaryDefinition.
SR-B45640 · Issue 303222
Resolved ConcurrentModification exception in getclass name
Resolved in Pega Version 7.3
Attempting to getclass name while iterating over values of mPageProperties in expandAllToProperties (in the putPropertyOntoClipboard call) was causing a ConcurrentModificationException that resulted in queues being blocked and loss of synch to the server. In order to more cleanly set the pxObjClass for the classless page-properties, pxObjClass has been added to the lookupDictionaryDefinition.
SR-B47342 · Issue 303997
Fixed page reference error when copying
Resolved in Pega Version 7.3
An error stating reference pyWorkPage.ProductLines were not valid was generated during deferredSave while copying embedded reference type auto populate properties. This was caused by operations that added references from the data page before the current auto populate's reference information was added to duplicator. To resolve this, if the copy target is auto populate the system will skip adding references, and if the target is any other page the references will be copied.
SR-B4768 · Issue 276160
Global DB Trace timestamp uses UTC
Resolved in Pega Version 7.3
When running Global DB trace, recorded timestamps were not following the 'set timestamp' setting. Timestamps instead corresponded to the requestor context. DB Tracer logging has been updated to ensure appended timestamps are passed as "UTC".
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.