Source System Integration

Client ID

This is required field. Client ID of the source system.

Grant Type

This is required field. The way an application gets an access token E.g. Authorization Code, Client Credentials or Password.

Auth URL

This is required field. Authorization URL of the source system.

Include Client Secret in Auth Token Request?

Yes or No. If yes, will enable Client Secret field to enter the details.

Include Scope in Auth Token Request?

Yes or No option. If yes, will enable Scope field to enter the restrictions to access source system.

Base 64 encoding?

Yes or No. If yes, all information will be encoded.

Auth URL

This is required field. Authorization URL of the source system.

Include Client Secret in App Authorization?

Yes or No. If yes, will enable Client Secret field to enter the details.

Include Scope in App Authorization?

Yes or No. If yes, scope will be included in the configuration.

Base 64 encoding?

Yes or No. If yes, all information will be encoded.

Grant Type

This is required field. The way an application gets an access token E.g. Authorization Code, Client Credentials or Password.

Token Type

This is required field. Select from the lookup values.

Include Client Secret in Refresh Token Request?

Yes or No. If yes, will enable Client Secret field to enter the details.

Include Scope in Refresh Token Request?

Yes or No. If yes, scope will be included in the configuration.

Auth URL

This is a required field. Authorization URL of the source system.

Client ID

This is a required field. Client ID of the source system.

Client Secret

This is a required field. the Client secret of the source system.

Grant Type

This is a required field. The way an application gets an access token E.g. Authorization Code, Client Credentials or Password.

Username

Enter the username.

Password

Enter a password.

User ID Field

This is required field. User Field Name.

User ID Value

This is required field. User Field Value.

User Password Field

This is required field. Password Field name.

User Password Value

This is required field. Enter Password value.

Relative URL

The url of the object in the source system

Method

The method to use when pulling the data. Options are: Get, Post, Put, Delete, Patch. For example, a GET, is a select of the data.

Content type

The type of the content in configuration format. E.g. Application/x-www-form-urlencoded, application/json

Choose the system

The system to create the object in. Available: Netdocuments, Imanage, or CAM

For example if you are trying to write to iManage choose iManage.

Suggested parameters

The suggested parameters to set. Content-type, Authorization are available.

Custom parameters

Set custom parameters for the objects, with a field and value pair. Click +Add

</>Encode

If the record is base64 encoded, click encode.

Header

The request header. In configuration format, Application/x-www-form-urlencoded

• View - Opens pop-up to view full Header contents.

Additional Basic Object Configuration

Additionally, you can include the API Call for same system to Fetch Data and Flattening Response containing Nested Objects by toggling ON. To configure see the below.

Response

The response pane.

• View - Opens Pop-up to view full response content

Relative URL

Specify the Endpoint URL. Based on the requirements you can replace actual Id to Uniqie_id in the Endpoint URL that helps to identify the backend process from where to replace id in the URL.

Method

Select Method type from the drop down to perform an action.

• GET

Mapping

To set the mapping of fields used for creation of the object.

For example, if you want to create an item in iManage, set the createiniManage parameter to true. It is best to set the system to CAM, and ensure the mapping here is done for the createiniManage parameter.

Pagination By:

Sorting Parameter to be used. Select from

• Response URL

• Query Parameters

• No Pagination

Pagination field

Field to be used for pagination, select from the list or manually enter the value by setting Custom Value On.

Result field

Select object name.

CAM Field

Select the CAM metadata from the drop-down. To assign a metadata, either click the drop-down menu and select from the list or manually enter the value, which will auto-complete if it is assigned in Administration>Metadata. Specifies how users can customize the name of the CAM Field -

• Prefix - Users can add custom text to the beginning of the folder name

• Custom Value - Users can assign a custom name to the folder

• Suffix - Users can add custom text to the end of the folder name

Web Response

Select the source system metadata from the drop-down. Or Manually enter a value for the field by setting Custom Value On.

Field Value

Select the default value to be assigned to the CAM metadata. Manually enter a value for the field.

Conditional Field

Dynamically setting values: e.g. ClientId = {FieldNameFromSource}&MatterId={FieldNameFromSource}

Eval Expression

(Conditional Sync)

Allows you to perform the conditional sync process using Eval expression. This process helps you to filter records coming from a source system such as the Google API.

• Using the eval expression, you can now skip records in the sync. In the eval expression, you must provide JavaScript code in the form of conditional statements with exports.skip = true or false. You can use the Variable names from the JSON Web Response attributes.

• You can find an example of the conditional sync feature implementation in the following code snippet. This code processes only those records whose name attribute starts with new-folder and skips all the other records. It helps you to filter records that start with new-folder.
  

if(typeof name !== 'undefined' 
&& name 
&& name.startsWith("new-folder"))
{
  exports.skip = false;
}
else
{
  exports.skip = true;
}

• Click Save to save the mapping. A token is generated and sent to the DevOps team.

• Get the token from the DevOps team and enter it in the Token Confirmation dialog box.

• Click the Confirm button.