Unique identifier for the Concur Settings record, typically used as the primary key in integrations or internal references.

System-generated global identifier used to uniquely track this record across environments or integrations.

System-generated URL or reference link to the current record within Veeva Vault.

Human-readable name or title assigned to the Concur Settings configuration.

Current lifecycle state of the record, such as Active, Inactive, or Archived, based on system-defined status values.

Username or user ID of the person or system that originally created the record.

Timestamp indicating when the record was initially created in the system.

Username or user ID of the person or system that most recently updated the record.

Timestamp capturing the date and time of the last modification to the record.

Code representing the attendee type classification for accounts in Concur event mapping.

Identifier for the Concur-integrated company associated with this configuration, used to scope settings to a specific company.

Secure token used to request new access tokens when integrating with Concur's OAuth authentication flow.

Comma-separated list of additional field identifiers used to store custom attributes for attendees.

Configuration reference for how attendees in Concur are linked to call records in Vault.

Configuration for how Vault call records are matched to Concur data elements.

Defines the mapping logic for associating the primary attendee in a Vault call with the appropriate Concur record.

Internet domain associated with the company used for validating Concur integrations or filtering data.

Username of the Concur administrator account used to manage and authorize API-based integrations.

Region where the associated Concur data center is located, such as US, EU, or CN, used for directing API requests.

Numeric code that determines selection or filtering logic when syncing data from Concur to Vault.

Code that specifies how contact-type attendees are identified during integration with Concur.

Comma-separated list of email addresses that should receive notifications when integration events or errors occur.

Code used to classify attendees that are speakers at events in Concur-Vault mapping.

Code used to categorize event team members during attendee synchronization from Concur.

List of user-defined fields that capture additional expense information from Concur during data transfer.

Expense type code that is applied at the header level for Concur expense reports imported into Vault.

Unique identifier used to link specific expense records from Concur to Vault records during data import.

Mapping logic that determines how medical event attendees in Vault correspond to Concur records.

Mapping rules that align Vault medical event records with corresponding event data from Concur.

The unique client key issued by Concur used to authenticate this application when requesting access tokens via the OAuth protocol.

The confidential client secret associated with the OAuth Key, used to securely validate the application during OAuth token exchanges.

The token granted after successful authentication, used to authorize API requests made to the Concur system on behalf of a user or integration.

The classification or identifier for non-user attendees included in expense reports, such as external consultants or guests, as configured in Concur.

The method of payment associated with Concur expense transactions, such as corporate card, personal card, or cash.

A predefined internal code representing the type of event attendee who is a Concur-registered user, often used for mapping or filtering attendee records.

The code representing attendees who are manually entered into event records, typically for ad hoc participants not pre-registered in Concur.

The internal identifier for the user or system entity that owns or manages the current Concur integration setup in Vault.

The name or reference of the security profile applied to this integration, determining access permissions and data visibility within Veeva Vault.

A reference identifier for Customer Relationship Management (CRM) systems previously used before the current Concur integration, retained for backward compatibility or data migration.

Specifies the version of the Concur API being targeted by this integration, ensuring compatibility with available endpoints and features.

The application-level configuration profile that defines environment-specific settings and parameters for the Concur integration.