This tutorial will take you through setting up a NetDocuments Integration. There are a few steps in this tutorial that must be completed within a time limit imposed by NetDocuments. To make configuration as easy as possible we have laid out this tutorial so you will have everything you need to complete configuration in time.

Before we begin make sure you are ready to complete the following steps:

1. Complete a POST request to NetDocuments within a 2 minute window
2. Fire a Rest Request Action from Onit to NetDocuments within a 20 minute window

First we will configure the Onit side of the integration. While configuring you will see that you need the following information from NetDocuments. Obtaining this information is outlined later in the document.

1. Encoded Client ID
2. Encoded Client Secret
3. Refresh Token

Steps that require any of the information stated above are marked with a yellow header for easy replacement later.

Create a new App called NetDocuments with the following Fields:

• name
  • Display name: NetDocuments Integrator
  • Type: Text

• netdocs_auth
  • Display name: Netdocs Auth
  • Type: Text
  • Liquid calculation:

{% assign x = netdocs_response | parse_json%}{{x.body.access_token}}

• netdocs_refresh
  • Display name: Netdocs Refresh
  • Type: Text
  • Liquid calculation:

{% assign x = netdocs_response | parse_json%}{{x.body.refresh_token | url_encode}}

• netdocs_response
  • Display name: Netdocs Response
  • Type: Text

Create a new Rest Request Action named Get Token

• URL: https://api.vault.netvoyage.com/v1/OAuth
• Call: POST
• Headers: (replace with your base 64 encoded client id and client secret)

Authorization: <ENCODED CLIENT ID AND CLIENT SECRET (E.G., BASIC ABCED...)>
Content-Type:application/x-www-form-urlencoded

• Body JSON:

grant_type=refresh_token&refresh_token={{netdocs_refresh}}

• Status Field: Netdocs response

Next create an Action Button to run the Get Token action.

Now that we have configured the NetDocuments App, we need to set up the App as a list provider in Onit. Create a new Transaction List Provider with the following Fields:

• Name: NetDocuments
• App: NetDocuments
• Atom Columns:
  • [NetDocuments] NetDocs Auth (netdocs_auth)
  • [NetDocuments] NetDocuments Integrator (name)

Now we will configure the iFrame. To begin we will need to find the client workspace GUID and the cabinet number to make the REST Request URL.

To retrieve the client workspace GUID login to your NetDocuments vault page (https://vault.netvoyage.com/neWeb2/docCent.aspx) then select Admin from the username drop down in the top right.

The URL on the next page will contain the GUID.

To get the Cabinet ID Number go to to Profile attributes from the Navigation menu

Then find the appropriate cabinet. The cabinet number will be the last two digits of the id.

To create the iFrame navigate to the App you would like the iFrame to display in, here we will use the Matter App.

Create a new Rest Request Action with the following information:

• URL: https://api.vault.netvoyage.com/v1/attributes/<CLIENT_WORKSPACE_GUID>/<CLIENT_CABINET_NUMBER>
• Call: PUT
• Headers

Authorization:Bearer {{ NetDocuments Integrator | list_lookup: NetDocuments, name, netdocs_auth}}

Content-Type:application/json

• Body JSON:

{
"defaulting": "",
"description": "{{name}}",
"hold": true,
"key": "{{number}}"
}

The final thing we need for this integration on the Onit side is the iFrame window. In the Matter App navigate to App Panels and create a new iFrame.

Name: NetDocs

Height: 700

URL:

https://vault.netvoyage.com/neWeb2/goId.aspx?ws={{number}}&cabinet=<CABINET_GUID>&smallDisplay=F

Notice a few things here:

• ws = workspace key
• cabinet = specific client cabinet GUID, not the cabinet ID number (see below)
• smallDisplay = F (changing this from 'F' to 'R' or other options from NetDocs will change the display type, such as full or mobile modes)

You can find the cabinet GUID by navigating to the admin page in the NetDocuments Admin Console and selecting the appropriate cabinet.

The cabinet GUID will appear in the cabinet URL.

You have completed the Onit side of this integration.

The following steps will walk you through obtaining the Client ID, Client Secret, Redirect URI, and Additional Redirect URI's (optional).

First, login to the NetDocument Partner Community (https://netdocuments.force.com/login). From the Home page click the Accounts tab.

Click 'Onit, Inc'

Scroll down to 'Applications' and find the correct application in the list and click 'Edit'.

From here, grab these four items.

Client ID (I.E. “AP-1234ABCD”)

Client Secret (I.E. “abcdefghijklmnopqrstuvwxyz123456890”)

Redirect URI (I.E. https://www.onit.com)

(Optional) Additional Redirect URIs (I.E. http://localhost/)

Now that you have the client ID and client secret, we'll need to encode them to make the Authorization Header.

To create this header join your Client ID and Client Secret with a ':'

For example:

Client ID of  “AP-1234ABCD”

Client secret of “abcdefghijklmnopqrstuvwxyz123456890”

Resulting plain-text header: AP-1234ABCD:abcdefghijklmnopqrstuvwxyz123456890

Next take this plain-text header and encode it using https://www.base64encode.org/

Take the resulting encoded header and prepend it with 'Basic'.

The authorization header value would then be:

“Basic QVAtMTIzNEFCQ0Q6YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY4OTA=” 

and the full authorization header would be

“Authorization: Basic QVAtMTIzNEFCQ0Q6YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXoxMjM0NTY4OTA=”

Save this full header for later use.

Now you should have:

• Client ID
• Client Secret
• Redirect URI
• (Optional) Additional Redirect URIs
• A base64 encoded header