Office 365 Connect Node
- Brian Banet
- Phil Holtz
- Olivia Miller
- 1 Node Settings
- 1.1 Connections Tab
- 1.2 Authentication Tab
- 1.3 Output Tab
- 2 Use Case
This node applies to GlobalCapture only.
Use the Office 365 Connect node to Automatically release captured data and documents directly from GlobalCapture to SharePoint or OneDrive for Business from Microsoft.
The Office 365 Connect release node for Microsoft SharePoint and OneDrive will work with:
SharePoint 2013 and newer, and SharePoint Online.
OneDrive for Business.
With the connector, you can create GlobalCapture Workflows as usual and release documents to SharePoint or OneDrive for Business. To do so, you will need to install the connector Node on the capture server, configure your Workflow, and configure the connector settings using the provided utility.
For Capture Transformation Services customers, your environment would need to be setup for Sharepoint support. Contact your Square 9 authorized reseller, or your Regional Sales Director for more details.
Node Settings
Title
The Title of your node should be brief but descriptive about what action is being done. Titles are important when revisiting workflows in the future and when migrating workflows. The title of the node will be displayed when resolving conflicts during imports.
Description
The Description your node should provide notes about this node. This could include information about intended use, details of the connection, output details, field mapping, etc. Descriptions can be very useful when revisiting workflows in the future.
Data Validation
Connections Tab
URL
The URL determines where the documents are released to.
Target Path
The Target Path is the specific folder structure to which to upload the documents.
Type
The Type is the application that we want to release the documents to. We can select SharePoint Online, SharePoint and OneDrive.
Authentication Tab
The Username and Password are required, as well as the credentials of the account establishing the connection. The Domain is the name of the Windows Domain being used, or the Server Name, for authentication.
Example: AzureAD would be the domain name, and OneDriveAdmin would be the Username.
The Client ID and the Client Secret are specific to your instance of SharePoint or OneDrive, speak to your Systems Administrator for this information.
Output Tab
A GUID (globally unique ID), or Original Name is used for specifying the name of the file being released. You can also set a Custom name.
Enforce Unique Name checkbox forces GlobalCapture to check for duplicate file names before releasing documents.
Allow Overwrite lets GlobalCapture overwrite any files with the same name.
Create Folder allows the release to create its own folder structure in SharePoint or OneDrive. You can specify the folder name or use S9 notation to dynamically name them.
When configuring output parameters, it is highly recommended you use a GUID for the File Name option and DO NOT use the Enforce Unique Name option. Sharepoint, and particularly Cloud versions of Sharepoint, can have release issues with document libraries that are larger than 5,000 records. By ensuring a unique value for File Name, you can skip checks for uniqueness in Sharepoint, which alleviates any record count limits. For customers who do not wish to use a unique File Name in Sharepoint, note that your document count should not exceed 5,000 documents per document library.
Note that releasing to Sharepoint does not delete the pages from the Capture Process. If Release to Sharepoint is the last step in your process, it is best practice to insert a delete pages step to remove unnecessary files from the GlobalCapture server.
Field Mapping Tab
The Process Fields are the GlobalCapture Process Field we want to hold the data in, before it’s transferred to the SharePoint Name specified.
It’s important to note that the names may not match in both applications.
We can add process fields by clicking the Plus Button in the top right corner. To remove a process field, select the X icon to the very right of each process field you'd like to remove.
Use Case
Release documents to SharePoint before releasing to GlobalSearch
In this example, I've configured the Office 365 Connect node to release documents to a SharePoint drive, before releasing to GlobalSearch. This is useful for storing documents in a cloud-based backup solution rather than having to back up files on a physical server on or off site.
Release documents to SharePoint and clean up the process with the Delete Page Range node
In this example, I've configured the Office 365 Connect node to release documents to a SharePoint drive. As a best practice I've added in a Delete Page Range node with the option to delete all of the pages after the release has been performed as a best practice.
This is useful to remove any unnecessary files from the GlobalCapture Server.
Customers changing their authentication are strongly encouraged to test their credentials in a test workflows to ensure authentication is functioning as expected.