Property | Description |
|---|---|
Connection Name | Name of the connection. Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -, Maximum length is 255 characters. |
Description | Description of the connection. Maximum length is 4000 characters. |
Type | Coupa V2 |
Use Secret Vault | Stores sensitive credentials for this connection in the secrets manager that is configured for your organization. This property appears only if secrets manager is set up for your organization. This property is not supported by Mass Ingestion. When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured. For information about how to configure and use a secrets manager, see Secrets manager configuration. |
Runtime Environment | The name of the runtime environment where you want to run tasks. Select a Secure Agent, Hosted Agent, or serverless runtime environment. Hosted Agent doesn't apply to mappings in advanced mode. |
Authentication | Select Coupa V2. |
Base Url | Base URL to connect to Coupa API. Specify the base URL in the following format: https://{instance_name}.coupahost.com/ For example, https://companyname.coupahost.com/ |
Client ID | The Coupa client ID required to generate a valid access token. Specify the Coupa identifier as the client ID. |
Client Secret | The Coupa client secret required to generate a valid access token. Specify the Coupa secret as the client secret. |
Scope | The scope used to authorize access to Coupa. Enter the scope defined for the user in Coupa. To enter multiple scopes, separate each scope with a space. |
Property | Description |
|---|---|
Custom Field Config | Specify custom fields for Coupa objects. Specify the custom fields in Coupa using the following format, where FieldName is value of the custom field name in Coupa, FieldType is the type of custom field, and IsAPIGlobalNamespace determines whether a custom field appears under root tag or custom-field tag in the Field Mapping tab: Object1=FieldName1,FieldType,DataType, IsAPIGlobalNamespace;\ FieldName2,FieldType,DataType, IsAPIGlobalNamespace;\ FieldName3,FieldType,DataType,IsAPIGlobalNamespace Object2=FieldName1,FieldType,DataType, IsAPIGlobalNamespace;\ FieldName2,FieldType,DataType, IsAPIGlobalNamespace Object3=FieldName1,FieldType,DataType,IsAPIGlobalNamespace;\ FieldName2,FieldType,DataType,IsAPIGlobalNamespace;\ FieldName3,FieldType,DataType,IsAPIGlobalNamespace Coupa V2 Connector supports only simple custom fields. For example: user-summary=custom_field1,Simple,String,true;\ custom_field2,Simple,String, false requisition-header=requisition_cf1,Simple,String,true;\ requisition_cf2,Simple,Integer,false;\ requisition_cf3,Simple,Integer user=user_customfield1,Simple,String,false;\ user_customfield_2,Simple,String,true For more information about the objects and rules and guidelines for custom fields in Coupa V2, see Coupa V2 Custom Fields and Rules and guidelines for Coupa custom fields. Note: The Secure agent replaces underscore in the custom field name with hyphen and displays the custom field name in the Field Mapping tab. |