Calgary MuleSoft Meetup APM and IDP .pptx

MuleSoft Meetup on APM and IDP

1. Calgary MuleSoft Meetup Revolutionising the B2B transactions with IDP and Anypoint Partner Manager July 05, 2024

2. Organizers ‹#› Bharath Kesavan Technology Architect Infosys Ishalveer Singh Randhawa Associate Solution Architect Caelius Consulting INC Nitha Joseph Senior MuleSoft Developer PwC Canada

3. ‹#› Speakers for the Session Diljot Singh Priyanshu Dhawan Sr. Solution Consultant Caelius Consulting Sr. Solution Consultant Caelius Consulting

4. A recording of this meetup will be uploaded to events page within 24 hours. Questions can be submitted/asked at any time in the Chat/Questions & Answers Tab. Make it more Interactive!!! Give us feedback! Rate this meetup session by filling feedback form at the end of the day. We Love Feedbacks!!! Its Bread & Butter for our Meetup . Housekeeping ‹#›

5. Land Acknowledgement ‹#›

6. Safe Harbor Statement Speaker and hosts are organizing this meetup in their individual capacity only. We are not representing our companies here. This presentation is strictly for learning purpose only. Organizer(s)/Presenter(s) do not hold any responsibility that same solution will work for your business requirements also. This presentation is not meant for any promotional activities.

7. Agenda Introduction Use Cases Benefits Live Demo Questions ‹#› Features Architecture Use Cases

8. What is B2B?

9. What is Anypoint Partner Manager? Anypoint Partner Manager allows seamless two-way business-to-business message exchanges using APIs and EDI (Electronic Data Interchange) formats, enabling transactions such as buying and selling products with partners. Partner Manager is versatile, supporting various message formats like EDIFACT, X12, JSON, CSV, and XML. These transactions can be securely transmitted through multiple transport protocols, including HTTP(s), SFTP, FTP, and AS2.

10. Features of Anypoint Partner Manager With Anypoint Partner Manager, we can effortlessly: Streamline Partner Onboarding : Simplify the technical onboarding process for our partners. Manage Message Flows : Set up, oversee, and monitor the exchange of business messages between our systems and those of our partners. Boost Operational Efficiency : Track and report on business transactions to enhance our B2B operations. Access Detailed Data : Quickly retrieve metadata, validation errors, and all messages within each transmission payload. Handle Multiple Messages : Efficiently manage transmission payloads containing multiple business messages.

11. EDI Transaction - EDI ‹#›

12. EDI Transaction - JSON ‹#›

13. Prerequisites User Account: Ensure we have an active Anypoint Platform user account with the necessary Partner Manager entitlement. Resource Capacity: Have the required Mule vCore capacity in place to effectively manage your B2B transaction workload. Also, allocate storage for the B2B transmission payloads we'll send or receive. This storage can be in the form of a database, Amazon S3, Azure Blob Storage, or a similar solution. Connector Licenses: Make sure we have the appropriate licenses for the AS2, EDIFACT, or X12 connectors that will be used in your B2B message flows EDI Knowledge: Familiarize ourselves with EDI message formats to effectively work with them Data Transformation: Be equipped with the ability to create DataWeave maps. These maps are instrumental in performing data transformations, a crucial aspect of B2B integration

14. Partner Manager Architecture Experiencing the power of Anypoint Partner Manager, we can deploy B2B integration message flows effortlessly, through the MuleSoft-hosted CloudHub When we deploy a configured message flow, Partner Manager automatically handles the transformation of configurations, deploying and updating the required applications These applications include: Receive Endpoint Service Document Processing Service Replication Service Send Endpoint Service Payload Storage Service ‹#›

15. Partner Manager Architecture

16. Partner Manager Architecture Partner Manager: MuleSoft-hosted cloud control plane empowers users to configure partner profiles, create and deploy B2B Integration message flows and monitor B2B transaction activity Receive Endpoint Service: Services to receive inbound EDI messages from partners through protocols like AS2 and SFTP or outbound application messages from Document Processing Service: Core B2B processing engine responsible for parsing, validating, and translating received B2B messages based on configurations and mapping in Partner Manager API Replication Service: Tracking service responsible for updating transmissions and transaction activities to the control plane and the payload storage API. Send Endpoint Services: Services to deliver transformed inbound application messages to internal applications such as ERP, billing, Order Management via transport protocols like HTTP, HTTPS, or SFTP; or outbound B2B EDI payloads to your partners via AS2, HTTP, HTTPS, or SFTP Payload Storage API: API to store B2B payload data in your storage solution. ‹#›

17. Types of transactions The following transactions can be performed using Anypoint Partner Manager: EDI (Electronic Data Interchange): EDI is general term for the electronic exchange of business documents. EDIFACT (Electronic Data Interchange for Administration, Commerce and Transport): EDIFACT is used by businesses around the world to exchange invoices, purchase orders, and other documents X12 (850/ 810/ 855): X12 is standard for the electronic exchange of business documents JSON (Javascript Object Notation): JSON is a lightweight data-interchange format. It is human-readable and machine-readable CSV (Comma Separated Values): CSV is a plain text format for storing data, which is separated by commas XML(Extensible Markup Language): XML is a markup language that provides rules to define any data

18. X12 850 (Purchase Order) - JSON to EDI An X12 EDI 850 is a type of electronic data interchange transaction set that contains details about an order It is usually sent to a vendor as the first step in the ordering process It can be used both for a single purchase, for recurring purchases, or to delete or amend an order as specified by the buyer. 

