Before using the TMF674 v4 resource mappings, refer these.
Assumptions
The initiation of a request from Salesforce to the Mule Application is implemented by the user.
GET, POST, and PATCH are synchronous interfaces, and the response from the external system is returned to the calling system.
Processing the response for GET, POST, and PATCH is implemented by the user.
The externalId is mapped with vlocity_cmt__PremisesIdentifier__c
The response includes only the optional parameters that are supported to prevent a 4xx error response.
The authentication mechanism used to connect to the Salesforce org is OAuth.
In the event of failures when invoking the external system endpoint, the request is retried up to three times, with a two-second interval between each retry attempt.
The href element is not passed as part of the payload for POST and PATCH.
The vlocity_cmt is taken as the default namespace prefix for the Salesforce object.
These resource and sub-resources are supported for the salesforce package entity: Premise (vlocity_cmt__Premises__c)
A user-friendly name for the place, such as [Paris Store], [London Store], [Main Home].
Name
status
string
-
The condition of the GeographicSite, such as planned, underConstruction, cancelled, active, inactive, former.
vlocity_cmt__Status__c
@type
string
-
The class type of the actual resource (for type extension).
”GeographicSite”
relatedParty
array
-
A RelatedPartyRefOrPartyRoleRef. RelatedParty reference. A related party defines party or party role or its reference, linked to a specific entity.
Sub-Resource - Related Party(entity = Account)
siteRelationship
array
-
A GeographicSiteRelationship. Details of geographic site relationship.
Sub-Resource - GeographicSiteRelationship
place
array
-
A PlaceRefOrValue. The polymorphic attributes @type, @schemaLocation & @referredType are related to the Place entity and not the PlaceRefOrValue class itself.
j