UiPath Data Fabric From Data Silos to Unified Flows.pptx

Agenda

1. What is UiPath Data Fabric

2. Why It Matters

3. From Silos to Streams: Solving the Data Fragmentation Problem

4. Live Demo: Using Data Fabric in Real-World Automation

5. Open Q&A + Interactive Discussion

1. From Data Silos to Unified Flows: Explore UiPath Data Fabric to Fuel Automations with Live, Trusted Data

2. Agenda 1. Introduction to UiPath Data Fabric 2. Why It Matters 3. Solving the Data Fragmentation Problem 4. Using Data Fabric in Real-World Automation

3. Enables secure, governed business data storage inside UiPath No need for external databases or custom integrations Provides common entity definitions and relationships Accessible by UiPath workflows, Apps, AI agents What is UiPath Data Fabric

4. What is UiPath Data Fabric

5. Key Capabilities & Features

6. Data Service provided persistent storage & no-code modeling (intro) Data Fabric adds triggers, events, zero-copy integration, stronger agent support Enhanced connectors, tighter integration with AI / Maestro Better performance, scalability, governance Evolution: Data Service → Data Fabric

7. Without Data Fabric Why it Matters

8. Why It Matters Overcomes data fragmentation across systems Removes redundant integrations and duplication Delivers real-time, consistent data to all automations Strengthens governance: centrally manage access and security Enables agent-based and AI workflows with live data (fuel for agents)

9. From Silos to Streams: Solving the Data Fragmentation Problem

10. Architecture / Component Layers

11. Data Fabric connector supports triggers (Record Created, Record Updated) Activities allow CRUD (create, read, update, delete) on records Connector uses internal authentication You don’t need to store extra credentials Operations consume DFUs Connector & Trigger Mechanics

12. Connector & Trigger Mechanics

13. Using Entities in Studio / Workflows You can import entities into Studio as arguments Use Data Fabric activities (e.g., Create Entity Record, Query Entity Records) in workflows You manipulate entity records as objects, not low-level fields Data-driven testing can use Data Fabric entities

14. Data Fabric usage is expressed in Data Fabric Units (DFU) Community license: ~100 MB storage, 500 MB attachments, 1,000 API calls/day Enterprise license: ~1 GB data, 5 GB attachments, 10,000 API calls/day You can allocate more DFU to your tenant Changing license type may require provisioning new Fabric tenant Licensing & Quotas (DFU)

15. Start small: pilot one critical entity Use clear naming conventions Use relationships, not duplication Minimize row-level triggers (only when needed) Monitor DFU consumption Version schema changes carefully Audit and logging Best Practices / Design Patterns

16. 1. Freshdesk Ticket Sync with UiPath Data Fabric Use cases  No Studio or Integration Service required Object-based mapping enables direct data ingestion Supports field joins, transformations, and schema alignment Enables real-time dashboards, queries, and automation triggers

17. 1. Smart HR Onboarding with UiPath Data Fabric Use cases  Unifies data from multiple sources into one governed layer Enables real-time, event-driven automations Acts as a single source of truth for all processes Adds security, access control, and full audit history Scales better than spreadsheets for enterprise data Connects seamlessly with UiPath Apps, AI, and Analytics Drives connected, intelligent automation across departments Google Sheets acts as the input source. Data Fabric becomes the governed system of record for onboarding workflows.

18. Advanced / Deep Features

19. Challenges, Limitations & Considerations DFU limits (quotas) Performance with high-volume data Schema changes and backward compatibility Latency / consistency under load Handling large attachments Governance complexity at scale External source schema changes may require remapping or revalidation in Data Fabric objects

20. Key Takeaways & Next Steps Data Fabric provides unified, governed, real-time data Eliminates redundant integration logic Enables agentic automation with context You can start small and scale Be aware of quotas, schema versioning, and governance

21. Thank you