19. Replay Transmissions Transmissions can fail due to data validation, mapping, or connectivity issues. If a transmission fails after an Anypoint Partner Manager endpoint secures it, you can replay the transmission. Replaying a transmission regenerates the transmission source and reprocesses the original transmission as a new transmission. You can replay both inbound and outbound transmissions The maximum number of transmissions that you can replay in a single request is 100.

20. Walkthrough of APM on Anypoint Platform

21. Introduction to MuleSoft IDP Fed up with sifting through documents for data? Let’s make it easier with MuleSoft IDP.

22. Some Basic Terms Prompts: Prompts are input sentences or queries provided by users to interact with language models. They request specific information, generate content, or engage in conversation. Prompts typically seek a precise response, task, or generation. Non-Prompts (statements or general queries) : Describe the characteristics of a Black hole. Hi, my name is Josh. Examples of Prompts: Translate to French "Hello, how are you?” Explain the process of photosynthesis.

23. Some Basic Terms Queries : Queries are questions in natural language used to extract specific data from documents. They are used to retrieve precise information like subtotal amounts, due dates, or highest prices. For eg. “What is the subtotal amount?”or “When is the due date?” Analyzers : Analyzers are requests in natural language that allow for deeper examination of documents using AI capabilities. They include tasks suc h as summarizing documents , itemizing purchased elements, identifying document types, or translating documents. For eg. "What is the type of this document?" or "Translate this document to Spanish"

24. Introduction to IDP MuleSoft IDP reads and extracts content from invoices, purchase orders, and other unstructured or semi-structured documents. Utilizing advanced AI, it automates document processing from PDFs and images. The user-friendly IDP interface allows us to create and publish document actions as APIs for seamless integration with Mule applications, RPA and other systems, without needing external services.

25. Architecture of IDP

26. WHY MuleSoft IDP? Cost Effective : Reduces manual data entry and processing costs. Makes data more manageable and easier to utilize in projects compared to other solutions. Powered by Salesforce Einstein : Leverages AI and machine learning for intelligent, accurate data processing, and uses prompts to fetch relevant data in documents. Accessible via REST APIs : Easy integration with a wide range of existing systems and applications. Flexible and Scalable : Adapts to various document types and formats like PDFs and images of purchase order invoices and generic documents, handling large volumes efficiently. Recommended as a Large-Scale Solution : IDP is the most recommended solution as a large-scale solution, offering affordability and effective data retrieval using prompts.

27. Features Of Mulesoft IDP Document Actions : Multi-step process that use AI engines to generate structured JSON responses, defining input types, extracting/filtering fields, and setting confidence thresholds, while configuring prompts for enhanced extraction using natural language. Confidence Scores : Evaluate extraction accuracy with metrics such as 100% indicating total accuracy and 75% suggesting a 25% chance of inaccuracy, triggering human review for low scores. Human Review : Assign reviewers to verify documents based on low confidence scores, ensuring the accuracy and reliability of extracted data. Customization : Create and publish IDP actions to define document schemas for specific processing needs.

28. Features Of Mulesoft IDP Templates : Utilize predefined templates designed for invoices and purchase orders to streamline document processing. Reviews : Queue documents for review if confidence levels are low or essential fields are missing, ensuring thorough validation. Verification : Update document status to SUCCEEDED upon successful validation, confirming accuracy and completion. IDP API : Trigger and query document actions seamlessly using the IDP API, enabling efficient integration and automation.

29. Creating Document Actions in MuleSoft IDP Overview of Document Actions: AI-Driven Processing: Use AI engines for multi-step document processing to generate structured JSON responses. Customization : Define document types, extract and filter fields, and set confidence thresholds. Natural Language Prompts: Utilize natural language prompts for refining data extraction.

30. Creating Document Actions in MuleSoft IDP Ensure necessary Anypoint permissions (Document Action Permissions) are in place Manage Actions : Complete access and default reviewer assignment. Build Actions : Ability to create, edit, and publish document actions. Schema Configuration: Configure the schema by hiding or marking fields as required in the JSON response. Set minimum confidence score thresholds for accurate extraction and customize visibility and validation settings for precise data handling. Upload and Preview: Go to Document Actions and create a new action. Upload up to 10 files (maximum 8 MB each) for initial analysis. Preview results with confidence score indicators.

31. Publishing Document Actions Finalizing Document Actions Save settings to complete document action setup. Add reviewers and publish to Anypoint Exchange for integration with systems. Document Action Versioning Maintain integration compatibility with semantic versioning. Increment minor versions (e.g., from 1.0.0 to 1.1.0) when republishing. Publish a Document Action Steps to Publish Open or create document action in edit mode. Click "Publish," verify asset details, and confirm publication. Asset will be published to Anypoint Exchange as an API for external system integration and await confirmation message before closing.

32. IDP API can be used to streamline automation of data extraction and integrate document actions seamlessly with Mule applications and other systems. Create a c onnected app with client credentials and required scopes to interact with the IDP API and obtain an access token. Executing and Monitoring Document Actions Post documents to IDP via API and retrieve an execution ID in response and we can use this ID to query the execution status. Query status includes ACKNOWLEDGED, IN_PROGRESS, MANUAL_VALIDATION_REQUIRED, FAILED and SUCCEEDED Query the execution status using the execution ID until the document processing status is "SUCCEEDED". Retrieve processed data upon successful completion. Automating Document Processing with IDP API

33. Walkthrough of IDP On Anypoint Platform

34. Use case Architecture

35. DEMO

36. Share: Share using the hashtag #MuleSoftMeetups https://meetups.mulesoft.com/ calgary / Feedback: Fill out the survey feedback and suggest topics for upcoming events Contact MuleSoft at [email protected] for ways to improve the program ‹#› What’s next?

37. Thank You !