Marketing Preference XAPI

(0 reviews)

FileMaker-Jarvis to Salesforce Integration

  • Vision: FileMaker Jarvis posts the Accepted articles and author information to Journal Article and End User Person Accounts Salesforce objects respectively.
  • FileMaker Jarvis: File Maker POST the Accepted articles Details to MuleSoft REST API

Sequence Diagram:

resources/filemaker%20%283%29-cb5cb7dd-cab1-4d42-be30-86322725500b.png


Sequence Diagram Description:

No.StepsDescription
1.Accepted Article DetailsThe File Maker Jarvis POST accepted articles details in Json Format to MuleSoft REST API
2.Validate if either Email ID or ORC ID suppliedValidate Email ID or ORC ID should be present, If validation fails, service returns specific error response.
3.Response Message AcceptedOn successful validation API sends accepted response to client.
4.Post Account and Preference DetailsThe MuleSoft experience API Post account and preference details to marketing preference process API.
5.Create or Update End User Person AccountMarketing preference process API validates if record exist in salesforce, accordingly, sends PUT or POST call to downstream Salesforce system API.
6.Feed End User Person Accounts and Journals Articles DataSalesforce SAPI creates or updates End User Person Account feed.
7.1Success Response Create or UpdateSalesforce SAPI responds back to caller API with success details in JSON format
8.1Failure Response Create or UpdateSalesforce SAPI responds back to caller API with exception details in JSON format.
8.2POST Data Feed ExceptionSalesforce SAPI transform the exception details and feed the details back to Salesforce Data Feed Exception object.
9.Return response from Salesforce System APIReturns the success response to marketing preference process API.
10.Return response from marketing preference process APIReturns the success response to marketing preference experience API.

End Point details:

  • File Maker : /api/acceptedArticles
TopicDetails
1.Operation DescriptionAccept the request in Json format and sent it salesforce System via Market preference PAPI
2.URI/api/acceptedArticles
3.MethodPOST
4.Interface SourceFileMaker
5.Interface TargetSalesforce system
6.Synchronous/AsynchronousSynchronous
7.ProtocolHTTPS
8.URLhttps://apis-sandbox.cambridgeassessment.org.uk/cupa-marketing-preference-xapi-dev/api/acceptedArticles
9.Mode of Communication☐ Batch ☐ Message ☒ Real Time
10.Interface Pattern☐ Publish / Subscribe ☒ Request / Reply

Reviews