際際滷

際際滷Share a Scribd company logo

Orchestrator and Flow in Slack: Antoine Cabot - Jacksonville Architects - Salesforce

A. Engin Utkan
A. Engin Utkan

This is an event for all Architects and aspiring Architects who are interested in the developments of Salesforce Automation. You can join this meeting to hear how Orchestrator and Flow on Slack can be used to automate your business processes. You can ask your questions and get answers from Antoine who is one of the few experts in Salesforce on this topic. A few questions that come to mind (forward-looking statements permitting): - What is the roadmap for the Orchestrator? How is the adoption? - What is the roadmap for Flow in Slack? What are the resources you can rely on when building your automation using this functionality? - Should we expect automation to come together on the platform in the future, and how do Einstein NBA, Mulesoft, and RPA come into play?

1 of 20
Download to read offline
Flow Orchestration & Flow in Slack Antoine Cabot Senior Director of Product Management June 15, 2022
Statement under the Private Securities Litigation Reform Act of 1995: This presentation contains forward-looking statements about the companys 鍖nancial and operating results, which may include expected GAAP and non-GAAP 鍖nancial and other operating and non-operating results, including revenue, net income, diluted earnings per share, operating cash 鍖ow 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 companys results could di鍖er 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 e鍖ect of general economic and market conditions; the impact of geopolitical events; the impact of foreign currency exchange rate and interest rate 鍖uctuations 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 signi鍖cant 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 o鍖ce facilities space; our operating results and cash 鍖ows; new services and product features, including any e鍖orts 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 bene鍖ts 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 a鍖ect 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 e鍖ect 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 a鍖ecting our ability to estimate our tax rate; the impact of expensing stock options and other equity awards; the su鍖ciency 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 a鍖ect the companys 鍖nancial results is included in the reports on Forms 10-K, 10-Q and 8-K and in other 鍖lings 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 companys 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. Forward-Looking Statement
Our Agenda 1 2 4 5 3 Flow in Slack Combined scenario Demos Q&A Flow Orchestration
Orchestration Multi-User Process: Flow Orchestration Skills-based Capacity Work Routing: Omni-Channel Service Level Agreements: Entitlements Interactions Conversational Self-Service: Einstein Bots Component Builder: FlexCards Smart Forms: Flow Builder, OmniScript Integration Low Code API Actions: External Services Data Virtualization: Salesforce Connect Pro-Code Integration: MuleSoft AnyPoint Low-Code Integration: MuleSoft Composer for Salesforce Decisioning Intelligent Actions: Einstein Next Best Action, Einstein Recommendation Builder Intelligent APIs: Einstein Language, Einstein Vision Business Rules: Decision Tables Intelligent Predictions: Einstein Prediction Builder Intelligent Insights: Einstein Discovery Automation Unstructured Data Extraction: Einstein Document Reader Autolaunched, Triggered, Scheduled: Flow Builder Robotic Process Automation: MuleSoft RPA Templates, Actions, Libraries: AppExchange Out-of-the-box Work鍖ows: 900+ Work鍖ow Templates Work鍖ow Libraries & Extended Capabilities Slack AI
Spectrum of Salesforces Process Automation Suite The Three Main Ways To Make Things Happen Full Declarative OmniStudio Full Programmatic OmniScript, FlexCards, Data Tools, Rules Engine, Doc Gen Pros: Programmatic level of functionality built with Con鍖guration For Work鍖ow and UI and Integration, Addl Rules/DocGen/Docusign Functionality Cons: New Skill Set Apex, LWC, AppExchange Pros: Full and virtually unlimited capabilities Cons: Expensive and time consuming to build, deploy, maintain. Work鍖ow Rules, Process Builder, Flow, Orchestrator Pros: Easy To Con鍖gure, platform integrations(SMS/Quip), ecosystem Cons: Limited UI Design, Limited Integration Capabilities(generally requires Apex/LWC for extensibility)
Flow Its the bedrock of automation on the platform Diverse tool set for automation buildable by Admins/Business Users. Great visual builder! Guided processes for single users through screen 鍖ows Run headless 鍖ows that work in the background Good con鍖guration tools, apex extensibility Lots of pre-de鍖ned platform functions like SMS,quip, etc. Tons of usability and functionality enhancements over the past few years! Awesome ecosystem and huge adoption around 鍖ow! But there are use cases that go beyond the OOTB and need to be built by non-devs, and thats why we have new options! Is awesome! Over 1T executions per quarter!
When can other tools supplement Flow. Flow OOTB is GREAT for work鍖ow that collects, updates, and/or creates Salesforce data, and interacts with other native functionality (SMS/Quip/Scheduler) Where Flow needs code for extensibility beyond the above: external use cases because LWC is needed to match corporate branding requires invocable apex to utilize external data* requires invocable apex to work with complex queries and hierarchical data doesnt have a native rules engine doesnt support multi-user processes So, if your use case falls into the above, and you dont have dev resources *External services.
Omnistudio introduces new automation tools to reduce the amount of code needed to work with hierarchical/external data and build pixel-perfect UI. It also ADDS a bunch of cool stu鍖 that previously reqd LWC Flow Orchestrator lets you run a 鍖ow of 鍖ows, and aimed at solving for multi-user work鍖ows As a solution architects and admins, you now have a more diverse set of tools in our belt. And dont worry, while well make comparisons, this isnt an either/or situation. They can all work together, so it should be whats the best tool for the job Ok, Flow isnt ideal for every use case. Now What? OmniStudio Flow Orchestration
Lets take a look at Flow Orchestration
Orchestrate work across users and systems Coordinate multi-user, multi-step tasks and approvalsinternal or externalacross the entire business for a seamless experience Build complex work鍖ows fast Drive continuous improvement with Low Code that makes it easy to quickly adjust and scale with changing needs Optimize time between hando鍖s Schedule parallel workstreams and reduce time between tasks with work queues, noti鍖cations, and intelligent decisioning Unify multi-user, multi-step work鍖ows. Flow Orchestration
1. Multi-Department Supports complex processes that span multiple teams So When Should you use Flow Orchestration? 3. Low Code Low code tooling empowers devs and admins to scale 2. Parallel Processes Supports parallel processes, not just sequential step by step 4. Supports All Org Incorporates non-Salesforce users who need to participate in work鍖ows Flow Supercharger Flow Orchestration is a unifying layer built on top of Flow, enabling more comprehensive automation
Waitwhat about Flow in Slack?
Deploy your Salesforce automation to Slack Automate communications Create collaboration-based automation with full support for Salesforce data and actions Collect input with guided work鍖ows Update data using guided, multi-step prompts, without needing to log into Salesforce Create an engagement layer for every work鍖ow Add an engagement layer to any work鍖ow including complex process orchestration Flow in Slack
Send Slack Message Action Get User Get Records Pin Slack Message Action Create Slack Channel Action Invite Users Action Auto-create a channel Create a channel when an opportunity changes and invite all relevant stakeholders to collaborate on next steps Auto-send messages Send messages related to an account status and pin them to ensure new and existing members can 鍖nd it Get Slack Information Action Archive Slack Channel Action Auto-archive channels Check Slack channel status and auto-archive any open channel when Opportunity stage is Closed Is Channel Archived? Decision Automate Communications Using Slack Actions in Flow Take the guesswork out of collaboration Edit Slack Message Action
Putting it all Together
Process Automation Primer Processes can be broken down into sub-processes Sub-Processes can range from: Manual tasks Simple record updates Complex, integrated, rules based, external facing, etc Business Process Is Not So Simple Or Straightforward
Lets take a look at a full process.A Loan App/Approval My requirements include: I need to capture my customers application data from our portal with our branding I need to have a loan o鍖cer look at the data collected and make some simple updates If the loan is complex/high risk, I need to pull a risk score from an external system and calculate a weighted risk score based on the amount requested, and allow a risk o鍖cer to make adjustments I need to generate loan documents once the credit evaluation is complete So what do I do? I use the right tool for the right job at each stage of the process
DEMOS
Q&A
Thank You

