Unlocking Seamless End-to-End Automation with the MuleSoft Automation Suite | MuleSoft Mysore Meetup #43
- 2. Mysore MuleSoft Meetup 13-Jan-2024 Unlocking Seamless End-to-End Automation with the MuleSoft Automation Suite
- 3. Organizers Shubham Chaurasia Billennium India Pro Integration Developer Giridhar Meka Sr. Technology Architect /in/giridharmeka /in/shubhamchaurasia1 Priya Shaw LTI MindTree Sr. Integration Specialist /in/priya-shaw
- 4. Speaker • Senior RPA Consultant at Lehmann + Pioneers Digital GmbH • MuleSoft Mentor • 10+ Years of Experience • Salesforce Certified MuleSoft Hyperautomation Specialist • https://www.linkedin.com/in/kiruthika-nithyanandan-06a7b0118/ Kiruthika Nithyanandan
- 5. Agenda MuleSoft Automation – Platform Overview Interaction Mechanisms RPA and Composer RPA and Anypoint Composer and Anypoint Demo Use case - Overview Live Demo Q&A Networking & Wrap-up
- 7. MuleSoft Automation – Platform Overview
- 8. When to use each MuleSoft product? MuleSoft RPA • Automating manual repetitive tasks involving UI or desktop applications (e.g., Excel, web browser) • Accessing legacy, terminal-only systems • Automating processes that require a “human in the loop” or involve reading data without defined syntax or OCR data • Last mile in hybrid automation solution MuleSoft Composer • Integrating SaaS systems using pre-built, IT-approved connectors (Zendesk,jira,Workday, Slack, …) • Orchestrating multi-step automations and integrations using clicks instead of code Anypoint Platform • Implementing API-led connectivity • Producing composable assets • Integrating with DevOps processes
- 9. MuleSoft RPA • Accessing a system via the UIs in order to bypass approved APIs and controls • Using bots to create point-to-point integrations between systems • Automating applications that cannot be installed on or accessed by a Windows RPA bot • High volume, bulk/ETL data transfer MuleSoft Composer • Integrating on-premise systems • Implementing complex integrations or data transformations that require coding • High volume, bulk/ETL data transfer Anypoint Platform • Consuming data from user interfaces • Simple integration of SaaS systems with available Composer connectors When to not use each MuleSoft product?
- 11. Interaction Mechanisms between RPA, Composer & Anypoint HTTP request from Anypoint Mule flow to RPA Manager • Anypoint Mule can submit "start process" command • Anypoint Mule can inquire process status • RPA publishes interface definitions of its APIs in the Anypoint Exchange HTTP requests from MuleSoft RPA Bot to Anypoint API endpoint • Bot can retrieve API responses (poll for status) • Bot can submit commands or propagates events HTTP request between Composer and RPA Manager • Composer can submit "start process" command • Composer can inquire process status • RPA can call an “Invokable” composer flow HTTP request from Composer to Anypoint API endpoint • Composer can retrieve data from Anypoint API
- 12. RPA & Composer
- 13. Composer to RPA ● RPA connector inside the composer flow ○ Sync calls - wait for the RPA process to finish before continuing with the Composer flow ○ Async Calls - invoke an RPA process and continue the Composer flow execution while the RPA process executes in parallel
- 14. RPA to Composer ● Create an “Invokable” Composer flow ● Use “REST call” action step in RPA to call the composer flow ● Configure the REST call with the flow credentials of the composer flow
- 15. RPA & Anypoint
- 16. RPA and Anypoint HTTP request from Anypoint to RPA API • Publish RPA API to Anypoint Exchange via an Invokable run configuration • Use the corresponding connector in the Mule app to Start an RPA process • Get the execution status of an RPA process HTTP request from RPA to Anypoint • Use REST call to configure the HTTP Request • Use Json Query to parse the response
- 18. Composer & Anypoint Composer to Anypoint API endpoint • Composer can retrieve data from Anypoint API • Use API sharing, if enabled • Use HTTP connector, if not Anypoint to Composer • Use HTTP Request to call an invokable composer flow
- 19. Demo Use Case - Overview
- 20. A Company wants to vet customer orders above a certain order value to reduce fraudulent orders. Due to the high volume of orders, there is a need for automation of this process. The vetting process involves , checking the customers‘ payment history and depending on the number of open payments, the order can either be approved automatically or must be passed on to a human to do a manual approval. Infrastructure: • Order data is stored in Snowflake • Customer Payment data is available in a legacy CRM system • Ticketing system is Jira Use Case Description Open Orders CRM Credibility Check Tickets for Manual Vetting Flag/unflag order Approve order Update Status and Ticket Number
- 21. Live Demo
- 22. Networking time
- 23. Thank You
Editor's Notes
- #9: https://knowledgehub.mulesoft.com/s/article/Automation-and-Anypoint-Usage-Patterns?_ga=2.201899601.1113425505.1704964560-1297013546.1693830172
- #19: MuleSoft Anypoint Platform customers can share externally available APIs managed in Anypoint Platform with business users for consumption in a MuleSoft Composer flow. Composer organizations are linked to Anypoint organizations. The API must be accessible from the public internet. https://docs.mulesoft.com/composer/ms_composer_prerequisites#api-sharing