Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

Building Bridges: Merging RPA Processes, UiPath Apps, and Data Service to build Solutions

•
•

This session is focused on the art of application architecture, where we unravel the intricacies of creating a standard, yet dynamic application structure. We'll explore: Essential components of a typical application, emphasizing their roles and interactions. Learn how to connect UiPath RPA Processes, UiPath Apps, and Data Service together to build a stronger app. Gain insights into building more efficient, interconnected, and robust applications in the UiPath ecosystem. Speaker: David Kroll, Director, Product Marketing @Ashling Partners and UiPath MVP

1 of 19
Download to read offline
Building Bridges Merging UiPath Apps, RPA, and Data Service to build Modern Applications
2 Meet today’s speaker: David Kroll Solutions Engineering, Product Marketing, Sales Enablement Recovering Application Developer 2x UiPath MVP with Apps Specialization @ Ashling Partners
3 1. Fundamentals of App Design A. Tour of App Studio Components & Definitions B. How and where they are used, example app makeup 2. Native Compatibility & Architecture A. Diagraming the components B. When should I use Data Service or RPA? C. Data Service Best Practices (in Apps) D. RPA Processes Best Practices (in Apps) 3. Applying the Fundamentals A. Design-time Demo 1. Apps Config 2. Data Service Config 3. RPA Process Config 4. Q&A Agenda Slide
Section 1 Fundamentals of Apps
5 A low code application needs to, at minimum, cover the following areas to be viable in an enterprise. What makes up an “App”? 1. Configurable User Interface (App Studio) 2. Flexible Data Storage (Data Service) 3. Client-Side Processing (Expressions & Attended) 4. Server-Side Processing (Unattended & Queues) 5. Environmental Deployment (Orchestrator) 6. Version Control, Rollback (App Studio) 7. Security and Permissions (Orchestrator + Studio) Security, Permissions, Version Control UI Data Processing Events Events RPA
6 App Studio – Historically, used to add pages with controls, rules on events, or styles Quick Tour COMPONENT MENU CONFIGURE (CONTEXT) ALIGN CONTROLS, LAYOUT, SELECT (CONTEXT) New! Ability to easily integrate Entities, Processes, Storage Buckets, Queues, Action Center, Variables, and Media PREVIEW & DEPLOY
7 Pages – Additional pages within your application (an app usually has multiple pages) • Landing Page, Request Page, Modals Dialogs, etc. Events – Defining logic and rules for application behavior (if-else, set value, start process, etc.) Styles – For each control, use styles to change appearance (ex. make circular red buttons) Controls – Divided into input, container, and display controls • Container (Container, Container Layout, Page Container) • Input – (Textbox, Buttons, Checkboxes, Sliders, Radio Buttons, etc.) • Display (Doc Viewer, Label, List, Table, etc.) UiPath continues to add new and more powerful features that are requested by its customers and community, including the new Data Grid and HTML controls! App Studio Components
8 Application Makeup
9 Example – Page Structure & Container Layout Containers are the magic, super control for application layout, master them, and you will be able to build virtually any design in apps!
10 Example – Display and Input Controls Expression Label Label Image Buttons (with Styles) Label Header Table Label Divider Image
11 Other designs for inspiration
Section 2 Native compatibility & architecture
13 Entity – Connections into UiPath Data Service Entities (create them in Data Service first!) Process – Connections into UiPath Processes (deploy them to Orchestrator first!) Storage Bucket – Store files from your application in cloud storage and tag accordingly Queue – Interact with RPA Queues in orchestrator from your app. Actions (preview) – Embed apps as task forms within Action Center (example: approvals). Variable – Store variables that persist across your application runtime Media – Load media files that you want to show in your app (like images) Native Compatibility
14 High Level Application Architecture User Interface Data Storage Processing & Logic Input Controls Display Controls Container Controls Icons/Styles Events Rules + Expressions Process RPA Entities Data Service Queues RPA Storage Bucket File Storage Variables Runtime Data Actions Action Center Security, Permissions, Version Control Permissions App & Data Service Orchestrator Security & Permissions Version Control App Studio
15 Best Practice: Use Data Service to add native and performant data storage into your app. Apps has native integration with Data Service, meaning you don’t need to call RPA to bring that data onto the App. I always use Data Service in my apps Entities are used: • To store the list of requests being made into your system. • To store associated or relational data between your records (master > child). • To deliver performant and reliable data exchanges within your app. When to use Entities (Data Service)?
16 Best practice: Try to handle logic using Events + VB Expression framework, when requirements go beyond its capabilities, use an RPA process to handle the operation. Examples: 1. Setting up data cleanup logic after you click the “delete draft” button on a draft. 2. Setting up a master workflow process that can be manipulated by arguments (ex “Method” and “RequestID”) 3. Handling API integrations using Integration Service or other pre-built components. But David, why not use RPA and all its power at every turn? Executing the logic within the expressions framework (or native calls to Data Service) is usually more performant than calling a process and waiting for the returned data, but sometimes using a process is necessary. Ask yourself: Does this process need to run and complete before the user can move to the next step or page, or can it be fire-and-forget (with a Queue, for example). When to use Processes (RPA)?
17 New technique: Set up RPA process to continually run while App is running RPA job “waits” for App to send a signal, and when it arrives RPA will immediately deliver the information without having to spin up the process again. Much faster than waiting for RPA jobs to spin up and spin down (shaves about 2-5s off spin up times, most noticeable during multi-process interactions) Look forward to a session on this approach in the near future! Other approaches
DEMO TIME Applying the Fundamentals
Also, anything that I missed that you would like to see in the future? Any questions?

