Integration between Appian & Salesforce

Hi Gawali,
If you are doing Update/Insert/Delete data in Salesforce from Appian. Then you need to think about how big that data will grow and frequency of the Operations use to Perform.
1. If that Data is too large then before implementing that synchronizing in Appian DB you can create a support ticket with Appian Team they can give you good guidance.
2. If that data is not expected to grow big, then you can use web Api' where from Salesforce these WebApi's triggered and can Maintain the DB synchronization.
3. If you don't want to have it Synchronization Immediately you can have batch job run at midnight which takes care of these Appian DB synchronization.

Thanks,
Chandra.

Hi Gawali !

Please go through the below articles :
docs.appian.com/.../Enterprise_Architecture_Overview.html
docs.appian.com/.../Connectors.html

Thanks,
Ravi.

I agree with Chandu's approach

I have requirement of getting Salesforce Object Schema created in Appian Cloud database including relationships.
So Which way is better. Appian provide any functionality to do this directly.

Hi Gawali,
SO you have a schema In salesforce and you need to create that same schema in Appian.
We can find any tools that are readily available to have a sql file generated for that. Its purely out of the box for me, May be DBA can assist you on this.

Ok thanks chandu

What you can do is actually create a webAPI endpoint in Appian. Use this webapi like a regular REST API.

docs.appian.com/.../Designing_Web_APIs.html

Hope this helps.

Note that SFDC integration guidance via REST or SOAP can be found in the playbook: community.appian.com/.../integrating-with-salesforce

Thanks Domen Jemec

but i have one issue to understand

with(

 local!tokenResponse: a!fromJson(index(index(rule!Salesforce_Service_Bearer_Token(),"result",{}),"body",{})),

 concat(

   index(local!tokenResponse,"token_type",null),

   " ",

   index(local!tokenResponse,"access_token",null)

 )

)

so can u elaborate.

@Gawali this is an expression rule that wraps around the Service User based integration call to format the header "Authorization" value for any SFDC interactions. If you look at screenshot for Salesforce_Service_Query, you see that in the integration headers there a call out for the expression rule: "Salesforce_Service_Token_Wrapper" which includes this SAIL outlined

This rule takes the response body from the Call to the token endpoint and concatenates the token type and access token together to form the authentication header value for any followup integrations for SFDC. Note that this is only needed if you are doing integrations on behalf of a service user. If you are using the first method outlined where you are integrating as a specific user, this rule/integration can be skipped and the connected systems will take care of it