Figure 1

Configuration-->Deployment

Mandatory Headers

Program and Project names are mandatory.So are the Comments.The grid comprising the list of configurations is given a new look with a new color. 

Figure 2

Figure 1

Sub-menu has been changed.It goes by the new name-Deployment Rollback. The same is reflected in the page.Comments are mandatory.

Figure 2

Figure 1

Configuration-->User Queue Access

New Fields

The following sections have been added in this version.

There are two types of reports, namely, Transactions and TAT reports. In this section we will see what information can be gleaned from Transactions Report.

One can run the workflow in Live and UAT environments, using the Run sub-menu and the details follow.

The machines provisioned for a particular program will be used to execute the projects mapped under the tenant.  If the user decides to cross -utilize or use the machine to execute projects of a different tenant, he has to unassign the machine from the provisioned tenant. 

When workflows are created in the Designer that require a DLL, it should be loaded against a specific project or it can be made available to all the projects.

This section explains the actions that can be taken on robots that are in various statuses and how to check their statuses.

Program-wise robot monitoring can be executed using this sub-menu.

You can easily manage projects by using the Project Management's sub-menus that are available in the Asset Management menu.