[MUSIC] Hello and welcome to this demonstration on the user interface of Cloud Orchestrator. So let's begin, the homepage of Orchestrator is divided into two contexts, tenant and folders. The users can switch between these contexts from the sidebar menu. Also, multiple menus are available in Orchestrator for easier access to its functionalities. The my profile and license pages can be accessed through the vertical ellipsis icon on the top right. [MUSIC] The alerts icon displays notifications for robots, que items, triggers, jobs, processes and tasks. The help icon displays a list of links to the Orchestrator guide, community forum, quick tour of Orchestrator submitting an idea and reporting a bug. The create new icon displays a list of shortcuts to various entities of Orchestrator. The search intendant icon enables the user to search for resources in a tenant. Let us understand the tenant context and its entities. The tenant context is used to manage tenant level entities of Orchestrator deployment and Orchestrator settings and licenses. It consists of 12 entities, let's see each of them one by one. The robots page at the tenant level illustrates the robot configuration done in Orchestrator. There is one tab on this page which is configured robots, this tab shows the robot configuration made in modern folders. The folders page shows the folders present in Orchestrator. A folder is a storage area that helps you keep the project separate. There are two tabs on this page the first is folders this tab can be used to create and manage folders in the tenant here, existing folders can be deleted or updated and new folders can be added. The second is personal workspaces, this tab allows you to explore and manage personal workspaces. A workspace is a modern folder available for the dedicated use of a particular attended user. [MUSIC] The monitoring page shows the monitoring solution that gives you real time metrics to help you keep an eye on the health and state of your system. This page contains various sections that can show aggregated data from all your folders such as machines, processes, queues in SLA. The manage access page allows you to view and configure the Orchestrator, users and groups. This page also offers the option to manage users in other services and check permissions for a specific user or group. There are two tabs on this page the first is assigned roles, this tab allows you to manage accounts and groups and check roles and permissions. The second is roles, this tab allows you to define and manage tenant and folder roles. There are two categories of roles that can be added from this tab. The first is tenant role which is used to define a user's access to resources at the tenant level. The second is folder role, which is used to define the users access and ability within their assigned folder. Based on the permissions included there are three types of roles. The first is tenant roles, this role includes tenant permissions and is required for working at the tenant level. The second is folder roles, this role includes permissions for working within a folder. The third is mixed roles, this role includes both types of permissions. The machines page allows you to provision and manage machine entities and use them to connect robots to Orchestrator. This page offers options to add, remove and edit machines, the packages page displays all the projects published from UI Path Studio and the ones that were manually uploaded. It allows you to manage packages across folders centrally there are two tabs on this page. The first is packages, this tab allows you to view and manage packages. It also offers an upload button to add a new package to Orchestrator the second is libraries, this tab shows the libraries that had been published from studio. The audit page displays the audit trail for actions performed by the Orchestrator users. There are two tabs on this page the first is audit, the audit page displaced the audit trail for actions performed by all entities in Orchestrator. The second is test automation audit the test automation audit page displays the audit trail for actions performed by all the test level entities in Orchestrator. The credential stores page allows you to access and manage pretended credential stores. You can create new stores, view existing stores and their properties and delete any current credential store. The web hooks page allows you to integrate the UI Path automation with the entire application ecosystem. It also allows you to set web hooks to connect the Orchestrator events to the application. The web hooks page enables you to easily set them up and view the ones that have been previously created. The license page allows you to manage the licenses across the tenant. Here, you can activate, renew, remove and allocate licenses. You can either require an individual license for one tenant or an aggregated license for multiple. The alerts page displays notifications for robots, que items, triggers, jobs, processes and actions. This page shows alerts from all the folders. Alerts are sent in real time and can have one of the following severity levels, info, success, warn, error or fatal. And can fit in one of the following components, robots, transactions, triggers, jobs, process, actions, queues, folders, personal workspaces and cloud robots. The settings page allows you to configure the Orchestrator application. There are eight tabs on this page, the first is general, this tab allows you to change the time zone enable personal workspaces create roles, enable auto update status for robot machines, account machine mapping and activate classic folders. The second is deployment, this tab allows you to adjust settings for packages and libraries. The third is male, this tab allows you to enable the email alerts make sure that system email notifications have been configured. The fourth is robot security, this tab allows you to specify the number of hours a robot can run offline without checking for its Orchestrator license. The fifth is scalability, this tab allows you to specify if the robot service should subscribe to signal our channels of Orchestrator and configure the transport protocols that work best for you. The sixth is non-working days, this tab allows you to configure calendars of non-working days in which triggers with non-working days restrictions are not launched. The seventh is cloud connections, here, elastic robot orchestration provides a way to automatically scale your unattended robots by allowing UI Path to scale and manage your robots for you in the cloud. Supported cloud providers are Amazon web services, AWS, Google Cloud platform, GCP, Microsoft Azure to host your virtual machines VMs in the cloud for elastic robot orchestration. The eighth is cloud robot images here you can create a snapshot of the machine and use it as the base image for an automation. The shareholders contest selecting systemized and machine image. Now let us understand the folders, context and its entities. The folders context allows you to select any available folder from the sidebar to view and manage that folders entities. The folders context contains a personal workspace folder and regular Orchestrator folders, you can rename it as my workspace, the shared folder is a regular Orchestrator folder. The regular Orchestrator folders are used to collaborate across an organization. These folders are set up by admins with fine grained controls and are shared between multiple users. On the other hand, personal workspaces are used by the owner to implement automation. Only the owner of the Orchestrator account can access it and use it at any time. [MUSIC] Let's see each of them one by one. The homepage gives you a quick overview of Orchestrator entities in the folder. It shows the count off, processes, assets, queues, triggers, users and machines. It also shows the job status, job history and transactions. The automation page allows you to run processes, deploy packages and manage jobs, triggers and logs. There are four tabs on this page, the first is processes, this tab allows you to deploy packages, manage processes and run automation. The second is jobs, this tab allows you to execute and view process runs. The third is triggers, this tab allows you to schedule automatic process runs. The fourth is logs, this tab shows the logs generated by process executions. The monitoring page allows real time monitoring of Orchestrator entities. There are five sections on this page. The first is overview, this section gives you an overview of job status, job history and transactions. The second is machines, this section gives you an overview of machine status. The third is processes this section gives you an overview of process runs outcomes. The fourth is queues this section gives you an overview of queue related details. The fifth is SLA, this section allows you to monitor the evolution of queues SLA metrics. The queues page allows you to create new queues there are two tabs on this page., the first is queues. This tab allows you to add queue items for processing, the second is review requests, this tab shows processed queue items that need further review. The assets page allows you to manage shared credentials or variables used in processes. They allow you to store specific information so that the robots can easily access it. The assets page enables you to create new assets, it also displays all previously created assets which can be edited or deleted. There are four types of asset, the first is text that stores only strings. The second is bull, that supports true or false values, the third is integer, that stores only whole numbers. The fourth is credential that contains user names and passwords that the robot requires to execute processes such as log in details for SAP or Salesforce. The storage buckets page allows you to manage different types of storage solutions integrated with automation. These are used to provide a per folder storage solution for our P. A developers when creating automation projects. The testing page allows you to test automation in Orchestrator to distribute and manage Your tests. There are five tabs on this page. The first is test sets. It allows you to represent a grouping of a number of individual test cases serving particular purposes. For example, full regressions, smoke tests, etcetera across any number of projects. The second is test cases, it allows you to manage test cases across all the projects and application versions. The 3rd is test executions. The test executions served as an immutable record of the execution of any respective test set at a specific point in time. You can re execute test sets after a previous run. The New test case result will override the previous one as shown on the test executions Page. The 4th is test schedules. In test schedules. You can plan and define test execution time intervals. The fifth is test data queues. Test data queues provide a way to store and manage your test data. The test data que acts as a container that holds your queue items ready to be consumed through a set of activities. The queue items are uploaded or removed from the test data que according to a first in first out. FIFA principle The settings page allows you to manage user permissions and machines assigned to the Folder. There are two tabs on this page. The first is manage access This tab allows you to view and manage the Orchestrator users assigned to this folder. The second is machines. This tab shows the machines assigned to this folder. Mm hmm. There is an important folder under the folders context called my workspace. The my workspace folder is a modern folder available for the dedicated use of a particular attended user. As you can see, this folder also has home automation monitoring queues, assets and storage buckets. These entities allow you to do the same thing as the entities in the shared folder. This folder is a personal workspace of the user. Any user with an attendant or modern robot assigned to them can be the owner of a personal workspace, provided this feature was made active by the Orchestrator admin on the respective tenant. With this, we now come to end of the video. It is encouraged that you open Orchestrator to explore and familiarize yourself with the interface. Thank you for watching. Okay.
