The Salesforce Provisioning Plugin provisions Contacts to Salesforce via the Force.com REST API. |
Registry CO Person Transaction | Changelog Action |
---|---|
Add | Synchronize the CO Person with Salesforce |
Edit | Synchronize the CO Person with Salesforce |
Enter Grace Period | No changes (unless attributes change as part of grace period) |
Expiration / Becomes Inactive | Synchronize the CO Person with Salesforce |
Unexpire / Becomes Active | Synchronize the CO Person with Salesforce |
Delete | No changes |
Manual Provision | Synchronize the CO Person with Salesforce |
Registry CO Group Transaction | Changelog Action |
---|---|
Add | No changes |
Edit | No changes |
Delete | No changes |
Manual Provision | No changes |
Registry CO Email List Transaction | Changelog Action |
---|---|
Add | No changes |
Edit | No changes |
Delete | No changes |
Manual Provision | No changes |
/services/oauth2
appended, eg https://test.salesforce.com/services/oauth2The SalesforceProvisioner plugin supports the use of a Salesforce Custom Object in order to provide additional attributes (see below) beyond what is supported in the Salesforce Contact record. To enable support for the CoPerson Custom Object:
The above instructions will not cause the Custom Object to appear on the Contact page, though it is visible if directly addressed.
The Salesforce Provisioner uses the following attribute mapping:
Registry Attribute | Salesforce Attribute | Notes |
---|---|---|
Address:country (type postal ) | MailingCountry | First Address of type postal associated with the first CoPersonRole Values must be from Salesforce picklist. Attribute Enumerations may be useful. |
Address:locality (type postal ) | MailingCity | First Address of type postal associated with the first CoPersonRole |
Address:postal_code (type postal ) | MailingPostalCode | First Address of type postal associated with the first CoPersonRole |
Address:state (type postal ) | MailingState | First Address of type postal associated with the first CoPersonRole Values must be from Salesforce picklist. Attribute Enumerations may be useful. |
Address:street (appended with Address:room, if set) (type postal ) | MailingStreet | First Address of type postal associated with the first CoPersonRole |
CoPerson:status | CoPerson__c:Status__c | If CoPerson custom object is enabled |
CoPersonRole:ou | Department | Department associated with the first CoPersonRole, sorted by CoPersonRole order. |
CoPersonRole:title | Title | Title associated with the first CoPersonRole, sorted by CoPersonRole order. |
EmailAddress:mail | If Email Address Type is set, the first Email Address of the specified type is used. Otherwise, the first Email Address of any type is used. | |
Identifier:identifier | CoPerson__c:Application_ID__c | If CoPerson custom object is enabled, type as configured in CoPerson Application ID Identifier Type |
Identifier:identifier | CoPerson__c:Platform_ID__c | If CoPerson custom object is enabled, type as configured in CoPerson Platform ID Identifier Type |
Identifier:identifier (type orcid ) | CoPerson__c:ORCID__c | If CoPerson custom object is enabled |
Name:honorific | Salutation | Primary Name is used, regardless of type |
Name:given | FirstName | Primary Name is used, regardless of type |
Name:middle | Middlename | Primary Name is used, regardless of type Middle Name is not enabled by default in Salesforce. Once enabled there, tick Provision Middle Name in the Provisioner configuration. |
Name:family | LastName | Primary Name is used, regardless of type |
Name:suffix | Suffix | Primary Name is used, regardless of type |
TelephoneNumber:number (type mobile ) | MobilePhone | First TelephoneNumber of type mobile associated with the first CoPersonRole |
TelephoneNumber:number (type office ) | Phone | First TelephoneNumbe of type office associated with the first CoPersonRole |
The Salesforce API has request limits that vary according to the service tier and available licenses. To view current API usage, use the Salesforce Source plugin if configured, or login to Salesforce and navigate to Reports > Administrative Reports > API Usage Last 7 Days. Note that the API call required to determine the current API limits counts against the API limit. |
In general, each provisioning operation (create or update) requires 1 API call, plus an additional API call if the CoPerson custom object is enabled.