Delivering powerful integrations without code using out-of-the-box Salesforce integration features
0 likes781 views
The document discusses the importance of software integration in enhancing enterprise solutions and presents various types of integrations, including data and application integration. It highlights the complexities and requirements involved in each type of integration, emphasizing the need for proper planning and execution while addressing potential risks and uncertainties. Forward-looking statements regarding the company's financial outlook are included, which may be affected by various market and operational factors.
Delivering powerful integrations without code using out-of-the-box Salesforce integration features
- 1. Delivering Powerful Integrations Without Code Anshul Verma, President anshul.verma@cynoteck.com @toanshulverma CynoteckTechnology Solutions LLC
- 2. Forward Looking Statement Statement under the Private Securities Litigation Reform Act of 1995: This presentation contains forward-looking statements about the company’s financial and operating results, which may include expected GAAP and non-GAAP financial and other operating and non-operating results, including revenue, net income, diluted earnings per share, operating cash flow growth, operating margin improvement, expected revenue growth, expected current remaining performance obligation growth, expected tax rates, the one-time accounting non-cash charge that was incurred in connection with the Salesforce.org combination; stock-based compensation expenses, amortization of purchased intangibles, shares outstanding, market growth and sustainability goals. The achievement or success of the matters covered by such forward-looking statements involves risks, uncertainties and assumptions. If any such risks or uncertainties materialize or if any of the assumptions prove incorrect, the company’s results could differ materially from the results expressed or implied by the forward-looking statements we make. The risks and uncertainties referred to above include -- but are not limited to -- risks associated with the effect of general economic and market conditions; the impact of geopolitical events; the impact of foreign currency exchange rate and interest rate fluctuations on our results; our business strategy and our plan to build our business, including our strategy to be the leading provider of enterprise cloud computing applications and platforms; the pace of change and innovation in enterprise cloud computing services; the seasonal nature of our sales cycles; the competitive nature of the market in which we participate; our international expansion strategy; the demands on our personnel and infrastructure resulting from significant growth in our customer base and operations, including as a result of acquisitions; our service performance and security, including the resources and costs required to avoid unanticipated downtime and prevent, detect and remediate potential security breaches; the expenses associated with new data centers and third-party infrastructure providers; additional data center capacity; real estate and office facilities space; our operating results and cash flows; new services and product features, including any efforts to expand our services beyond the CRM market; our strategy of acquiring or making investments in complementary businesses, joint ventures, services, technologies and intellectual property rights; the performance and fair value of our investments in complementary businesses through our strategic investment portfolio; our ability to realize the benefits from strategic partnerships, joint ventures and investments; the impact of future gains or losses from our strategic investment portfolio, including gains or losses from overall market conditions that may affect the publicly traded companies within the company's strategic investment portfolio; our ability to execute our business plans; our ability to successfully integrate acquired businesses and technologies, including delays related to the integration of Tableau due to regulatory review by the United Kingdom Competition and Markets Authority; our ability to continue to grow unearned revenue and remaining performance obligation; our ability to protect our intellectual property rights; our ability to develop our brands; our reliance on third-party hardware, software and platform providers; our dependency on the development and maintenance of the infrastructure of the Internet; the effect of evolving domestic and foreign government regulations, including those related to the provision of services on the Internet, those related to accessing the Internet, and those addressing data privacy, cross-border data transfers and import and export controls; the valuation of our deferred tax assets and the release of related valuation allowances; the potential availability of additional tax assets in the future; the impact of new accounting pronouncements and tax laws; uncertainties affecting our ability to estimate our tax rate; the impact of expensing stock options and other equity awards; the sufficiency of our capital resources; factors related to our outstanding debt, revolving credit facility, term loan and loan associated with 50 Fremont; compliance with our debt covenants and lease obligations; current and potential litigation involving us; and the impact of climate change. Further information on these and other factors that could affect the company’s financial results is included in the reports on Forms 10-K, 10-Q and 8-K and in other filings it makes with the Securities and Exchange Commission from time to time. These documents are available on the SEC Filings section of the Investor Information section of the company’s website at www.salesforce.com/investor. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements, except as required by law.
- 5. What is Software Integration “In Information Technology, process of linking together different computing systems and software applications physically or functionally, to act as a coordinated whole” (WikiPedia) Subtitle placeholder Billing Inventory Sales Service Finance HR Banking
- 6. Types of Integrations Data Integration Invoice Payment Invoice Payment Salesforce Data Warehouse/ Lake Data Integration - Data (at rest) sent from one system to other
- 7. Types of Integrations Subtitle placeholder Application Integration - Transaction data sent from one system to another, mostly on occurrence of an event - Source expects Target to initiate additional processing upon receiving data Invoice Payment Create Invoice Salesforce ERP Account Receivable Cubes (Analytical)
- 8. Integrations by Code Not for the faint hearted Manage Authentication Code Integration (Complex) Error Handling Testing (Lots and Lots) Maintenance
- 9. Integration by Point and Click
- 10. Outbound Messaging Introduction PROS CONS SimpleComplexity Data IntegrationPurpose 1. Send Salesforce data (SOAP messages) to external web service endpoint 2. Trigger integration via workflow 3. Automated retry and batching 1. Mandates Message format 2. Doesn’t support complex structure 3. Doesn’t support various authentication mechanisms
- 11. Outbound Messaging How does it work? Salesforce Account User User updates data 1 1 Workflow Outbound message External Service Workflow triggered2 Outbound Message Queued3 Outbound Message Sent4 4 3 2
- 12. Outbound Messaging – How To? How to build/ use? Create Workflow Create Outbound Message Share Service WSDL with External Developer Pre-Requisites: 1. Endpoint URL
- 13. External Objects Introduction PROS CONS SimpleComplexity Data IntegrationPurpose 1. Access remote data like native data/ objects without consuming salesforce data storage 2. Ability to search, view and report on data like native data and basic CRUD operations 3. Uses widely used common data standards (OData, FederatedSearch etc.) 1. Limited OData support across legacy applications 2. Higher network usage 3. Salesforce connect licenses costs
- 14. Salesforce External Objects How does it work? Account – Record view User User opened account record 1 1 Related list External Query External Data Source Related list invoked2 Request for External Data3 Query sent to External Data Source4 4 3 2 Receive Records Related list 5 6 7 Salesforce receive external data5 Related list data populated6 Related list displayed7
- 15. External Objects How to build/ use? Create External Data Source Create External Object (Optional) Create Relationship / Tab Pre-Requisites: 1. Endpoint URL 2. Authentication Details 3. Schema of external service
- 16. External Services Introduction PROS CONS ModerateComplexity ApplicationPurpose 1. Invoke custom Web APIs (Interagent, Swagger Open API 2.0) 2. Trigger integration via Flow 1. Schema limited to 100,000 characters 2. Less options to debug
- 17. Salesforce External Services How does it work? Issue Refund (Flow) User User initiates Issue Refund flow 1 1 Payment Service External Service Flow invokes external service action2 Request sent to External Service3 Response received from External Service 43 2 Process Response 4 5 Response Parsed and Processed5
- 18. External Services How to build/ use? Add Named Credential Register External Service Create Flow Pre-Requisites: 1. Endpoint URL 2. Authentication Details 3. External service schema (Interagent or Swagger OpenAPI 2.0)
- 19. Platform Events Introduction PROS CONS Moderate - ComplexComplexity ApplicationPurpose 1. Persistent and immutable messages 2. Enables Loosely coupled functionalities 3. Enables pub-sub pattern (publisher – subscriber) 4. Replay past events 1. Can result in complicated technical design 2. DML limits apply 3. Limits on subscribers and events to publish
- 20. Billing Salesforce Platform Event How does it work? ERP publishes platform event with order fulfilment status 1 1 Lifetime Metrics Process Builder updates customer lifetime order data 2 Billing system updates billing details 3 Process Builder updates order information 4 2 Update Order 3 ERP Create Billing 4 Salesforce sends notification to all subscribers 5 5 App 2 App 3 App N Platform event publisher Order Platform Event
- 21. Platform Events – How To? How to build/ use? Define New Platform Event Type Add Event Fields/ Attributes Publish Events Subscribe to Events Pre-Requisites: 1. Event design (attributes)
- 22. Working Demo – External Objects
- 23. Working Demo – External Services
- 24. Working Demo – Platform Events
- 25. More Learning External Objects: https://trailhead.salesforce.com/content/learn/projects/quickstart-lightning- connect External Services: https://trailhead.salesforce.com/en/content/learn/modules/external-services/get- started-with-external-services Platform Events: https://trailhead.salesforce.com/en/content/learn/modules/platform_events_basics