More Related Content

Building Bridges: Merging RPA Processes, UiPath Apps, and Data Service to build Solutions

  • 1. Building Bridges Merging UiPath Apps, RPA, and Data Service to build Modern Applications
  • 2. 2 Meet today’s speaker: David Kroll Solutions Engineering, Product Marketing, Sales Enablement Recovering Application Developer 2x UiPath MVP with Apps Specialization @ Ashling Partners
  • 3. 3 1. Fundamentals of App Design A. Tour of App Studio Components & Definitions B. How and where they are used, example app makeup 2. Native Compatibility & Architecture A. Diagraming the components B. When should I use Data Service or RPA? C. Data Service Best Practices (in Apps) D. RPA Processes Best Practices (in Apps) 3. Applying the Fundamentals A. Design-time Demo 1. Apps Config 2. Data Service Config 3. RPA Process Config 4. Q&A Agenda Slide
  • 5. 5 A low code application needs to, at minimum, cover the following areas to be viable in an enterprise. What makes up an “App”? 1. Configurable User Interface (App Studio) 2. Flexible Data Storage (Data Service) 3. Client-Side Processing (Expressions & Attended) 4. Server-Side Processing (Unattended & Queues) 5. Environmental Deployment (Orchestrator) 6. Version Control, Rollback (App Studio) 7. Security and Permissions (Orchestrator + Studio) Security, Permissions, Version Control UI Data Processing Events Events RPA
  • 6. 6 App Studio – Historically, used to add pages with controls, rules on events, or styles Quick Tour COMPONENT MENU CONFIGURE (CONTEXT) ALIGN CONTROLS, LAYOUT, SELECT (CONTEXT) New! Ability to easily integrate Entities, Processes, Storage Buckets, Queues, Action Center, Variables, and Media PREVIEW & DEPLOY
  • 7. 7 Pages – Additional pages within your application (an app usually has multiple pages) • Landing Page, Request Page, Modals Dialogs, etc. Events – Defining logic and rules for application behavior (if-else, set value, start process, etc.) Styles – For each control, use styles to change appearance (ex. make circular red buttons) Controls – Divided into input, container, and display controls • Container (Container, Container Layout, Page Container) • Input – (Textbox, Buttons, Checkboxes, Sliders, Radio Buttons, etc.) • Display (Doc Viewer, Label, List, Table, etc.) UiPath continues to add new and more powerful features that are requested by its customers and community, including the new Data Grid and HTML controls! App Studio Components
  • 9. 9 Example – Page Structure & Container Layout Containers are the magic, super control for application layout, master them, and you will be able to build virtually any design in apps!
  • 10. 10 Example – Display and Input Controls Expression Label Label Image Buttons (with Styles) Label Header Table Label Divider Image
  • 11. 11 Other designs for inspiration
  • 13. 13 Entity – Connections into UiPath Data Service Entities (create them in Data Service first!) Process – Connections into UiPath Processes (deploy them to Orchestrator first!) Storage Bucket – Store files from your application in cloud storage and tag accordingly Queue – Interact with RPA Queues in orchestrator from your app. Actions (preview) – Embed apps as task forms within Action Center (example: approvals). Variable – Store variables that persist across your application runtime Media – Load media files that you want to show in your app (like images) Native Compatibility
  • 14. 14 High Level Application Architecture User Interface Data Storage Processing & Logic Input Controls Display Controls Container Controls Icons/Styles Events Rules + Expressions Process RPA Entities Data Service Queues RPA Storage Bucket File Storage Variables Runtime Data Actions Action Center Security, Permissions, Version Control Permissions App & Data Service Orchestrator Security & Permissions Version Control App Studio
  • 15. 15 Best Practice: Use Data Service to add native and performant data storage into your app. Apps has native integration with Data Service, meaning you don’t need to call RPA to bring that data onto the App. I always use Data Service in my apps Entities are used: • To store the list of requests being made into your system. • To store associated or relational data between your records (master > child). • To deliver performant and reliable data exchanges within your app. When to use Entities (Data Service)?
  • 16. 16 Best practice: Try to handle logic using Events + VB Expression framework, when requirements go beyond its capabilities, use an RPA process to handle the operation. Examples: 1. Setting up data cleanup logic after you click the “delete draft” button on a draft. 2. Setting up a master workflow process that can be manipulated by arguments (ex “Method” and “RequestID”) 3. Handling API integrations using Integration Service or other pre-built components. But David, why not use RPA and all its power at every turn? Executing the logic within the expressions framework (or native calls to Data Service) is usually more performant than calling a process and waiting for the returned data, but sometimes using a process is necessary. Ask yourself: Does this process need to run and complete before the user can move to the next step or page, or can it be fire-and-forget (with a Queue, for example). When to use Processes (RPA)?
  • 17. 17 New technique: Set up RPA process to continually run while App is running RPA job “waits” for App to send a signal, and when it arrives RPA will immediately deliver the information without having to spin up the process again. Much faster than waiting for RPA jobs to spin up and spin down (shaves about 2-5s off spin up times, most noticeable during multi-process interactions) Look forward to a session on this approach in the near future! Other approaches
  • 18. DEMO TIME Applying the Fundamentals
  • 19. Also, anything that I missed that you would like to see in the future? Any questions?