Objective ECM/Nexus

A logical, intuitive UX. Informative dashboards. Powerful business process capabilities. Focus on outcomes as well as information management.

www.objective.com

Authentication Connection

This connector require an Authentication Connection to function. Authentication connectors are used to authenticate repository/output connections that need certain authentication fields like access tokens or refresh tokens.

  1. Select Authentication from the navigation menu or the dashboard.

  2. Click the New Authentication button

  3. Enter a unique name for the connection and give it a description

  4. Select the connection type from the drop-down and click save.

  5. Fill in the configuration settings on the edit connection page and click save.

Authentication Connections Overview

Note:  Passthrough authentication currently only works for ECM content service:
Objective Basic Authentication Connector: passthrough username and password
Objective OAuth Connector: only passthrough username

Objective Basic Authentication

Important:  Objective Basic auth connector does not work for ECM Nexus

  • Connection Name: Unique Name for the Auth Connection to identify it in the UI.

  • Username: The username to authenticate with the repository if applicable.

  • Password: The password to authenticate with the repository if applicable.

  • Server URL: The URL to your Objective server

Objective OAuth Connection

Important:  Minimum required version of ECM/Nexus is 11.2 for OAuth connections

  • Name: Connector Name

  • Server URL: Server URL e.g https://myserver.objective.com

  • User Id: User Id with permissions to execute API calls

  • Client Id: Client Id generated when setting up the client application

  • Client Secret: Client secret generated when setting up the client application

Discovery Connection

Discovery makes mapping to and from your sources easier for data migration and ensures the data gets connected to the right fields. Discovery requires an Authentication Connection

  1. Select Schema Instance from the Navigation Menu or the Dashboard under Discovery

  2. Select the new connection button

  3. Enter a name for your Discovery Connection

  4. Select your connection type from the drop down

  5. Click save on the Create Connection form

  6. In the edit connection page fill out any addition fields and click save

Guide to Discovery Connections

Configuration

  • Name: Unique Name for the Discovery Connection to identify it in the UI.

  • Authentication Connection: Your Objective Authentication Connection

  • Ignore Types: Comma delimited list of types to ignore.

Integration Connection

Every job requires an integration connection for both the source repository connection and the output connection. Also known as input an output connections. Their job is to query or crawl remote systems for files, folders, metadata, versions, and renditions. . In repo mode, it will retrieve list items and all of their relevant metadata from a list or library on the specified site. In output mode, the connection will write content and assign the mapped content type (from type mappings), or simply leave the new list item as a Document. Click here for more information on setting up an integration connection.

  1. Select integration and click on the new connection button.

  2. Enter the name and description of your connection.

  3. Select the connection type from the drop down list.

  4. Click Save on the Create Connection form.

  5. Click Save on the Edit Connection page.

There are no fields to configure in an integration connection.

Guide toIntegration connections

  • Connection Name: This is a unique name given to the connector instance upon creation.

  • Description: A description of the connector to help identify it better

  • Authentication Connection: Your Objective Auth Connection

Job Configuration

