INC-126857 · Issue 564596
Added handling for download of attachment with special characters
Resolved in Pega Version 8.4.2
If the name of an uploaded attachment contained a non-ascii character, the upload was successful but the downloaded file had the wrong name without any suffix. This was an issue on WAS or JBoss servers where filenames contained non-ascii characters, and the filename parameter in the content disposition header also contained these characters. To resolve this, the filename parameter in the content disposition header will be encoded as well along with the filename* parameter to handle non-ascii characters in the filename.
INC-126857 · Issue 565640
Added handling for download of attachment with special characters
Resolved in Pega Version 8.4.2
Added handling for download of attachment with special charactersIf the name of an uploaded attachment contained a non-ascii character, the upload was successful but the downloaded file had the wrong name without any suffix. This was an issue on WAS or JBoss servers where filenames contained non-ascii characters, and the filename parameter in the content disposition header also contained these characters. To resolve this, the filename parameter in the content disposition header will be encoded as well along with the filename* parameter to handle non-ascii characters in the filename.
INC-126857 · Issue 563678
Added handling for download of attachment with special characters
Resolved in Pega Version 8.4.2
If the name of an uploaded attachment contained a non-ascii character, the upload was successful but the downloaded file had the wrong name without any suffix. This was an issue on WAS or JBoss servers where filenames contained non-ascii characters, and the filename parameter in the content disposition header also contained these characters. To resolve this, the filename parameter in the content disposition header will be encoded as well along with the filename* parameter to handle non-ascii characters in the filename.
INC-127775 · Issue 567263
Added handling to resolve missing Pega 7 schema objects error on upgrade
Resolved in Pega Version 8.4.2
After upgrade, running post-upgrade activities reported the index table 'pr4_rule_vw_idx1' was listed as missing in the PEGA_RULES schema even though the index was present on pr4_vw_idx1. This was caused by formatting differences between Pega 7 and Pega 8.4 intended to make the columns unique. The pxObjClass column was removed from that index in 8.4 but this made it equivalent to the vw_updateDateTime index. As a result the code that performs the DDL upgrade ignored the new definition for pr4_rule_vw_idx1 because vw_updateDateTime already existed. It was safe to ignore this 'missing' index as the correct form exists as vw_updateDateTime, but to avoid issues the pXObjClass column has been added back to index pr4_rule_vw_idx1, but as a second column in the index.
INC-129143 · Issue 565392
Resolved sync error for offline workorder
Resolved in Pega Version 8.4.2
After logging on to the mobile app and then switching to off-line mode before opening a workorder from the worklist and processing the full workorder from end to end in offline mode, reconnecting resulted in the work order being moved to the [email protected] work basket with “Sync-Failed” status. Investigation showed that this was a caused by the DateTime properties being an empty string or null despite being created with a valid string. This was traced to the datetime conversion handling, and has been resolved.
INC-131416 · Issue 575453
Class Loader cache values wrapped with WeakReference for improved cleanup
Resolved in Pega Version 8.4.2
Out Of Memory exceptions due to Metaspace were observed on Web tier instances running with a max Metaspace size of 2GB. Investigation showed that in PRClassLoaderDB, mLoaderCache values were wrapped with a SoftReference. To resolve this, the Class Loader cache values will be wrapped with a WeakReference, allowing the cache to free memory when it is no longer needed. JVM options has also been added to switch types of References being used if there is a preference.
INC-131518 · Issue 575754
PegaURLBuilder API updated to handle authentication alias
Resolved in Pega Version 8.4.2
The fragment '/app/ApplicationName' was getting appended to the Document URL whenever a sharable link was generated for the document attached in the spaces, causing the link to fail. This was traced to previous assumptions that a public link URL would not have an authentication alias. Now that an authentication alias can be added to the public link URL, an update has been made to the PegaURLBuilder API: the last URL component in the public link URL will be retrieved then verified with the existing authentication aliases. If it matches, then the authentication alias will be injected to the URL in the appropriate location.
INC-131629 · Issue 570035
Updated padding character handling for access group hash
Resolved in Pega Version 8.4.2
While generating an access group hash from an access group name, Pega was using the '(' character as padding. However, Siteminder blocks the '(' character, causing requests to be rejected. To resolve this, the padding character will be removed while encoding and decoding will handle hashes both with and without the padding character.
INC-132769 · Issue 573198
ArrayList constructor added to jarList initialization
Resolved in Pega Version 8.4.2
During the Switch Schema and Rolling Restart phase of an upgrade, failure occurred on the all the tiers with the error "PRRuntimeException: Method Invocation exception". This was traced to the method used to implement list initialization from an array, and has been resolved by adding an ArrayList constructor for jarList initialization.
SR-D40785 · Issue 515100
WorkPageName preserved during passivation so attachments are correctly tracked
Resolved in Pega Version 8.4.2
When a work object was left open but inactive for a period, using the delete button in the pyAttachFieldRequired section caused the deletion of the Attachment Links for the 500 most recent attachments in the system with the same value for the AttachmentFieldName, regardless of which work object they were attached to. This was due to the delete attachments activity being executed with missing parameters: since data page loading was disabled and read-only data pages are not passivated, the value for the autopopulate property 'WorkPageName' was passed as empty. This has been resolved.