UiPath Veterans RPA Studio track program -Session 4: Advanced practices with Studio and Orchestrator
- 1. UiPath Community Veterans program Serving those who served. Session #4: Advanced practices with Studio and Orchestrator
- 2. UiPath MVP, RPA CoE Lead Jeremy Gilliland Senior Community Marketing Manager – AMER, UiPath Diana Gray Director of Intelligent Automation UiPath MVP, Anika Systems Chris Bolin 5x UiPath MVP, Operational Excellence Partnership Lead, Centric Consulting Tracy Dixon Today’s Panel Pradeep Shukla Chief Technologist Peraton
- 3. 3 Agenda Chapter #1: •Basic String Manipulation •Debugging and error handling in Studio •Demo Chapter #2: •Send Email using Automation •Leveraging Orchestrator Assets •Making use of Orchestrator Queues •How to publish a project in Studio •Deployment to Orchestrator •End to End Demo
- 4. 4 Chapter #1: •Basic String Manipulation •Debugging and error handling in Studio •Demo
- 5. 5 Manipulating the data as per the requirement is the need of the business and is used in every project. There are various functions available in VB.NET that help to manipulate the data very easily as per our needs. String Manipulation Example: Extract the author's name and book names from the Initial Message using string methods and display them using the message box.
- 6. 6 String Manipulation: common methods Some of the commonly used string manipulation methods are demonstrated using the example below. Example: MyText = “Test example ” Method Syntax Output Trim MyText.Trim “Test example” ToLower/ToUpper MyText.Trim.ToUpper “TEST EXAMPLE” Split MyText.Trim.Split(“ ”c) {“Test”, “example”} Contains MyText.Contains(“example”) True Length MyText.Trim.Length 12 EndsWith/StartsWith MyText.StartsWith(“Test”) True Substring MyText.Substring(5) “example ” Replace MyText.Replace(“Test”, “Hello”) “Hello example ”
- 7. 7 String Manipulation: common activities
- 8. 8 Debugging, Error Handling in Studio
- 9. 9 Debugging in Studio: Debugging actions • Debugging is the process of identifying and removing errors that prevent a project from functioning correctly. • It is recommended to perform debugging during the design stage of the automation project, at activity, file and project level. Execution Trail When enabled, it shows the exact execution path at debugging. It marks and highlights each Activity in the designer panel during execution. Highlight Elements If enabled, UI elements are highlighted during debugging. Log Activities If enabled, debugged activities are displayed as Trace logs in the Output panel. Continue on Exception When enabled, the Continue on Exception button logs thrown exceptions as they happen and yet continues the execution. Picture in Picture Once enabled, whenever we click Run or Run file, Debug or Debug file, the process starts in a picture in picture session. Remote Debugging Remote debugging lets us run, and debug attended and unattended processes on robots deployed to remote machines. Slow Step While enabled, it decreases the execution speed, letting us take a closer look at activities during debugging. Profile Execution Profile Execution helps us identify performance issues in workflow executions. Open Logs The Open Logs button will open the logs folder where the logs are stored locally.
- 10. 10 Debugging in Studio: Debugging actions (Contd.) Step Out This action is used for stepping out and pausing the execution at the level of the current container. Restart The action is used for restarting the debugging process from the first activity of the project. Step Over This action does not open the current container. When used, it debugs the next activity, highlighting containers without opening them. Step Into Use this activity to debug activities one at a time. Retry Retry re-executes the previous activity and throws the exception if it's encountered again. Ignore This action can be used to ignore an encountered exception and continue the execution from the next activity. Breakpoints Breakpoints are used to purposely pause the debugging process on an activity which may trigger execution issues. Focus This action helps you return to the current breakpoint or the activity that caused an error during debugging.
- 11. 11 Debugging in Studio: Multiple Panels • The Locals panel is only available in debug mode, and it displays exceptions, arguments, variables, properties of the previously executed activity and properties of the current activity. • The Watch panel can be set to display the values of variables or arguments, and values of user- defined expressions that are in scope. • The Immediate panel can be used for inspecting data available at a certain point during debugging • The Call Stack panel displays the next activity to be executed and its parent containers when the project is paused in debugging.
- 12. 12 Error handling techniques ▪ Try Catch activity is used to catch run-time exceptions and to perform the recovery steps. ▪ Throw activity is used to throw an exception, even if it is not generated by an activity. ▪ Rethrow activity is used only inside catch blocks and will throw again the exception that is been initially caught. Use case: In a data validation process, if you encounter invalid data that cannot be processed further, you can use the “Throw” activity to raise a custom exception with a meaningful error message, indicating the issue encountered.
- 14. 14 Chapter #2 •Send Email using Automation •Leveraging Orchestrator Assets •Making use of Orchestrator Queues •How to publish a project in Studio •Deployment to Orchestrator •End to End Demo
- 15. 15 Email automation with Studio Studio provides email automation capabilities through the: Mail Activity Package Microsoft Office 365 Package Google Workspace Activity Package ▪ Once you've enabled APIs and added credentials, you can build automation projects that include Google GSuite activities. ▪ Designed for automating Google Workspace (formerly G Suite) applications. ▪ Supports Google Calendar, Drive, Sheets, Gmail, and Docs automation. ▪ It gives you the ability to automate interactions with Microsoft 365 applications. ▪ By integrating the Microsoft Graph API, the activities allow your robots to: ▪ Manage Outlook calendars ▪ Create and edit Excel workbooks ▪ Manage OneDrive and SharePoint files ▪ Search and send Outlook emails ▪ Manage SharePoint lists ▪ Trigger automations when certain events happen. Facilitates automation of mail- related tasks covering multiple protocols: IMAP, POP3, and SMTP.
- 16. 16 SMTP is used for sending out emails POP3 & IMAP is used for retrieving emails IMAP is more customizable (can get only unread emails, mark emails as read or not ) SMTP POP3 or IMAP Email protocols (SMTP, POP3, IMAP)
- 18. 18 Leveraging Orchestrator Assets #1 Orchestrator Assets are configuration values, which are pulled at runtime by automation solutions. But, why use Assets, when I can just keep the values locally in my automations? Sure, but what data types can Orchestrator Assets store? Okay, but I need a value defined per Robot/Account, so I can’t use Assets, right? 1 2 3
- 19. 19 Leveraging Orchestrator Assets #2 Now that we know what Orchestrator Assets are and why we use them, we need to how we use them. Two main Activities for interacting with Assets: Get Asset Get Credential Though, you can also Set Asset values! 1 2 1 2
- 20. 20 Making use of Orchestrator Queues
- 21. 21 Making use of Orchestrator Queues #1 An Orchestrator Queue is a list of items to be processed by automation solution(s). Orchestrator Queues: Enforce Unique-ness Support Robot Scaling Provide Process Metrics
- 22. 22 Making use of Orchestrator Queues #2 When making use of Queues, a common best practice is to split automation solutions into Dispatchers (shown below) and Performers.
- 23. 23 Making use of Orchestrator Queues #3 With the transaction items added to the Queue, the Performer will begin retrieving items and processing them.
- 24. 24 How to publish a project in Studio
- 25. 25 Publishing a Project in Studio Once you have finished developing an automation solution, you can leverage the publish functionality in Studio to package/push your code to Orchestrator. Publishing: Validation errors will prevent successful publishing.
- 27. 27 Deployment to Orchestrator With our automation solution package in Orchestrator, we need to create a new process and assign it our published package.
- 29. 29 1. Go through the RPA Developer Associate courses on the Academy https://academy.uipath.com/ 2. Re-visit all the Veteran sessions at your own pace: https://community.uipath.com/uipath-community-veterans-program/ 3. Please use the 'UiPath Community Veterans Training Program' dedicated UiPath Forum thread, where you can tag both hosts and mentors for any questions / doubts you may have. Next Steps
- 30. Thank You!