A 3Sixty Job is the process of moving or syncing content (including versions, ACL's, metadata) from one CMS (content management system) to another. Add tasks to your job to have better control over how your data gets migrated. Click here for details on how to set up an integration job.

Guide to Integration jobs

  1. Select List Jobs under integration on the navigation menu or the dashboard

  2. Click the create job button

  3. In the New Job form

    1. Name the job

    2. Select Simple Migration from the job type drop down

    3. Select the Repository Connection

    4. Select the Output connection

    5. Select your Content Service Connection

      (Only required if you will be using Federation)

    6. Click Save to open the Edit Job page

    7. Fill in the configurations for the Repo and Output Configuration tabs

  4. Click save to save your new integration job

  1. Select Run and Monitor Jobs under Integration in the navigation menu

  2. Click the play button next to the job you want to run

  3. Click the refresh button to view your completed job status

    (Larger jobs will take longer to run)

Repository Specification

Also known as an input connection. It's job is to query or crawl remote systems for files, folders, metadata, versions, and renditions. When using this connector as a source repository filling out the following configuration fields will tell 3Sixty how to locate the files you want migrated.

Configuration

  • Comma delimited list of folders to crawl: ** For this field use FolderIds

Output Specifications

When using this connector as a file destination, filling out the following fields will tell 3Sixty where you want the files integrated to.

Configuration

  • Output Folder Path: Folder ID to start output. Note that the path from the source will be duplicated in the output and subsequent folders will be created as needed.

  • Instead of write (Objective to Objective only): An additional option when running a job from one Objective to another is to update the metadata instead of moving files.

Note:  The Objective connector uses the job's Repository Time Zone field for time zone conversion. The output Time Zone field is ignored, since 3Sixty always sends ECM a UTC DateTime.

Note:  Duplication Check Task

Given the ECM connector is the source repository, when there are two of the same documents in the source repository with different paths; and if documents are pptx, docx, xlsx files, the ECM seems to change these documents and their MD5 code are different. Therefore, when the job for ECM to ECM has a duplication check task with a field to compare as file content hash, it will create a new version for these types of documents.

When the duplication check task field to Compare is set as File content hash, and there are two emails with the same content and the same subject, the MD5 codes will still be different for these two emails. Because of this, 3Sixty cannot use duplication check task to skip one of them.

Caution:  
Only new files greater than 100MB are up chunked and uploaded.
Chunked uploads do not take place if the file already exists in the Objective folder specified.
Linked documents and version updates are not currently supported by this feature.

Tasks

Job tasks also known as processors provide a processing pipeline for documents and metadata. Post processors can also be added as a task to run after the files are processed.

Click here for a list of all the tasks you can add to your integration job.

  1. Click on the task tab in your integration job.

  2. Find the task you want to create in the drop down. Tasks are grouped by type. You can also search for the task by name.

  3. Select the create task button

  4. Fill out the configuration fields. Some tasks do not require configuration.

  5. Click Done to save the task to your job.

Mapping

3Sixty Mapping gives you the ability to map your content types and metadata from one system to another.

There are two places in 3Sixty where you can set up mappings:

  • At the top of the mapping tab you can select from saved mappings

  • Creating a unique mapping based on your connectors.

Guide to 3Sixty Mapping

Important:  When adding job mapping, the type mapping and aspect mapping should be added first and then add the calculate mapping and field mapping.

When "Field Mapping" from ECM connector, make sure fields do not have "document." prefix. For example, "document.dateUpdated" must be written as "dateUpdated" Remove the "document." prefix added by schema instance.

SharePoint Connection: When mapping "Modified by" field of SharePoint, schema instance will add it as "Document.Modified By", but it must be manually changed to "Document.simflofy_last_modified_by".

EMail Integrations

*For the MS Graph Mail connector and the Exchange Email connectors

In a job MS Graph Mail connector / Exchange Email connector to ECM with the job type set as manage in place, if the user changes the object type to E-Mail Message type through mapping, then when running the job, the external records will generate in ECM with object type as E-Mail Message and the default metadata fields set in the E-Mail Message will not get a value.

Content Service Connection

This connection will provide a full ECM API for interacting with files, folders, metadata, versions, and renditions.

Content Service Connections Overview

  1. Select Content Service under Connections in the navigation menu

  2. Click the New Connection button

  3. Fill in the following configuration fields.

Basic Configuration

  • Connector ID: Give your connector a unique name

  • Description: Provide a description for this connection

  • Type: Select the Filesystem Content Service Connector

  • Keep Connection Alive: Keep this connection active

  • Keep alive in Milliseconds (300000 is 5 minutes): How long until connection expires if unused

  • Connection URL: The web address for your connection

  • Security Mode: None needed for this connection

  • Mapping Type: Choose single map or group mapping if you are using mapping for jobs

  • Create Folder

  • Get File Content

  • Get Object Properties

  • Delete Object By id

  • List Folder items

Manage In Place

For Objective ECM Version 11.3+

Manage in Place (MIP) is intended for organisations who have their content spread out across multiple repositories (file shares, M365 sources like SharePoint, Exchange, OneDrive, or other line of business applications) and wish to centrally govern the content while meeting the records compliance needs. It allows users to manage their content's lifecycle through Objective ECM without the need to transfer it from its original location.

Click here for details on setting up your Manage in Place Jobs

API Keys

Objective Connector: Read=true: Write=true: MIP=true

Repo (Read) Specs

Key

Description

Data Type
folders Comma delimited list of folders to crawl String

Output (Write) Specs

Key

Description

Data Type
outputfolderpath Output Folder Path String