Release Version 4.4

Resolved an issue with the date/time field not parsing correctly. 3Sixty no longer adds the value true to the date time format field which was causing an error during integration.

More info on the Azure Blob Connector

Resolved an issue that would time out manage in place jobs during post processing. The idle timer will no longer time out a job if post processing is still occurring.

More info on Manage In Place

The action option for tasks (where available) has been changed from Audit and Continue to Continue. If a task encounters an error or a document that meets the stated conditions, users can chose to either continue, skip of fail. In certain cases the changes will be stated in the metadata if the fields are mapped to display. For example if you are running a duplication check task and you have mapped the duplication detection fields you can create a BFS job to see the files tagged as duplicate.

More information on using Objective 3Sixty Tasks

The user guide has been updated to clarify how chaining trivial detection tasks work. Using one task will detect a file as trivial if all conditions are met. Chaining tasks will detect files that match either condition of the separate detection tasks. For example you can use one task if you want to find files under a certain size and with a certain file type. Chaining tasks will allow you to find files under a certain size or with a certain file type.

To prevent 3Sixty from overwriting the trivial tags when processing the chained tasks, use the condition check and enter the following statement for subsequent tasks.

equals('#{field.isTrivial}', 'false')

This will tell 3Sixty to only check files where the isTrivial flag is set to false, allowing you to see all files detected as trivial instead of just the files detected by the last processed task.

More information on the Trivial Detection Task

Access related issue fixed for 3Sixty Discovery users.

More information on User Authentication Management

When using the CMIS connector as an output connector users were not able to uncheck the following boxes

• Strict Version Mode (true/false)

• CMIS Cache Enabledd (true/false)

This issue has been resolved and users can now uncheck the boxes if they do not want to include those options during migration.

Also when using the CMIS connector users ran into an issue where the connector would only migrate the first version of a document. 3Sixty has been updated so that the CMIS connector will now support multiple versions.

More information on using the CMIS Connector

Reverts a change that breaks certain aspects of the Tesseract Extraction Task. If you have added this task to any Jobs or Task Groups since installing 4.4.0 it will need to be recreated.

Group mapping has been updated to allow users to select a group or groups when mapping instead of having to manually enter the group name(s).

The executor and monitor roles have been fixed to give authorization to create or view a discovery report.

Users can now use Microsoft Entra ID to login to 3Sixty and manage groups and user roles through a new authentication management section under administration.

Upgraded Elasticsearch version to 7.17.22
Upgraded Jackson version to 2.17.2. Configured Jackson deserialization to allow reading the maximum allowed string stream length

Job run history and mapping audits for automatically generated PII scans were changed so that they are not deleted upon completion of the scan and can now be viewed in the audit detail.

An Amazon KMS key can now be used for server side encryption.

Changed the way processed documents are counted. 3Sixty will check if the document is already processed in the system based on the `sourceRepositoryId`. If not, they only we count as new document processed.
Note: If an any repo uses paths an as id (Filesystem/S3), then if the document is moved after its been processed, it will be counted again, since there is no way to record it being moved, and it could be a copy.

Added a feature to use existing tasks if requested. If existing tasks already contain PII Detection Task, then the default PII Detection task will not be used. Improved the PII Scan Results in discovery to provide more relevant information when using the PII Scan.

Adds a feature to the PII Properties that will allow for the export and import of PII Rules using a CSV file.

Fixed an issue Automatically Generated PII Jobs not copying over the Thread Count from the original job.
Fixed an issue where PII Detection Tasks were logging, but not marking the task as failed, if an error occurred.
Updated default pii rules to avoid issues on export/import

Configured the Tika Text Extractor task to use temporary storage to process files over 50 megabytes, fixing an issue where large files were not being processed.

Fixed an issue where inputting multiple semicolons in custom parameters in Content Service connectors were causing an parsing error. Updated so that only the first parameter is taken as a delimiter.

Resolved an issue with the transfer manager. It will now wait until the upload is finished before sending the upload request.
S3 timeouts are now in seconds, rather than milliseconds. The timeout will also be applied to staging the file to disk.

Resolved an issue with resuming a MIP job if documents have already been processed/errored/skipped.
Removed document from in process when they are already processed/errored/skipped.

The way PII properties are imported have changed. There is a sample file available. A text editor is recommend instead of using excel which can cause issues.

New fields added to the PII detection and Tika Text Extraction configurations.

• Attach extracted text as metadata

• Field name for extracted text content