ITCanopy

Identify Required Activity Packages: Identify the activity packages needed for integration tasks (e.g., Microsoft Office 365, Salesforce, servicenow, Slack). Install Activity Packages: Ensure you have the latest activity packages installed in UiPath Studio to leverage the most up-to-date features and integrations available. Enable "Use Integration Service " Option: After adding a connector to the workflow, checkmark the "Use Connection" box from the properties panel. This will automatically establish the default connection. Access integration Activities: Go to the "Integrations" section in UiPath Studio and select the relevant category (e.g., "Microsoft office 365 Activities") for your integration needs. Define Input Arguments: Define the necessary input arguments (e.g., UiPath Event, Event connector, Event Object id, Event Object type) to receive information from the Integration Service. Utilize Switch Activity: Implement the Switch a...

UiPath Integration Service is a component of the UiPath Platform, designed to simplify and enhance the automation of third-party applications. As automation continues to play a pivotal role in transforming businesses, it's crucial to establish seamless connections between different systems, providing data exchange and streamlined processes. In this course we'll explore the integration Service's key features, benefits, and functionalities that make it an essential tool for automating processes involving various third-party applications. You can access Integration Service from the ribbon on the left side of Automation Cloud. The main key features of UiPath Integration Service are: Large and Growing Catalog of Pre-built Connectors: The Integration Service offers a wide range of popular, pre-built connectors, making it easier to integrate with various third-party applications. This saves time and effort in setting up connections and simplifies the integration process. Simplifie...

Connector Builder is a powerful feature in UiPath Studio that empowers users to design and use custom connectors. By harnessing the capabilities of Connector Builder, users can effortlessly establish connections between different applications and services. With Connector Builder, you can construct first-class connectors tailored to your specific needs. Connector Builder allows users to interact with the following features: Integration with the Integration Service: The Connector Builder experience will be seamlessly integrated into the Integration Service, enabling users to create and utilize custom connectors directly from UiPath Studio. Custom Connectors in Studio Web Automation Cloud: Users will have the capability to use their custom connectors in the Studio Web Automation Cloud, providing them with flexibility and access to their connectors from anywhere. Publishing and Sharing Custom Connectors: Automation Cloud will include the Connector Builder feature, empowering users to publi...

Triggers are essential for automating processes based on specific events, such as new file creation, email receipt, or database updates. By setting up triggers, we can streamline processes, save time, and reduce errors. Triggers provide a mechanism for subscribing to specific events from third-party apps, which are passed through the connections. For example, a trigger can initiate an automation such as: Email Received: an automation can be triggered when a user receives a new email in their inbox. Form Submission: an automation can be triggered when a user submits a form on a website. New File Uploaded: an automation can be triggered when a new file is uploaded to a cloud storage service. Payment Received : an automation can be triggered when the inventory level of a product falls below a certain quantity. These are just a few examples, and there are countless other possibilities depending on the integrations and events supported by the third-party apps and automation platforms you ar...

Consider a scenario where a team is assigned to develop several processes using UI Automation on the same target application. It is expected that the target application will be upgraded in the future and your team needs a method to quickly update the projects when it happens. In order to resolve this issue, object repositories were introduced in 2020.10. These repositories can quickly fix the issue within a few minutes if the application's upgrade in the future. What is Object Repository? The Object Repository allows for creating and reusing UI taxonomies inside and across automation projects. With Object Repository you can build a UI API for your application and share it with your team within minutes. Object Repository's key features Object repositories in Studio provide the following features: 1. Centralized Storage Object repositories allow you to store and manage reusable components, activities, and workflows so they are easy to access, update, and maintain. 2. Reusability ...

Libraries and Templates in Orchestrator Orchestrator can also be used to store libraries and templates so that they can be used again and again for  reusability among other features that include automation and robot management. Orchestrator is a tool that all developers within a company can use to share development assets and make sure the right versions are being used. Storage Buckets Lesson covers Storage Buckets which provide a per-folder storage solution for RPA developers to leverage in creating automation projects.A Storage Bucket is created within a folder, so you can control access to it and its contents with fine-grained permissions and role assignment models. Main Takeaways What are Storage Buckets? Storage Buckets are Orchestrator entities used for storing files which can be used in automation projects. UiPath Studio offers a set of activities to simplify working with Storage Buckets. These activities are available in the UiPath.System.Activities pack, under Orchestrator...

