Recommended
Recommended
More Related Content
Similar to Unleashing the power of AI in UiPath Studio with UiPath Autopilot.
Similar to Unleashing the power of AI in UiPath Studio with UiPath Autopilot. (20)
More from DianaGray10
More from DianaGray10 (20)
Recently uploaded
Recently uploaded (20)
Unleashing the power of AI in UiPath Studio with UiPath Autopilot.
- 1. Unleashing the power of AI in UiPath Studio with UiPath Autopilot March 27th, 2024
- 2. 2 2 About UiPath South California Chapter We are an online and offline community where RPA developers, professionals and enthusiasts: - meet each other and share experiences in the RPA industry - learn together about the challenges they encounter - build projects and components together and expand upon automation ideas
- 3. 3 UiPath Community Marketing Manager, Americas, UiPath Diana Gray Organizers/Team Greg Jacobson Russel Alfeche qBotica, Inc. Tech Leader, RPA Protiviti Senior Manager Intelligent Automation
- 4. Introduction Autopilot for Studio Coded Workflows Q&A Meeting Agenda Coded Automation Autopilot for Studio Web Demo
- 7. Autopilot for Developers – Studio Web
- 8. 8 Demo • Studio Web Workflow Generation • Studio Web Expression Builder
- 9. Autopilot for Developers/Testers – Studio Coded Automation Coded automations allow you to create automations using code instead of drag-and-drop activities, allowing collaborative work on complex projects. In coded workflows and test cases, you can use UiPath services (equal to activity packages), APIs (similar to activities), external .NET NuGet packages, and your custom C# classes in UiPath Studio. This makes it easy to integrate with external systems, databases, APIs, and other services. Coded automations can be of three types: •Coded workflows – used for designing workflows in code. •Coded test cases – used for designing test cases. •Code source files – used for creating code that you can later call in other coded file types.
- 10. Benefits 1.Enhanced productivity – If you’re familiar with coding or scripting you can leverage your skills and increase your productivity. Working within a familiar coding environment allows you to develop more efficient automations. 2.Complexity management – Coded automations provide a flexible solution for managing complex automation scenarios. By using code, you can implement custom logic, manage exceptions, and create reusable functions. 3.Hybrid automation – You can use coded automations interchangeably with low-code automations. This promotes seamless integration between the two approaches, enabling you to create flexible automation solutions. 4.Improved performance – Coded automations empower you to optimize your automation workflows to enhance performance. By using code, you can implement specific algorithms to make your automation executions faster. 5.Readability – Coded automations allow you to create structured code, resulting in code readability. If you organize your code and document it, you can easily maintain it and share it with other collaborators.
- 11. 11 Demo • Coded workflow, source files and test cases • Autopilot Code Generation from Comments
- 12. Coded Workflow/Test Case/Source Files
- 13. Demo – Simple UI Automation using Coded Workflow
- 14. Demo – Interoperability (Coded to Low code & Vice Versa)
- 15. Demo – Default and Custom Services (Service Registration using Source Files) Default Services (Activity Packages) New Services
- 16. Thank you!
- 17. Education Learn RPA Skills - Free Community Software - Academy - Certification - Academic Alliance Support Solve problems - Forum - Documentation - Community Blog - Use Cases Repository - Job Board Network Grow your career - Meetups & DevCon - Mentorship - Hackathons - MVP Program - Automation Champions An ecosystem enabling developer success
- 18. Vibrant ecosystem of more than 1.5 million professionals and citizen developers learning, getting support, and succeeding together in their automation careers. • Start with the free Community Edition to get trained and certified • Then upgrade to the Enterprise version of the product Academy • Get crowdsourced support and share product feedback on UiPath Forum • Check the product documentation • Join the Insider Preview for early testing Forum Community Events • Access the latest articles and video tutorial content created by community members and UiPath engineers in our Community Blog • Contribute as an author. UiPath Community MVPs • Get recognized as a Most Valuable Professional (MVP), Automation Champion or one of the Forum Leaders, based on the contribution to others’ growth Join the UiPath Community • Connect with like-minded people and share best practices with the UiPath Community • Solve challenges in engaging hackathon competitions • Join meetups and conferences Blog and Tutorials Automation Cloud • Learn the skills of the future on UiPath Academy or through our Academic Alliance • Earn globally recognized credentials with UiPath Certifications
Editor's Notes
- C:\Users\RusselAlfeche\OneDrive - QBotica\Documents\UiPath\CodedAutomation
- C:\Users\RusselAlfeche\OneDrive - QBotica\Documents\UiPath\CodedAutomation
- - Method decorators/entry point methods - touch a bit on - input and output arguments - code generation for employee class - inheritance The entry point method for both coded workflows and coded test cases is named Execute() and is attributed as either Workflow or TestCase. You can change the name of the method, as long as you attribute it to either Workflow or TestCase. You can only use one Execute() method ([TestCase] or [Workflow]) inside a file, that inherits the Coded Workflowclass. In this method, you can add input and/or output arguments, which are equivalent to In, Out or In/Out arguments in low-code automations. Go through the Working with Input and Output arguments tutorial to learn how to use arguments in coded automations. This entry point method serves as the starting point for running the automations. This makes coded workflows and test cases easy to identify as entry points due to their Execute() method. Coded automations inherit the CodedWorkflow partial class, creating a relationship of type CodedAutomationExample : CodedWorkflow. This means that the CodedAutomationExample class inherits attributes, methods, and functionality from the CodedWorkflow class. Essentially, it can access and utilize the features defined in the CodedWorkflow class, which provides a foundation for the coded automation, making it easier to build upon and customize the automation's behavior. The CodedWorkflow class is declared as a partial class, allowing you to extend its functionalities by defining the same partial CodedWorkflow class in a code source file. This way, you can add new fields and methods to further customize the behavior of your coded automations. You can use this approach to implement a Before and After interface, specifically for coded test cases. Additionally, the CodedWorkflow partial class inherits the CodedWorkflowBase class.
- C:\Users\RusselAlfeche\OneDrive - QBotica\Documents\UiPath\CodedAutomation Demo1-Workflow.cs Phase 1 - rpa challenge - object repository - simple ui automation - uiautomation options (just show overload methods for now)
- C:\Users\RusselAlfeche\OneDrive - QBotica\Documents\UiPath\CodedAutomation Demo1-Workflow.cs Phase 2 - use challenge.xlsx as an input - input and output arguments - use the employee class for the coded automation, instead of datatable I know we're making this more complicated as it normally would, doing these unnecessary complications, but the purpose of this is to show you when it would make sense to use coded automation vs low code. A good rpa developer would know when to use one vs the other, which in this case I'm not. - low code (readinputexcel.xaml) -> coded (employeesworkflow.cs) - code generation for employeeworkflow class - coded (rpa challenge wf.cs) -> lowcode (readinputexcel.xaml) Phase 3 - typeintooptions Bugs - casting reference types like datable as an output from the lowcode workflow - error when debugging interoperable workflows/coded automation
- C:\Users\RusselAlfeche\OneDrive - QBotica\Documents\UiPath\CodedAutomation - source files - default services - creating new services - openaiservice gpt4-1106-preview model highlight native activity limitation vs openai new model using new service show first readinputexcel.xaml (uncomment generate chat completion activity) then show Demo2-VeryLongContextWorkflow.cs (comment generate chat completion activity in readinputexcel.xaml) - openaiservice image generation and tts model show Demo3-GenerateImage.xaml Coded automations inherit the CodedWorkflow partial class, creating a relationship of type CodedAutomationExample : CodedWorkflow. This means that the CodedAutomationExample class inherits attributes, methods, and functionality from the CodedWorkflow class. Essentially, it can access and utilize the features defined in the CodedWorkflow class, which provides a foundation for the coded automation, making it easier to build upon and customize the automation's behavior. The CodedWorkflow class is declared as a partial class, allowing you to extend its functionalities by defining the same partial CodedWorkflow class in a code source file. This way, you can add new fields and methods to further customize the behavior of your coded automations. You can use this approach to implement a Before and After interface, specifically for coded test cases. Additionally, the CodedWorkflow partial class inherits the CodedWorkflowBase class.