Release Version 4.5

Restored crawling default libraries to SharePointREST Connector through a new option which adds the "Documents" library to the crawl list for each site.

Users were not getting the correct metadata for versioned document. This issue was resolved so that 3Sixty will provide the correct metadata for each document.

More info on SharePoint REST

Resolved an issue causing the content type to be pulled incorrectly.

Fixed Manage In Place issue regarding reading all versions of existing documents.

Fixed an issue with incremental jobs.

Fixed an issue that was preventing 3Sixty from creating multiple versions of some documents.

More detail on Microsoft Graph SharePoint

3Sixty will read date/time fields even if the date is entered as a negative which was resulting in errors and stopping jobs from running properly.

Resume job aspect will work more efficiently. An issue was fixed that was causing jobs to fail due to failed documents being queried in the source repository. Documentation has been updated to advise that users check their SharePoint Permissions if they are running into job failure issues as the authorised account may not have the needed permissions to conduct certain tasks.

More detail on the SharePoint REST Connector

Fixed an issue where passing an integer into a long field could not be passed as long.

Several improvements have been made to the APIv2 Swagger document available in 3Sixty.

Updated APIv2 to reflect current connectors and removing unsupported connectors.

More info on APIv2

When the user selects working copy as the output the exemption code will overlay the redacted words. Users can also edit the global properties file to customise the border and overlay box colours.

The redaction task now supports AI-based sensitive information detection and redaction as a value-add

Updates have been made to the redaction task for to work be more user friendly by expanding the new redaction task section and collapsing the previous one during configuration..

More info on the Redaction Task

More info on the Open AI Completion Task

The "Remove content after extraction" has been left unchecked by default as this is not a common use of the task but is still an option if needed.

More detail on the Tika Text Extraction Task

Logging in the JDBC post processor has been updated and the documnetation has been updated to inform users that the query supports the use of the expression language. The query samples provided in the documentation are just samples. Each SQL Query/Statement will need to be tailored to their specific Database Syntax.

More details on the JDBC Post Processor

Updates have been made to how Mongo DB handles dates and metadata resolving an issue that was causing some incremental jobs to fail.

Job Types

The new File Format Converter task will convert files of one format to another format during migration. Document processing often requires transforming documents from one format to another. For example, for long term preservation/archival, PDF/A is a desired format. All documents may not be in that format – and doing such conversion at scale is often hard, and the quality may at times be compromised. With Objective’s Universal Document Converter, any document can be converted into desired format without loss of quality. It will also support complex processing when a document cannot be directly converted into another format by converting it into a transient format before converting it into the desired format.

More about the Converter Task

Redaction is crucial for safeguarding sensitive information across the regulatory industries. The new redaction task will search the content of documents while migrating ad redact any words phrases or patterns based on the targets set in the task's configurations.

More about the Redaction Task

3Sixty has upgraded the available API keys. These can be used to create connections and jobs with or without tasks as well as run jobs without using the UI. This can speed up the process and allow for large scale scheduling. API details can be found on the individual connector and tasks pages as well as in the advanced user section under API V2.

More about API V2

3Sixty users can now add multiple sites and libraries to the SharePoint REST Connector

More about the SharePoint Connector

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).

More about user authentication

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

Resolved an issue that would cause 3Sixty to not create a job ID due to a bug with the Alfresco Site Path field causing errors and missing documents.

Fixed an incorrect default value for the Date Time Format for Alfresco output. Users should check and make sure this value matches their desired format. For existing jobs you can add the time to see the new format.

More info on the Alfresco Connector

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

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

More about user roles

Resolved the issue where if user were member of a group, 3Sixty was not able to get the permission for those users. Now 3Sixty is able to see the permission for individual users.

Resolved an issue where the SharePoint Rest URL got corrupted for subsites causing schema instances to fail. With this issue fixed users will be able to run discover instance for subsites.

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.