Orchestrator is the component of the UiPath Platform for managing automations, robots, and the related entities. Although it comes with different cloud and on-premises delivery options, including persistence, high availability, and disaster recovery, users can access it through a simple web interface. Orchestrator offers role-based access control and a structure of tenants and folders to replicate organizational structures. Users can run the automation workflows developed in Studio and published to Orchestrator using the unattended robot workforce. Furthermore, Orchestrator is used to manage and distribute licenses, as well as to store automation resources. A single Orchestrator instance can be split into multiple Tenants. Each tenant in an organization can be further subdivided and organized into Folders. Tenants are designed for the purpose of complete isolation of all Orchestrator entities (i.e., Robots, Assets, Queues, etc.) between these segregated instances of your deployment, al...

What is logging? Logging can be defined as the process of recording events or actions that occur during the execution of a workflow. It involves creating log messages that contain details such as process start/end, timestamps, error messages, severity levels of messages, user inputs, or any other information relevant to an action and then storing them in a Log file. Effective logging practice is an essential part of developing automation as it helps understand the flow of execution of workflows and identify the cause of errors or unexpected behaviors. Types of logs in UiPath Before we learn how to set up logs that are useful when developing projects, let's first start by checking out the main types of logs generated by the UiPath Platform: Studio logs. Setup Logs Orchestrator diagnostic logs. Robot Logs Robot logs There are two types of Robot logs: Robot execution logs : These are messages generated by the execution of a process and contain information related to its behavior and u...

What's File and Folder Automation? File and Folder Automation involves automating tasks you do with your files and folders on your computer, like creating, copying, or renaming them. Studio offers a number of activities that help users automate tasks having to do with files and folders. Check out below what you can most commonly do with them: Copy copying a file or a folder from a specified location to another with the "Copy File" and "Copy Folder" activities. Create create an empty file in a specified location or a folder in a specified location with the "Create File" and "Create Folder" activities. Delete delete a file or folder with the "Delete File" and "Delete Folder" activities. Move the "Move File" and "Move Folder" activities allow you to move a file or a folder, giving you the option to overwrite duplicates. Rename with the "Rename File" and "Rename Folder" actions, you can ...

The Try Catch activity catches a specified exception type in a sequence or activity, and either displays an error notification or dismisses it and continues the execution. As a mechanism, Try Catch runs the activities in the Try block and, if an error takes place, executes the activities in the Catches block. The Finally block is only executed when no exceptions are thrown or when an exception is caught and handled in the Catches block (without being re-thrown). Don'ts While the Try Catch activity can be helpful, it's important to avoid excessive usage. Catching an exception should only be done when there's a valid reason to do so. Typically, the Catch block is responsible for handling the exception and enabling error recovery. However, there are instances where an exception is caught performing certain actions, for the purpose of logging it, before being re thrown to higher levels. Here are a few examples where the Try Catch activity shouldn't be used: When dealing wit...

The Retry Scope activity allows you to repeat the execution of enclosed activities as long as a specific condition isn't met or an error is encountered. The purpose of the Retry Scope activity is to catch and handle errors, similar to the TryCatch activity. However, the key difference is that Retry Scope focuses on retrying the execution of activities rather than providing a more complex error handling mechanism. It simplifies the process by automatically retrying the activities until the condition is met or an error is thrown. This activity is a powerful tool in cases where exceptions are thrown sporadically and other measures, like tuning selectors, already took place. For example, a particular selector isn't found in a certain application in less than 5% of the time the workflow runs, but no further selector improvements are possible. Using Retry Scope in this scenario will make the robot try to access the selector again in case a SelectorNotFoundException is thrown. The Ret...

System and Business exceptions Errors are events that occur in a program and can't be handled normally. On the other hand, exceptions are events that are recognized, categorized, and handled by the program. Errors are events that a particular program can’t normally deal with. There are different types of errors, based on what's causing them—for example: Syntax errors, where the compiler/interpreter can't parse the written code into meaningful computer instructions. User errors, where the software determines that the user’s input isn't acceptable for some reason. Programming errors, where the program contains no syntax errors but doesn't produce the expected results. These types of errors are often called bugs. Exceptions are events that are recognized (caught) by the program, categorized, and handled. More specifically, there is a routine configured by the developer that is activated when an exception is caught. Sometimes, the handling mechanism can be simply stoppi...