More Related Content

Orchestrator and Flow in Slack: Antoine Cabot - Jacksonville Architects - Salesforce

  • 1. Flow Orchestration & Flow in Slack Antoine Cabot Senior Director of Product Management June 15, 2022
  • 2. Statement under the Private Securities Litigation Reform Act of 1995: This presentation contains forward-looking statements about the companys 鍖nancial and operating results, which may include expected GAAP and non-GAAP 鍖nancial and other operating and non-operating results, including revenue, net income, diluted earnings per share, operating cash 鍖ow 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 companys results could di鍖er 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 e鍖ect of general economic and market conditions; the impact of geopolitical events; the impact of foreign currency exchange rate and interest rate 鍖uctuations 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 signi鍖cant 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 o鍖ce facilities space; our operating results and cash 鍖ows; new services and product features, including any e鍖orts 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 bene鍖ts 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 a鍖ect 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 e鍖ect 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 a鍖ecting our ability to estimate our tax rate; the impact of expensing stock options and other equity awards; the su鍖ciency 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 a鍖ect the companys 鍖nancial results is included in the reports on Forms 10-K, 10-Q and 8-K and in other 鍖lings 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 companys 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. Forward-Looking Statement
  • 3. Our Agenda 1 2 4 5 3 Flow in Slack Combined scenario Demos Q&A Flow Orchestration
  • 4. Orchestration Multi-User Process: Flow Orchestration Skills-based Capacity Work Routing: Omni-Channel Service Level Agreements: Entitlements Interactions Conversational Self-Service: Einstein Bots Component Builder: FlexCards Smart Forms: Flow Builder, OmniScript Integration Low Code API Actions: External Services Data Virtualization: Salesforce Connect Pro-Code Integration: MuleSoft AnyPoint Low-Code Integration: MuleSoft Composer for Salesforce Decisioning Intelligent Actions: Einstein Next Best Action, Einstein Recommendation Builder Intelligent APIs: Einstein Language, Einstein Vision Business Rules: Decision Tables Intelligent Predictions: Einstein Prediction Builder Intelligent Insights: Einstein Discovery Automation Unstructured Data Extraction: Einstein Document Reader Autolaunched, Triggered, Scheduled: Flow Builder Robotic Process Automation: MuleSoft RPA Templates, Actions, Libraries: AppExchange Out-of-the-box Work鍖ows: 900+ Work鍖ow Templates Work鍖ow Libraries & Extended Capabilities Slack AI
  • 5. Spectrum of Salesforces Process Automation Suite The Three Main Ways To Make Things Happen Full Declarative OmniStudio Full Programmatic OmniScript, FlexCards, Data Tools, Rules Engine, Doc Gen Pros: Programmatic level of functionality built with Con鍖guration For Work鍖ow and UI and Integration, Addl Rules/DocGen/Docusign Functionality Cons: New Skill Set Apex, LWC, AppExchange Pros: Full and virtually unlimited capabilities Cons: Expensive and time consuming to build, deploy, maintain. Work鍖ow Rules, Process Builder, Flow, Orchestrator Pros: Easy To Con鍖gure, platform integrations(SMS/Quip), ecosystem Cons: Limited UI Design, Limited Integration Capabilities(generally requires Apex/LWC for extensibility)
  • 6. Flow Its the bedrock of automation on the platform Diverse tool set for automation buildable by Admins/Business Users. Great visual builder! Guided processes for single users through screen 鍖ows Run headless 鍖ows that work in the background Good con鍖guration tools, apex extensibility Lots of pre-de鍖ned platform functions like SMS,quip, etc. Tons of usability and functionality enhancements over the past few years! Awesome ecosystem and huge adoption around 鍖ow! But there are use cases that go beyond the OOTB and need to be built by non-devs, and thats why we have new options! Is awesome! Over 1T executions per quarter!
  • 7. When can other tools supplement Flow. Flow OOTB is GREAT for work鍖ow that collects, updates, and/or creates Salesforce data, and interacts with other native functionality (SMS/Quip/Scheduler) Where Flow needs code for extensibility beyond the above: external use cases because LWC is needed to match corporate branding requires invocable apex to utilize external data* requires invocable apex to work with complex queries and hierarchical data doesnt have a native rules engine doesnt support multi-user processes So, if your use case falls into the above, and you dont have dev resources *External services.
  • 8. Omnistudio introduces new automation tools to reduce the amount of code needed to work with hierarchical/external data and build pixel-perfect UI. It also ADDS a bunch of cool stu鍖 that previously reqd LWC Flow Orchestrator lets you run a 鍖ow of 鍖ows, and aimed at solving for multi-user work鍖ows As a solution architects and admins, you now have a more diverse set of tools in our belt. And dont worry, while well make comparisons, this isnt an either/or situation. They can all work together, so it should be whats the best tool for the job Ok, Flow isnt ideal for every use case. Now What? OmniStudio Flow Orchestration
  • 9. Lets take a look at Flow Orchestration
  • 10. Orchestrate work across users and systems Coordinate multi-user, multi-step tasks and approvalsinternal or externalacross the entire business for a seamless experience Build complex work鍖ows fast Drive continuous improvement with Low Code that makes it easy to quickly adjust and scale with changing needs Optimize time between hando鍖s Schedule parallel workstreams and reduce time between tasks with work queues, noti鍖cations, and intelligent decisioning Unify multi-user, multi-step work鍖ows. Flow Orchestration
  • 11. 1. Multi-Department Supports complex processes that span multiple teams So When Should you use Flow Orchestration? 3. Low Code Low code tooling empowers devs and admins to scale 2. Parallel Processes Supports parallel processes, not just sequential step by step 4. Supports All Org Incorporates non-Salesforce users who need to participate in work鍖ows Flow Supercharger Flow Orchestration is a unifying layer built on top of Flow, enabling more comprehensive automation
  • 13. Deploy your Salesforce automation to Slack Automate communications Create collaboration-based automation with full support for Salesforce data and actions Collect input with guided work鍖ows Update data using guided, multi-step prompts, without needing to log into Salesforce Create an engagement layer for every work鍖ow Add an engagement layer to any work鍖ow including complex process orchestration Flow in Slack
  • 14. Send Slack Message Action Get User Get Records Pin Slack Message Action Create Slack Channel Action Invite Users Action Auto-create a channel Create a channel when an opportunity changes and invite all relevant stakeholders to collaborate on next steps Auto-send messages Send messages related to an account status and pin them to ensure new and existing members can 鍖nd it Get Slack Information Action Archive Slack Channel Action Auto-archive channels Check Slack channel status and auto-archive any open channel when Opportunity stage is Closed Is Channel Archived? Decision Automate Communications Using Slack Actions in Flow Take the guesswork out of collaboration Edit Slack Message Action
  • 15. Putting it all Together
  • 16. Process Automation Primer Processes can be broken down into sub-processes Sub-Processes can range from: Manual tasks Simple record updates Complex, integrated, rules based, external facing, etc Business Process Is Not So Simple Or Straightforward
  • 17. Lets take a look at a full process.A Loan App/Approval My requirements include: I need to capture my customers application data from our portal with our branding I need to have a loan o鍖cer look at the data collected and make some simple updates If the loan is complex/high risk, I need to pull a risk score from an external system and calculate a weighted risk score based on the amount requested, and allow a risk o鍖cer to make adjustments I need to generate loan documents once the credit evaluation is complete So what do I do? I use the right tool for the right job at each stage of the process
  • 18. DEMOS
  • 19. Q&A