Schema Reference
The application schema is used to configure the objects returned from a connector.
Note
-
The Account Schema tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as Entitlement or Multi-Valued. Refer to Managing Source Account Schemas for more information.
-
The schema attributes that are not present by default must be defined as strings if not specified.
The Movidesk connector uses the following default correlation and object configurations.
Default Account Schema
Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.
The set of account attributes each source stores and how they're organized is known as the account's schema. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to Managing Source Account Schemas for more information.
Default Account ID
SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as account IDs.
Caution
Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
To resolve issues caused by changing account IDs, reconfigure them to their default values.
The following table lists the default account IDs for this connector:
| Account ID | Schema Object Type |
|---|---|
| id | Account |
Default Account Attributes
The Movidesk connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.
| Attribute Name | Description |
|---|---|
| id | Unique Account ID |
| role | Role assigned to the person, used as an entitlement value |
| personType | Type of person record (for example, agent or customer) |
| contact | Contact information associated with the person |
| Email address of the person | |
| bossId | Identifier of the person's manager |
| bossName | Display name of the person's manager |
| codeReferenceAdditional | Additional reference code for the person |
| isActive | Indicates whether the person account is active |
| classification | Classification category assigned to the person |
| teams | Teams associated with the person, used as entitlement values |
| cultureId | Culture or locale identifier for the person |
| createdDate | Date the person record was created |
| timezoneId | Timezone identifier for the person |
| corporateName | Corporate or company name associated with the person |
| emailType | Type of email address associated with the person |
| businessBranch | Business branch associated with the person |
| businessName | Business name associated with the person |
| userName | Username of the person |
| accessProfile | Access profile assigned to the person, used as an entitlement value |
| profileType | Profile type of the person |
Note
Teams, role, and access profile are modeled as account entitlements on the teams, role, and accessProfile attributes. A separate entitlement schema is not used.