...
This node was written specifically to pull data from a BC endpoint into GlobalCapture. It uses service to service oAuth login flow described here. Before attempting to use this node, be sure to follow the steps outlined for configuring auth.
Setup
You will need the Tenant ID, Client ID, and Client Secret to authenticate and make requests. It’s highly recommended you test your configuration outside of a Capture flow by following the instructions here.
...
| Info |
|---|
BC supports “custom” endpoints. Integrators may develop non-standard routes to present or join specific data elements. If the customer is using non-standard routes, the integrator will need to be involved to secure the routes properly and ensure they are published to the correct deployment (production, sandbox, etc). |
Execution
When this node runs, it will authenticate, and then perform a GET on the o365 endpoint specified. Results returned are expected to come back in a JSON object with an Array named “value”. The node will attempt to map process fields to elements at array index 0. For example, if the response includes a field named “vendorName”, it will automatically assign that value to a like named Process Field. If there are multiple matches, they will all be assigned.
| View file | ||
|---|---|---|
|
Date | Version | Description |
|---|---|---|
11/21/2022 | 1.0 | Initial node release. |
01/20/2023 | 1.1 | Fixes an error with logging connection |