2024.11.1.1211 Patch

Fix

Export

When a template was generated with a placeholder rule, subsequent exports could generate all images as placeholders not adhering to the scope set by the rule. This has been corrected to follow the configuration of the rule.

In some situations, when Automate ScanPST was enabled, this workflow could be initiated even when all content was extracted from the PST due to an inconsistency when calculating the expected child count. This calculation has been improved to prevent ScanPST from being run when not necessary.

When adding endorsements to an export with Tiff/PDF images, an exception would be thrown due to missing required settings at the time of configuration. This has been improved to prevent the export from being submitted until all necessary settings are configured.

Fix

Export

When images were exported using the Australian Protocols export type, the job could stall with a “Requested value 'ARIAL' was not found” error cause by a bad evaluation of branding fonts. This has been resolved to prevent jobs from not completing and output as intended.

Fix

Reports

Keyword search group designations were not being considered for keyword reports. An update to reflect these configurations has been applied.

New

Project Settings

A new project level setting, labeled “Process Teams items as Short Message,” can be found under Processing Options > Email. This setting is on by default and allows the user to disable the treatment of Teams messages to generate 24 chunk renderings and instead output individual files per message when turned off.

Fix

Import

Logic was not properly considering volume storage versus S3 for on-prem environments, which led to project paths using a mishmash of forward ( / ) and back ( \ ) slashes, leading to problems at other steps in the workflow. Enhancements have been made to better align how paths are created depending on storage method in use.

Fix

Export

The point in time when family hash values were generated for Journaled emails prevented them from being identified as duplicates when compared to the non-journaled version. Order of operations has been improved to ensure these examples are better identified as duplicative.

Fix

Export

MasterDate generation was found to be miscalculated for projects configured with the Aspose email engine. Logic has been updated to properly calculate MasterDate values for Aspose configured projects.

Fix

Export

SQL used to generate export files was inadvertently omitting mime mail types. This SQL has been corrected so that output is included at export as intended.

Changed

Import

When reprocessing an archive after running ScanPST, it is possible that previously extracted items could be removed through the ScanPST remediation. These items could then result in missing native errors at export time. Improvements have been made to set these items to filtered so that they will be excluded from further processing or export, ensuring that natives can be generated at export time.

Fix

Import

Attachments extracted from NSF files were encountering file recognition errors due to a conflict between 32 and 64 bit processes. Implementation has been updated to prevent this conflict and allow attachment extraction as expected.

Fix

Import

Some PST's containing partial corruption could run into an issue with job progressed stalled when using the Aspose email engine. This workflow has been improved to better prevent corrupted items from causing jobs to hang for long periods of time.

Fix

Import

A situation could occur where files from a container are improperly extracted to the same directory, resulting in false identification of duplicates. Improvements have been made to prevent files being assigned the same path and processed as intended.

Fix

Export

In certain examples of Teams exports, the 24 hour rendered chunks would not be generated as expected. In large part, these are instances were both Teams and standard email were included in the PST. Additional logic has been implemented to better identify Teams messages and ensure the proper rendering path is followed.

Fix

Project Settings

Date filters configured during Project Creation were inadvertently applying with exclusionary logic. This has been corrected to apply as an inclusion filter.