# mulesoft RPA Manager - Full Documentation --- product: RPA Manager --- # Admin Settings Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). If you use an RPA account to login to RPA Manager, refer to the [**Organization Management** documentation](https://docs.mulesoft.com/rpa-manager/organizationmanagement-overview). The **Admin Settings View** of the **Settings** module enables you to do the following: - Configure the currency and decimal sign to show in RPA Manager modules. - Reassign the RPA assets of deleted or disabled users. --- product: RPA Manager --- # Alerting Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Manager can alert you in case of errors. You define rules which RPA Manager checks during process run. If a rule applies, an email is sent to the targets you specify. You can check for: - Activity run results - Process run results - Bot status The **Alerts** view shows you all triggered alerts. ## See Also - [View Run Results](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#view-run-results) - [Bot Management](https://docs.mulesoft.com/rpa-manager/botmanagement-overview) - [Creating Alerting Email Templates](https://docs.mulesoft.com/rpa-manager/alerting-target) - [Defining Rules for Alerts](https://docs.mulesoft.com/rpa-manager/alerting-rule) --- product: RPA Manager --- # Analysis Packages > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The **Analysis Packages** widget displays the number of analysis packages of all RPA Bots collected during the analysis interval. **Analysis packages** contain data on the sequence of execution of an individual process element of type **Activity**. **Analysis packages** are normally only created in the event of errors. Bots, for which the option **Analysis Package on OK** is activated in the **RPA Bot Configurator**, create an analysis package for each process element during each run. ## Data Representation The number of analysis packages is a link. ## Configuration This widget cannot be configured. Use the sorting and filter options of the **Analysis Packages** list to highlight the information that is relevant for you. ## Drill-Down Click on the number of all collected analysis packages to obtain a list of all analysis packages listed individually. ### Data Representation of the Analysis Packages The analysis packages are displayed in a list. ### Columns of the **Analysis Packages** List #### Process Name of the process. #### Bot Name of the RPA Bot that carried out configuration of the Process. #### Configuration Name of the Configuration in which the process was executed. #### Category Category to which the Process belongs. #### Type Type of workflow to which the analysis package belongs. ##### Activity Activity workflow. #### Run Type Type of process execution. ##### Test The process was executed during the test phase. ##### Productive The process was executed in production phase. #### Start Time Time stamp of the start of execution of the activity. #### End Time Time stamp of the end of execution of the activity. #### Duration Duration of execution of the activity. #### Result Result of the process execution. ##### Triggered The trigger workflow was executed successfully but there was no task pending. ##### Success The activity workflow was executed successfully. ##### Execution Failure An error occurred during execution of a workflow. #### Download If an analysis package was created, you can download it by clicking on the icon **Download**. --- product: RPA Manager --- # Analyzing Costs and Savings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Enter all expenses for automation of a process. On the basis of the costs of manual execution of the process and the number of process runs already carried out automatically, and the expected future number of monthly process runs, the **Net profit** per month and the expected **Break-Even Point** of the process are calculated. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Finance Analysis view and see all processes for which you are part of the process team.

RPA Performance Analyzer, RPA Operations Manager, RPA Administrator

Finance Analysis Open

Open the Finance Analysis view and see all processes of all teams.

RPA Performance Analyzer, RPA Operations Manager, RPA Administrator

Global Finance Analysis View

Edit finance analyses, add and edit cost entries, and change deprecation periods.

RPA Performance Analyzer, RPA Operations Manager, RPA Administrator

Finance Analysis Edit

- A project must exist in the **Process Automation** module with the following values set in the **Process Costs** tab of the data sheet: - **Cost per process run for manual process execution** - **Frequency per month for manual process execution** - For the Finance Analysis, you require the following values: - Actual and expected number of process runs per month. - Costs of a process run if this is carried out by a human - Initial Investment for acquisition of the MuleSoft RPA solution and all other investments. - Period in months for depreciation of the initial investment and all other investments - Monthly operating costs of process automation ## Add Analysis Data Enter data to calculate the **Net profit** per month and the expected **Break-Even Point** of the process automation. Together with the values that are not displayed here, Actual number of process runs per month and **Cost per process run for manual process execution**, the entries in the **Finance Analysis: Cost entries** panel determine the shape of the curves in the graphics **Break Even Analysis** and **Cost Evaluation**. You can also use the entry options to analyze in which areas changes must be made to maximize the benefits of automation. The changes are shown graphically but are only saved in the detailed view if you Save the data. ### Add Investments Add new investments as soon as they occur. The initial investment is copied from the process data sheet. 1. In the **Finance Analysis** view of the **Process Operations** module, click the icon **Finance Analysis** in the row of the **Process** you want to add investments to. 2. In the panel **Finance Analysis: Cost entries**, click **Add investment**. 3. Complete the form **Finance Analysis: Cost entries**: - **Starting at**: Click on the calendar icon to select the month and year in which the investment was made. - **Total Invest**: Enter the investment amount. - **Deprecation period (in months)**: Specify the duration of the depreciation of the investment in months. 4. Click **OK**. 5. Click **Save**. ### Add Operating Costs The specified monthly operating costs are in each case the total monthly operating costs from the specified month. The previously entered operating costs are only valid in each case until the previous month of the next entry of operating costs. Therefore, the new operating costs replace the old. The initial operating costs are copied from the Process data sheet. Note that any changes to the operating costs shift the date of the break-even point. 1. In the **Finance Analysis** view of the **Process Operations** module, click the icon **Finance Analysis** in the row of the **Process** you want to add investments to. 2. In the panel **Finance Analysis: Cost entries**, click **Add change of operating costs**. 3. Complete the form **Finance Analysis: Cost entries**: - **Starting at**: Click on the calendar icon to select the month and year in which the investment was made. - **Operating costs**: Enter the new monthly operating costs. 4. Click **OK**. 5. Click **Save**. ### Forcast Monthly Process Runs Expected number of automatically executed process runs in the current month and in coming months. This number initially equals the number of manually executed process runs per month so far (Frequency per month for manual process execution), but can be adjusted at any time. Based on past experience, re-estimate the expected number of process runs every month to forecast the break-even time as accurately as possible. ### Set Displayed Number of Months Move the slide control **Months** with the mouse to set the required number of months displayed on the X-axis of the graphics. ## View a Finance Analysis View the graphics **Break-Even Analysis** and **Cost Evaluation**. 1. In the **Finance Analysis** view of the **Process Operations** module, click the icon **Finance Analysis** in the row of the **Process** you want to view. ## See Also - [Starting Automation of Approved Processes](https://docs.mulesoft.com/rpa-manager/myrpa-start) - [Finance Analysis Basics](https://docs.mulesoft.com/rpa-manager/processoperations-financeanalysis-basics) --- product: RPA Manager --- # Approving a Process for Automation > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). You approve an evaluated process candidate to refer it to a project manager or a center of excellence for automation. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Refer a process for automation to a center of excellence.

RPA Evaluations Manager

Process Evaluation Approval to a CoE

Refer a process for automation directly to a project manager.

RPA Evaluations Manager

Process Evaluation Approval to a Project Manager

- You can only approve evaluated process candidates. - You can only refer processes to users assigned the `Project Management` privilege or user groups assigned as `Center of Excellence`. If you use an Anypoint account to login to RPA Manager, user groups are replaced by teams and the Center of Excellence flag is deprecated. Ensure that the team you refer a process to has the required RPA permissions for automating the process. ## Select a Process for Approval You can automate processes that have ratings for feasibility. Consider the benefits before automating a process. Automate simple processes first. 1. Filter the process list in the **Process Evaluation** view of the **Process Evaluation** module to show only newly-created evaluations. 2. View the **Process Matrix**. If you cannot see it, click **Expand** (![less-than symbol in a green half-circle](/mulesoft/current/en-us/rpa-manager/_images/expand-imagebutton.png)). 3. Hover over the dots to see the names of the corresponding processes. 4. Click one of the toggle-dots in the upper right half of the matrix to select it and to display only the corresponding processes. ## Approve a Process Approve the selected process to refer it to a project manager or a center of excellence for automation. After approval, the process is also displayed either in the personal backlog of the project manager (**My RPA** - **My Backlog**) or in the team backlog of the center of excellence (**My RPA** - **Team Backlog**). 1. In the **Process Evaluation** view of the **Process Evaluation** module, click **Approve** in the row of the evaluation you want to approve. 2. Choose a user or a center of excellence as **Project Manager**. 3. Click **OK**. ## See Also - [Considering Which Processes to Automate](https://docs.mulesoft.com/rpa-manager/processevaluation-consider) - [Anypoint Platform Migration Overview](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview) - [Access Management](https://docs.mulesoft.com/access-management/) - [Access Management - Manage User Access Using Teams](https://docs.mulesoft.com/access-management/teams) - [RPA Permissions - RPA Evaluations Manager](https://docs.mulesoft.com/rpa-home/automation-userrolesandpermissions-anypointrpapermissions#rpa-evaluations-manager) - [Starting Automation of Approved Processes](https://docs.mulesoft.com/rpa-manager/myrpa-start) --- product: RPA Manager --- # Assembling Dashboards > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Arrange important widgets on a dashboard. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Dashboard module.

RPA Operations Viewer, RPA Operations Manager, RPA Administrator

Dashboard Open

Manage dashboards.

RPA Operations Manager, RPA Administrator

Dashboard Administration

## Create a Dashboard Create a dashboard that shows you the progress of your automation management within a defined time period on one page. 1. In the **Private Dashboards** view of the **Dashboard** module, click **Create**. 2. Complete the form **Create a Private Dashboard** and click **OK**. 3. In your new dashboard, click **Add Widget** and select one from the Dropdown. 4. Repeat the previous step until you added all necessary widgets. 5. Arrange the widgets by dragging and dropping them onto the dashboard. 6. Configure widgets by clicking on the **Configure** icon. 7. Click on the time frame string in the header of the page to adjust the time interval of the retrieved data. 8. Click **Save** ## Publish a Dashboard Publish a Dashboard to share it with your colleagues. Published dashboards are copied and not synched with the private dashboards they are derived from. 1. In the **Private Dashboard** view of the **Dashboard** module, click the **Publish** icon in the row of the dashboard you want to publish. --- product: RPA Manager --- # Assembling User Groups > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). In automation projects, several employees often work together on one task. These users can be assigned to user groups. User groups can be deployed for processing of user tasks during execution of a process. User groups marked as center of excellence may approve processes for automation. If you use an Anypoint account to login to RPA Manager, Anypoint teams replace the RPA Manager user groups. To function as a center of excellence for approving processes for automation or to complete user tasks, the teams must have the required RPA permissions. To manage teams, refer to the [Anypoint Access Management documentation](https://docs.mulesoft.com/access-management/). In the **User Groups** view in the **User Management** module, you can see all existing user groups. You can create new user groups, check their usage, edit them, and delete them. ## Before You Begin - Ask an administrator to assign you the required privileges:
ActionPrivilege

Open the User Management module.

User Management Open

Create, edit, and delete user groups.

User Group Create, User Group Edit, User Group Delete

## Create a User Group Create a new user group as defined. 1. In the **User Groups** view of the **User Management** module, click **Create**. 2. Complete the form **Create a New User Group**: - **Center of excellence**: Select the **Center of Excellence** checkbox to enable entry of the user group as a project manager for process approvals. - **Available/Assigned Users**: Click on user names to assign them to or remove them from the user group. 3. Click **Save**. ## Edit a User Group Edit a user group to change its function or members. 1. In the **User Groups** view of the **User Management** module, click **Edit** in the row of the user group to edit. 2. Edit the form **Edit User Group**: - **Center of excellence**: Select the **Center of Excellence** checkbox to enable entry of the user group as a project manager for process approvals. - **Available/Assigned Users**: Click on user names to assign them to or remove them from the user group. 3. Click **Save**. ## Delete a User Group Delete user groups no longer needed. Check their usage and reassign their tasks first. 1. In the **User Groups** view of the **User Management** module, click the icon **Usage** in the row of the user group to delete. Proceed only, if the user group is not needed anymore. 2. In the **User Groups** view of the **User Management** module, click **Remove** in the row of the user group to delete. 3. Confirm the deletion. ## Designate User Groups as Centers of Excellence User groups marked as center of excellence may approve processes for automation. You can designate user groups as centers of excellence on creation or edit this property afterwards. 1. In the **User Groups** view of the **User Management** module, click **Edit** in the row of the user group to edit. 2. Edit the form **Edit User Group**: - **Center of excellence**: Select the **Center of Excellence** checkbox to enable entry of the user group as a project manager for process approvals. 3. Click **Save**. --- product: RPA Manager --- # Automation Management > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The **Automation Management** widget shows the progress of your process automation based on the distribution of the projects to the different phases of the lifecycle of a project. You can choose which project categories are to be shown in the graphic. You can also include processes that are still being evaluated. Rename the widget in accordance with the project categories it contains. ## Data Representation The distribution across the phases of the lifecycle is shown as a colored pie chart. In each case, the total number of selected processes for each phase is displayed. ## Configuration Select a single category or multiple categories in sequence from the drop-down list. Select the checkbox **Evaluations included** if you wish to include processes that are still being evaluated. ## Drill-down This widget does not contain any drill-down data. --- product: RPA Manager --- # Bot Management > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Bots are software. They look out for work and automatically carry upcoming processes step by step. They need a computer with the applications required for the processes installed and specific instructions. You manage the bots in the **Bot Management** module. Every bot is assigned to RPA Manager through an API key. After installation, the bot connects to RPA Manager automatically at defined intervals. You can then assign licenses, applications, and service times to the bot. ## Getting Started ### Install 1. Create an API key for each bot before installation. 2. Install each bot on a separate computer, where the applications needed to run the processes are installed. 3. After successful installation, the bots connects to RPA Manager automatically. ### License - After you have installed all bots, open the **Bots** view module and assign _Secure Session_ licenses to each bot that should run processes invisibly. ### Assign Service Times 1. If a bot should only be available to execute processes at certain times, create the corresponding service times in the **Service Times** view module. 2. Assign any number of service times to a bot by editing each bot in the **Bots** view. ### Assign Applications 1. In the **Process Applications** view in the **Process Automation** module, enter all the applications needed to run processes. 2. Assign the applications to the bots that can access them by editing each bot in the **Bots** view. ### Assign Phases - Authorize bots for deployment in the test or production phase by editing each bot in the **Bots** view. ### Create Processes - Create processes in the **Process Evaluation** module and automate them in the **Process Automation** module. ### Deploy Processes - Deploy processes to suitable bots in the process configurations in the **Process Management** view in the **Process Automation** module. ### Monitor - The **Bot Execution Plans** view shows which bot is to execute which processes and when. - The **Process Run Statistics** view shows the results of the processes that have been deployed to the bots. - The **Bot State and Operation** view and the **Deployment Map** view in module **Process Monitoring** shows you what the bots are doing right now. - The widgets **Current Bot Status** and **Bot Workload** can be added to a **Dashboard** in the module of the same name. ## Definitions ### Secure Session A _Secure Session_ is a hidden Windows session that runs invisibly and closed in a separate user account. The screen does not show what is happening or what information is being processed. ## See Also - [Installing RPA Bot](https://docs.mulesoft.com/rpa-bot/latest/installation) - [Configuring RPA Bot](https://docs.mulesoft.com/rpa-bot/latest/configuration) - [Bot Management](#) - [Supporting Bots](https://docs.mulesoft.com/rpa-manager/botmanagement-support) - [Getting to Know Bots](https://docs.mulesoft.com/rpa-manager/botmanagement-know) - [Managing Bots](https://docs.mulesoft.com/rpa-manager/botmanagement-manage) - [Troubleshooting Bots](https://docs.mulesoft.com/rpa-manager/botmanagement-troubleshoot) - [Process Evaluation](https://docs.mulesoft.com/rpa-manager/processevaluation-overview) - [Process Automation](https://docs.mulesoft.com/rpa-manager/processautomation-overview) - [Process Monitoring](https://docs.mulesoft.com/rpa-manager/processmonitoring-overview) --- product: RPA Manager --- # Bot Workload > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The **Bot Workload** widget shows how many of the sessions of an **RPA Bot** are reserved and how many are still free. This gives you an overview of the utilization of the bots and you can allocate resources flexibly. ## Data Representation The workloads of the Bots are displayed as a bar chart. The individual bars have different colors depending on the allocation between free sessions and those reserved for individual production configurations. ## Configuration You can select multiple bots in sequence from the drop-down list. ## Drill-down This widget does not contain any drill-down data. --- product: RPA Manager --- # Business Process Performance > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The **Business Process Performance** widget shows for each process how often the process has been executed within the analysis interval and how long the average execution time was. The number and average runtimes of this widget only take account of processes that have been completed successfully. ## Data Representation The processes are displayed in a list. ### Columns of the List of Business Process Performance of All Processes #### Process Name of the process. Click on the name of a Process to see details of the individual process runs. #### Execution Count Number of successful executions of the Process in the defined time period. #### Average Runtime Average runtime of all successful executions of the Process in the defined time period. ## Configuration This widget cannot be configured. Use the sort and filter options of the **Business Process Performance of an individual Process** list to highlight the information that is relevant for you. ## Drill-down If you click on the name of a Process, you can view details of the individual runs of this Process. ### Data representation of the list of Business Process Performance of an individual Process The Process runs are displayed in a list. ### Columns of the List of Business Process Performance of an Individual Process #### Bot Name of the Bot that executed the Process run successfully. #### Configuration Name of the configuration that was used for the successful run. #### Type Type of Process run. ##### Test The Process was executed as a test run. ##### Productive The Process was executed as a productive run. #### Start Time Time stamp of the start of the Process execution. #### End Time Time stamp of the end of the Process execution. #### Duration Duration of the Process execution. #### Result Result of the process execution. ##### Success The Process run was executed successfully. --- product: RPA Manager --- # Configure General Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). If you use an RPA account to login to RPA Manager, refer to the [**Organization Management** documentation](https://docs.mulesoft.com/rpa-manager/organizationmanagement-settings#configure-currency-and-decimal-sign). The **General** tab in the **Admin Settings** view enables you to configure the currency and decimal sign to show in RPA Manager modules. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

View configured settings for your organization.

RPA Administrator

Organization Management Open

Add or modify settings for your organization.

RPA Administrator

Organization Management Administration

## Configure Currency and Decimal Sign To configure the currency and decimal sign to show in RPA Manager modules: 1. In the **Settings** module, click **Admin Settings**. 2. Ensure that you are in the **General** tab. 3. Configure the following values: - **Currency** The currency symbol that RPA Manager shows in modules and dashboards. - **Decimal Sign** The decimal sign that RPA Manager uses to show fractional numbers in modules and dashboards. 4. Click **Save** --- product: RPA Manager --- # Configure Organization Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). If you use an Anypoint account to login to RPA Manager, refer to the [**Settings** documentation](https://docs.mulesoft.com/rpa-manager/settings-overview). If you use an RPA account to login to RPA Manager, the **Settings** view enables you to configure the currency and decimal sign to show in RPA Manager modules and configure your Anypoint Platform credentials, which enables you to publish a process automation to Anypoint Exchange. ## Before You Begin - Ask an administrator to assign you the required privileges:
ActionPrivilege

View configured settings for your organization.

Organization Management Open

Add or modify settings for your organization.

Organization Management Administration

## Configure Currency and Decimal Sign To configure the currency and decimal sign to show in RPA Manager modules: 1. In the **Organization Management** module, click **Settings**. 2. Ensure you are in the **General** tab. 3. Configure the following values: - **Currency** The currency symbol RPA Manager shows in modules and dashboards. - **Decimal Sign** The decimal sign RPA Manager uses to show fractional numbers in modules and dashboards. 4. Click **Save** ## Configure Anypoint Platform Credentials Before you can connect with your Anypoint Platform account, ensure that you have configured a Connected App in Access Management to enable the RPA Connection. See [Configure a Connected App in Access Management](https://docs.mulesoft.com/rpa-home/publish-process-automation-exchange#configure-connected-app-rpa) for instructions on creating a Connected App. To connect RPA Manager with your Anypoint Platform account: 1. In the **Organization Management** module, click **Settings**. 2. Select the **Anypoint** tab. 3. Click **Configure Settings** and provide the following values: - **Client Id** The Client Id of the Connected App in Access Management. - **Client Secret** The Client Secret of the Connected App in Access Management. - **Domain** The URL of your Anypoint Platform instance you connect to. 4. Click **Next**. 5. Select the **Anypoint Organization** to connect to. 6. Click **Finish**. ## See Also - [Publish a Process Automation to Anypoint Exchange](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#publish-automation) --- product: RPA Manager --- # Configuring Process Evaluations > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Process evaluations are based on templates. Evaluation templates contain criteria to assess the feasibility and benefits of a process’s automation. You create criteria and templates adapted to your needs. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Process Evaluation module.

RPA Evaluations Viewer, RPA Evaluations Contributor, RPA Evaluations Manager, RPA Administrator

Process Evaluation Open

Manage the Process Evaluation module.

RPA Evaluations Contributor, RPA Evaluations Manager, RPA Administrator

Process Evaluation Administration

Open the Evaluation Criteria view.

RPA Evaluations Viewer, RPA Evaluations Contributor, RPA Evaluations Manager, RPA Administrator

Evaluation Criteria Open

Create, change, and delete evaluation criteria.

RPA Evaluations Contributor, RPA Evaluations Manager, RPA Administrator

Evaluation Criteria Create, Evaluation Criteria Edit, Evaluation Criteria Delete

Open the Evaluation Templates view.

RPA Evaluations Viewer, RPA Evaluations Contributor, RPA Evaluations Manager, RPA Administrator

Evaluation Templates Open

Create, change, and delete evaluation criteria.

RPA Evaluations Contributor, RPA Evaluations Manager, RPA Administrator

Evaluation Template Create, Evaluation Template Edit, Evaluation Template Delete

## Manage Process Evaluation Criteria Process evaluation criteria are properties of the process that are used to assess feasibility and benefits of automating a process. They are graded according to the extent to which they are present in the process. You can create, edit, and remove criteria. ### Create Process Evaluation Criteria Create criteria adapted to your processes. 1. In the **Evaluation Criteria** view of the **Process Evaluation** module, click **Create Qualifier** or **Create Benefit**. 2. Complete the form **Create new <\[Qualifier,Benefit\]\]>**: - **Exclude**: Select this checkbox if the criterion can be excluded from a process evaluation. When you create a process evaluation, the same checkbox appears next to the criterion. Excluded criteria are not used in the computation of the rating. - **Gradation**: Move the slide control to the right to increase the number of gradations of the criterion step by step from 2 to 5. You can enter a description for each gradation level. The higher the level, the better the rating for the process automation’s feasibility respectively benefits. 3. Click **Save**. ### Edit Process Evaluation Criteria Edit criteria to make it more useful. RPA Manager does not change process evaluations that are based on a template with edited criterion. The evaluations continue to contain the criterion in its original form. The changed form of the criterion is used in the templates as soon as the changes are saved. 1. In the **Evaluation Criteria** view of the **Process Evaluation** module, click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the row of the criterion to edit. 2. Edit the form **Edit **. 3. Click **Save**. ### Remove Process Evaluation Criteria Remove criteria you no longer use. Process evaluations that have been created before are not changed and continue to contain the criterion even after it is removed. 1. In the **Evaluation Criteria** view of the **Process Evaluation** module, click **Remove** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) in the row of the criterion to delete. 2. Confirm the removal of the criterion from the templates it is used in. ## Manage Process Evaluation Templates Process evaluation templates combine criteria suitable for a specific type of process. You can create, copy, edit, and remove templates. ### Create Process Evaluation Templates Create different templates for different types of processes. Instead of creating a new, empty template, you can also copy and edit an existing template: 1. In the **Evaluation Templates** view of the **Process Evaluation** module click **Create**. 2. Complete the form **Create a new Evaluation Template**: - **Available/Assigned **: Click on a criterion to move it from **Available** to **Assigned** and vice versa. - **Exclude MuleSoft default evaluation criteria**: Select the checkbox to exclude the MuleSoft default criteria from the selection lists. 3. Click **Save**. ### Copy Process Evaluation Templates Copy and edit templates instead to save time. 1. In the **Evaluation Templates** view of the **Process Evaluation** module, click **Copy** (![copy symbol](/mulesoft/current/en-us/rpa-manager/_images/copy-icon.png))in the row of the template you want to copy. 2. Edit the form **Copy an Evaluation Template**. 3. Click **Save**. ### Edit Process Evaluation Templates Edit templates to make them more useful. 1. In the **Evaluation Templates** view of the **Process Evaluation** module, click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the row of the template to edit. 2. Edit the form **Edit an Evaluation Template**. 3. Click **Save**. ### Remove Process Evaluation Templates Remove templates you no longer use. Evaluations of a process that use a removed template are not changed. 1. In the **Evaluation Templates** view of the **Process Evaluation** module, click **Remove** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) in the row of the template to delete. 2. Confirm the removal of the template. ## See Also - [Process Evaluation](https://docs.mulesoft.com/rpa-manager/processevaluation-overview) - [Considering Which Processes to Automate](https://docs.mulesoft.com/rpa-manager/processevaluation-consider) - [Proposing a Process Candidate for Automation](https://docs.mulesoft.com/rpa-manager/processevaluation-propose) - [Approving a Process for Automation](https://docs.mulesoft.com/rpa-manager/processevaluation-approve) --- product: RPA Manager --- # Connecting to RPA Processes from Salesforce Products > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). RPA Manager requires user authentication to integrate RPA processes into other Salesforce products. For example, you can use your API key to configure an RPA connector in a MuleSoft Composer flow. If you use an RPA account to login to RPA Manager, refer to the [**User Management** documentation](https://docs.mulesoft.com/rpa-manager/usermanagement-connect). For security reasons, you can only see and copy an API key on creation. > [!TIP] You can now use > [Connected Apps](https://docs.mulesoft.com/access-management/connected-apps-overview) for a more > secure and scalable authentication method than User API Keys. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

View configured settings for your organization.

RPA Administrator

Organization Management Open

Create, edit, and delete API keys.

RPA Administrator

User API Key Create, User API Key Edit, User API Key Delete

- Users must have an Anypoint Platform account to associate the API key with. - You must have a secure way to transfer the API Key to the user. - Users must have a secure place to store their API key. ## Create a User API Key Create an API key for a user to integrate an RPA process into another Salesforce product. After expiration, the integrated process instance can no longer connect to RPA Manager from other Salesforce products. Edit the API key to move the expiration date. For security reasons, RPA Manager shows the API Key only during creation. Copy the API Key and securely send it to the user. If the user lose an API Key, create a new one. To create a user API key: 1. Open the **User API Keys** view of the **User Management** module. 2. Click **Create**. 3. Complete the form **Create User API Key**: - **User**: Select a user whose identity and permissions are used to connect from another Salesforce products to RPA Manager. - **Expiration Date**: Select an expiration date for the user API key from the calendar. 4. Click **OK**. 5. In the window **Key Created**, click **Copy to clipboard**. 6. Copy the API key to a secure place. 7. Click **Close**. Send the user API key to the user in a secure way. The users can copy their API key into the configuration settings of the Salesforce products into which they want to integrate the RPA processes. ## Edit a User API Key Edit a user API key to change its name, description, or expiration date. If you lost access to an API key, create a new one. To edit a user API key: 1. Open the **User API Keys** view of the **User Management** module. 2. Click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) on the panel of the user API key to edit. 3. Edit the form **Create User API Key**: For an explanation of the properties, see [**Create a User API Key**](#form-createuserapikey). 4. Click **Save**. ## Delete a User API Key Delete a user API key to revoke the user’s REST API access to RPA Manager. Integrated processes that use the deleted API key stop working. To delete a user API key: 1. Open the **User API Keys** view of the **User Management** module. 2. Click **Remove** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) on the panel of the user API key to remove. 3. Confirm the removal. ## See Also - [Access Management](https://docs.mulesoft.com/access-management/) - [Connected Apps](https://docs.mulesoft.com/access-management/connected-apps-overview) - [Create an Invocable Run Configuration](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#invocable-configuration) - [MuleSoft RPA Connector for Composer](https://docs.mulesoft.com/composer/ms_composer_rpa_reference) - [Salesforce: Use Flows with MuleSoft RPA](https://help.salesforce.com/s/articleView?id=platform.flow_build_use_flows_with_mulesoft_rpa.htm&type=5) --- product: RPA Manager --- # Connecting to RPA Processes from Salesforce Products > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). If you use an Anypoint account to login to RPA Manager, refer to the [**Settings** documentation](https://docs.mulesoft.com/rpa-manager/settings-connect). RPA Manager requires user authentication to integrate RPA processes into other Salesforce products. For example, you can use your API key to configure an RPA connector in a MuleSoft Composer flow. For security reasons, you can only see and copy your API key on creation. ## Before You Begin - Ask an administrator to assign you the required privileges:
ActionPrivilege

Open the User Management module.

User Management Open

Create, edit, and delete API keys.

User API Key Create, User API Key Edit, User API Key Delete

- You must have an account in RPA Manager to associate your API key with. - You must have a secure place accessible to store your API key. ## Create a User API Key Create an API key for yourself to integrate an RPA process into another Salesforce product. After expiration, the integrated process instance can no longer connect to RPA Manager from other Salesforce products. Edit the API key to move the expiration date. For security reasons, RPA Manager shows the API Key only during creation. Copy your API Key and save it to a secure place. If you lose an API Key, create a new one. To create a user API key: 1. Open the **User API Keys** view of the **User Management** module. 2. Click **Create**. 3. Complete the form **Create User API Key**: - **User**: Select yourself. Your identity and permissions are used to connect from another Salesforce products to RPA Manager. - **Expiration Date**: Select an expiration date for the user API key from the calendar. 4. Click **OK**. 5. In the window **Key Created!**, click **Copy to clipboard**. 6. Copy the API key to a secure place. 7. Click **Close**. Copy your saved API key into the configuration settings of the Salesforce products into which you want to integrate the RPA processes. ## Edit a User API Key Edit a user API key to change its name, description, or expiration date. If you lost access to your API key, create a new one. To edit a user API key: 1. Open the **User API Keys** view of the **User Management** module. 2. Click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) on the panel of the user API key to edit. 3. Edit the form **Create User API Key**: For an explanation of the properties, see [**Create a User API Key**](#form-createuserapikey). 4. Click **Save**. ## Delete a User API Key Delete a user API key to revoke the user’s REST API access to RPA Manager. Integrated processes that use the deleted API key stop working. To delete a user API key: 1. Open the **User API Keys** view of the **User Management** module. 2. Click **Remove** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) on the panel of the user API key to remove. 3. Confirm the removal. ## See Also - [Create an Invocable Run Configuration](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#invocable-configuration) - [MuleSoft RPA Connector for Composer](https://docs.mulesoft.com/composer/ms_composer_rpa_reference) - [Salesforce: Use Flows with MuleSoft RPA](https://help.salesforce.com/s/articleView?id=platform.flow_build_use_flows_with_mulesoft_rpa.htm&type=5) --- product: RPA Manager --- # Considering Which Processes to Automate > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Consider these aspects before starting robotic process automation: - Standards - Qualifiers - Benefits - Order ## Standards There might be several ways in which your company processes the same task. So before proposing a business process for automation, follow these steps: 1. Collect Ask all employees how they complete a certain task. 2. Compare Compare the answers to get the necessary steps. 3. Compile If possible, compile the necessary steps into one process description and make it a standard in your company. Standardizing business processes helps to prepare automation and avoids automating one task in multiple ways. ## Qualifiers Qualifiers are process properties that help determine whether a process can be automated and how easily this can be done. The more of the following requirements your process meets, the easier it is to automate:
QualifierDescription

Data-driven

Processes based on texts or numbers are easier to automate than processes that require an understanding of images or spoken language.

Rule-based

The better a process can be described using rules, the higher the automation capacity. If a process has both judgement-based parts and rule-based parts, it can be partly automated. The bot carries out the rule-based process parts and waits for human decisions.

Uses structured digital input

If all related documents are available in digital, structured forms, the process automation is easier. You can use the RPA Builder tools to digitize documents.

Stable

You can only automate a process if it always runs predictably, that is, if it is stable.

## Benefits Benefits are process properties that help you determine how useful the automation of a process is for the company.
BenefitDescription

High costs of manual execution

A process is costly if either one manual execution takes a lot of time or if it is carried out very often. Automating an expensive process frees employee time for work that cannot be automated.

Error-prone

Automation that helps prevent errors improves the quality of the process result. Fewer errors lower process costs and increase customer satisfaction.

Risky

Risks include all events and occurrences that can lead to additional costs or losses, such as breaking the law and associated penalties, fraud, loss of customers and sales, the costs of inefficiencies, poor decisions and corrective action, damaging the company’s reputation, illness and the loss of employees. Automation reduces risks.

Use of legacy systems

Automate a process to connect or migrate legacy systems to your state of the art systems.

Speed-sensitive

Automate processes that must finish quickly. Bots work faster than humans.

Occurring irregularly

Processes that occur only in irregular time intervals and vary in volume make inefficient use of employees. Bots wait patiently for their turn and can be scaled according to need in case of peak demand.

## Order Begin with simpler processes to support the learning curve and to produce quick results. You can tackle more complex processes if they are well documented and if experienced designers are available. The more frequently a process is carried out, the higher the costs and the more effective the automation. For this reason, consider both the position of the process in the **Process Matrix** heat map in the view **Process Evaluation**, and the process costs to determine whether and when the process should be automated. ## See Also - [Process Evaluation](https://docs.mulesoft.com/rpa-manager/processevaluation-overview) - [Configuring Process Evaluations](https://docs.mulesoft.com/rpa-manager/processevaluation-configure) - [Proposing a Process Candidate for Automation](https://docs.mulesoft.com/rpa-manager/processevaluation-propose) - [Approving a Process for Automation](https://docs.mulesoft.com/rpa-manager/processevaluation-approve) --- product: RPA Manager --- # Creating Alerting Email Templates > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Create a template for an email to send as an alert. Address the email to users within RPA Manager or to other people that must be aware of problems. Use keywords to extract the relevant information from the incident. Combine targets to target groups to save time when creating alert rules. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Alerting module.

RPA Operations Viewer, RPA Operations Manager, RPA Administrator

Alerting Open

Create, edit, and delete alerting targets and rules.

RPA Operations Manager, RPA Administrator

Alerting Administration

## Create Alert Targets Create a template for an email to send as an alert. Address the email to users within RPA Manager or to other people that must be aware of problems. Use keywords to extract the relevant information from the incident. 1. In the **Alert Targets** view of the **Alerting** module, click **Create**. 2. Complete the form **Create a new email target**: - **Keywords**: Click on the **Keywords** icon to add placeholders to the subject or the body of the email. The placeholders are filled with the actual values when RPA Manager sends the emails. 3. Click **Save**. ## See Also - [Alerting Overview](https://docs.mulesoft.com/rpa-manager/alerting-overview) - [Defining Rules for Alerts](https://docs.mulesoft.com/rpa-manager/alerting-rule) --- product: RPA Manager --- # Current Bot Status > For the full documentation index, see: https://docs.mulesoft.com/llms.txt In the **Current Bot Status** widget, you can see at a glance which of your bots are ready for use. ## Data Representation The numbers of Bots in each case are links displayed together with a graphical representation of the ratio of those Bots ready for use compared to those not ready. The length of the green line labeled with **Ready** corresponds to the number that are ready for use; the length of the red line labeled with **Not Ready** corresponds to the number not ready. ## Configuration This widget cannot be configured. ## Drill-down Click on a number to obtain a list of all Bots or only those Bots with a specific status. ### Data Representation of the Current Bot Status The Bots are displayed in a list. ### Columns of the **Current Bot Status** List #### Status ##### OK The Bot is ready for use. ##### Stopped The Bot is not ready for use because it has been stopped. ##### No License The Bot is not ready for use because it is not licensed. #### Bot Name of the bot. Click on the name of the bot to get to its detailed view. #### Processing Shows if a process configuration has been deployed to the bot. --- product: RPA Manager --- # Dashboard Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The dashboard shows you the progress of your automation management within a defined time period on one page. You arrange widgets on the dashboard. These display the most important data from processes and robots. The data includes, but is not limited to: - The execution frequency and duration of processes - The utilization of the bots - An overview of the used bot minutes - An overview of the lifecycle - Information that helps to distribute resources efficiently - Comparisons between manual and automatic execution times - Analysis packages that provide further information on selected processes For each dashboard, you can select the analysis interval and the refresh rate. You can publish dashboard so that others can use them. Open a dashboard by clicking on its name. --- product: RPA Manager --- # Defining Rules for Alerts > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Specify the incidents that trigger an alert. Each activated rule be checked while configurations are deployed. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Alerting module.

RPA Operations Viewer, RPA Operations Manager, RPA Administrator

Alerting Open

Create, edit, and delete alerting targets and rules.

RPA Operations Manager, RPA Administrator

Alerting Administration

- Appropriate alert targets must exist in the **Alert Target** view. ## Create an Alert Rule Create a rule to trigger an alert. You can create alert rules for these types of incidents: - Activity Run Result Run result of a single bot task. - Process Run Result Run result of a process execution. - Bot Status Status of the bot. The created alert rule is active upon saving. You can deactivate alert rules by clicking the **Deactivate** icon. 1. In the **Alert Rules** view of the **Alerting** module, click **Create**. 2. Select the type of the incident to trigger the alert. 3. Complete the form **Create new rule**. 4. Click **Save**. ## See Also - [Alerting Overview](https://docs.mulesoft.com/rpa-manager/alerting-overview) - [Creating alerting email templates](https://docs.mulesoft.com/rpa-manager/alerting-target) --- product: RPA Manager --- # Deploying Automations > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The third phase of process automation is the **Test** phase. In this phase, you can test the implemented process model in different configurations. You can [transition](https://docs.mulesoft.com/rpa-manager/processautomation-manage#transition-an-automation-project-to-another-phase) back to **Build** phase to change the implementation. When the tests are successful, transition to **Production** phase. The **Production** phase is the final phase in the life cycle of a process. You have three ways to run a process: - Create and deploy a **Scheduled Run Configuration** to run the process automatically at defined times. - Create and publish an **Invocable Run Configuration** to use it within other Salesforce products. - Create an **On-Demand Run Configuration** to start the process run manually. You can’t run processes openly in existing console sessions or run them hidden in Secure Sessions. In console sessions, only one process can run at a time. In Secure Sessions, different processes or several instances of the same process can run in parallel. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Process Automation module.

RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Process Automation Open

- At least one RPA Bot must be installed to deploy or publish a process. - Be aware that bots can reside in different time zones. - If you want to use the values of [global variables](https://docs.mulesoft.com/rpa-manager/processautomation-prepare-deployment-variable) or [credentials](https://docs.mulesoft.com/rpa-manager/processautomation-prepare-deployment-credential) as initial values for activity parameters, an RPA administrator must create them in the **Global Variables** or **Credential Pool** view first. - A project in test or production phase must exist in the **Project Management** view of the **Process Automation** module. - Obtain the needed permissions as a member of the process team in the project data sheet in the **Project Management** view of the **Process Automation** module. - To run a process in an existing console or RDP session, you must deploy it to a bot that is configured for console sessions, and the specified user must be logged in to this session when you deploy the run configuration. If the user is logged in more than once, the bot starts the process in the first session in which the user is logged in. The bot searches for the user in this order: 1. Physical console session 2. RDP session 1 3. RDP session …​ 4. RDP session . > [!WARNING] Bots running an earlier version than 1.2.0 overtake an open console session > without checking if the logged-in user matches the specified user. Don’t close or minimize the console session while the bot executes the process. - To run a process in a hidden session, you must deploy it to a bot configured for Secure Sessions. Before deploying a run configuration on a bot that has only one licensed secure session, don’t disconnect the session, instead sign out the specified user. Don’t sign in to a computer where a bot with one licensed Secure Session is running a process. - RPA Manager requires authentication to integrate RPA processes into other Salesforce products: - Use user API keys to use Salesforce Flows with RPA. - Use Connected Apps to configure an RPA connector in a MuleSoft Composer flow. ## Test a Process Automation Transition the project to the test phase and create test configurations to execute test runs. Test configurations contain start values for the activity parameters defined in RPA Builder, users who process the user tasks, the configuration of the test environment, and the executing bots. Transition the project back to the build phase to change the implementation. ### Transition Process to Test Phase Transition the fully implemented process to test phase for testing: 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of a project to open it. 3. Click **Publish (Test)**. 4. In the window **Release to Test**, add the needed applications. 5. Check **I confirm that the process should be released into the test phase and all responsible persons have agreed.** 6. Click **Release to Test** to confirm the transition. ### Create a Test Configuration To create a test configuration: 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of a project to open it. 3. Click **Create new test plan**. 4. Complete the **Create test plan** wizard: - **Activity Parameter** The activity parameters for each process are created in RPA Builder and are given initial values there. You can overwrite these values with new initial values by double-clicking on the relevant field in the **Value** column. Set a value by entering text or by clicking on a checkbox, and complete your entry by pressing ENTER. Alternatively, you can set the value of an activity parameter by linking it with a global variable. To link the parameter to a variable, click **Link a global activity parameter** (![symbol](/mulesoft/current/en-us/rpa-manager/_images/linkglobalvariable-icon.png)) and select a variable. RPA Manager displays variables of the same type, assigned to the test phase, and only the credentials to which you’re [affiliated](https://docs.mulesoft.com/rpa-manager/processautomation-prepare-deployment-credential#form-create-credential-useraffiliation). If a credential affiliated to another user is already linked, RPA Manager displays a row of stars to hide the data. The variables are typed. You can only enter or link values of the same type. The values entered here are start values, which can be overwritten by other values during the process run. - **User Task** User tasks are elements of a process model, which can’t be processed fully automatically by a bot, but which require the support of a human. Specify which users are to process the user tasks by clicking on the **User Assignment or User Group Assignment** icon. The number of assigned users and user groups is displayed in the table. You can specify both users and user groups at the same time. The user task is then displayed to each specified user until a user reserves it for processing. Select the checkbox **Send email notification to all related users** when the task is ready for processing if you want all specified users to receive an email as soon as they’re supposed to process a user task. This email contains the name of the user task, the process, and the project manager, as well as a prompt to review the pending tasks in the **My RPA** module. - **Execution** Decide whether to carry out the test run in an existing console or RDP session or in a Secure Session, and specify an appropriate user. You can link the user with a global credential variable by clicking on the **Link a credential from credential pool** icon. Use the syntax `domain\username` instead of `username@domain.com` for domain users and `username` for local users, regardless of whether you enter the username manually or link a global credential. Ensure that the bot that you want to execute the process is configured for the execution type, because you can’t save the test configuration otherwise. The bot can overtake the console or RDP session only if the specified user is logged in at runtime. If no user or another user is logged in at runtime, the process run results show the failure **No active session with the user '' could be found on the system**. > [!WARNING] Bots running an earlier version than 1.2.0 overtake an open console session > without checking if the logged-in user matches the specified user. If you want to watch the execution of the process in the **Process Streaming** view of the **Process Monitoring** module or if the process uses elements of the Windows operating system like the start menu or the task bar, check **Enable Taskbar (Start menu, taskbar buttons)**. - **Bots** Select all RPA Bots that are to carry out the test configuration. Select the checkbox **Show bots not enabled in this phase** to also show bots that aren’t intended for use in this phase. When you select a bot, ensure that it’s configured for the required session type, that it’s allowed to be deployed in the relevant phase, and that it can operate the required applications. If one of the selected bots isn’t configured appropriately, RPA Manager displays a notification, and you can’t proceed with the test configuration. Hover the mouse pointer over the info label to display more detailed information about the cause of the warning or error in the form of a tooltip. 5. Click **Finish**. ### Run Tests Run all tests in parallel. RPA Manager shows a warning in case of deployment problems. View the results in the **Test Results** panel: 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of a project to open it. 3. Click **Start tests**. 4. In the window **Select Configuration to deploy**, check all test configurations you want to run. 5. Click **Execute**. ### View Test Results View the test results to decide if the project can transition to production phase. In case of errors, download an analysis package and open it in RPA Builder. To view the test results and to download an analysis package: 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of a project to open it. 3. In the panel **Test Results**, select a time interval and click **Update**. 4. View the run results in the table. 5. If you want details on a result, click a number. 6. In case of errors, click the **Download** icon. ## Deploy a Process Automation Transition the project to the production phase to deploy a run configuration to a bot. The process runs fully automated from now on. Sometimes it’s necessary to start a process manually when something happens that only a human can evaluate. For example, the goods inwards inspection process can only start after the banana delivery ship reaches the pier wall. For this purpose, use the **Run Now** option. You have three ways to run a process: - Create and deploy a **Scheduled Run Configuration** to run the process automatically at defined times. - Create and publish an **Invocable Run Configuration** to use it within other Salesforce products. - Create an **On-Demand Run Configuration** to start the process run manually. You can run processes openly in existing console sessions or hidden in Secure Sessions. In console sessions, only one process can run at a time. In Secure Sessions, different processes or several instances of the same process can run in parallel. Pause or revoke configurations to stop the execution temporarily. Transition the project back to the build phase to change the implementation. You can’t delete projects of processes that a bot has already run productively. ### Transition Process to Production Phase Transition the tested process to production phase for running it fully automatically or for publishing it to Anypoint Exchange: 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of a project to open it. 3. Click **Publish (Production)**. 4. In the window **Release to Production**, add the needed applications. 5. Check **I confirm that the process should be released into the production phase and all responsible persons have agreed.** 6. Click **Release to Production** to confirm the transition. ### Create a Run Configuration A run configuration consists of a name, a description, initial values for the Activity Parameters, one or more bots, and conditions for deployment of the automation with this configuration. There are three types of run configurations: - **Scheduled run configurations** define intervals for the runs. - **Invocable run configurations** are called from other products. Automations can have one invocable run configuration. - **On-demand run configurations** are started manually. You can publish an invocable run configuration after you save it. You can create a new configuration or [copy](#copy-run-config) an existing one. To create a new run configuration: 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of a project to open it. 3. Click **New** > ** Run Configuration**. 4. Complete the **Create production configuration** form. The shown parameters depend on the configuration type: - **Settings** - **Priority** Enter a number between 1 and 200 to specify the priority of the process run. Deployed processes are inserted in a session queue according to their priority. Process configurations with lower numbers are considered higher priority and are executed before configurations of lower priority. Invocable and on-demand run configurations always have highest priority. - **Activity Parameter** The activity parameters for each process are created in RPA Builder and are given initial values there. You can overwrite these values with new initial values by double-clicking on the relevant field in the **Value** column. Set a value by entering text or by clicking on a checkbox, and complete your entry by pressing ENTER. Alternatively, you can set the value of an activity parameter by linking it with a global variable. To link the parameter to a variable, click **Link a global activity parameter** (![link symbol](/mulesoft/current/en-us/rpa-manager/_images/linkglobalvariable-icon.png)) and select a variable. RPA Manager displays variables of the same type, assigned to the production phase, and only the credentials to which you’re [affiliated](https://docs.mulesoft.com/rpa-manager/processautomation-prepare-deployment-credential#form-create-credential-useraffiliation). If a credential affiliated to another user is already linked, RPA Manager displays a row of stars to hide the data. The variables are typed. You can only enter or link values of the same type. The values entered here are start values, which can be overwritten by other values during the process run. - **User Task**: User tasks are elements of a process model that a bot can’t process fully automatically and require human intervention. Specify which users are to process the user tasks by clicking on the **User Assignment** or **User Group Assignment** icon. The table displays the number of assigned users and user groups. You can specify both users and user groups at the same time. The user task is then displayed to each specified user until a user reserves it for processing. Select the checkbox **Send email notification to all related users** when the task is ready for processing if you want all specified users to receive an email as soon as they’re supposed to process a user task. This email contains the name of the user task, the process, and the project manager, as well as a prompt to review the pending tasks in the **My RPA** module. - **Execution**: Decide whether to carry out the productive run in an existing console or RDP session or in a Secure Session, and specify an appropriate user. You can link the user with a global credential variable by clicking on the **Link a credential from credential pool** icon. Use the syntax `domain\username` instead of `username@domain.com` for domain users and `username` for local users, regardless of whether you enter the username manually or link a global credential. Ensure that the bot that you want to execute the process is configured for the execution type, because you can’t save the run configuration otherwise. The bot can overtake the console or RDP session only if the specified user is logged in at runtime. If no user or another user is logged in at runtime, the process run results show the failure **No active session with the user '' could be found on the system**. > [!WARNING] Bots running an earlier version than 1.2.0 overtake an open console session > without checking if the logged-in user matches the specified user. If you want to watch the execution of the process in the **Process Streaming** view of the **Process Monitoring** module or if the process uses elements of the Windows operating system like the start menu or the task bar, check **Enable Taskbar (Start menu, taskbar buttons)**. - **Schedule**: **Note that bots might run in different time zones.** *** You create a schedule without specifying a time zone. The bot you assign the production configuration to executes the process at the specified times in its local time. The time intervals might change, depending on daylight saving time. For example, if you work in Buenos Aires (ART (UTC -3)), specify a schedule that starts at 5:30 AM and ends at 9:30 PM and assign the configuration to three bots installed on computers in Berlin, San Francisco, and Tokyo, the bots don’t execute the processes simultaneously:
BotExecution Time in the Bot’s Local Time ZoneExecution Time in the Buenos Aires User’s Local Time Zone

Berlin bot

5:30 AM - 9:30 PM (Berlin time, (CET (UTC +1)) =

1:30 AM - 5:30 PM (Buenos Aires time (ART (UTC -3)))

San Francisco bot

5:30 AM - 9:30 PM (San Francisco time, (PST (UTC -8)) =

10:30 AM - 2:30 AM (Buenos Aires time (ART (UTC -3)))

Tokyo bot

5:30 AM - 9:30 PM (Tokyo time, JST (UTC +9)) =

5:30 PM - 9:30 AM (Buenos Aires time (ART (UTC -3)))

The bot checks every minute whether it’s within a scheduled time frame and within its service time and whether the required process applications are outside all downtimes. The process isn’t executed if the executing bot is outside its service time or if one or more of the process applications used by the bot are within a downtime. *** Invocable and on-demand run configurations don’t have schedules. For a scheduled run configuration, choose the schedule type: > [!IMPORTANT] Interval and Cron expression scheduling are supported by bots running version > 1.7.0 or later. - **Interval** Enter the interval to repeat the process. The process starts once at the beginning of each interval. The intervals are equidistant in the defined time frame. For example, `Repeat my process every 10 minutes`. If you need a more complex interval, use **Cron expression**. - **Cron expression** Enter a Cron expression to repeat the process. The process starts once at the beginning of each interval. The intervals aren’t equidistant. For example, `Run my process on minutes 3, 11, and 48 of every hour between 08:00 AM and 10:42 PM, only on Monday and Friday, from February to April, and in November`. If you need a simpler interval, use **Interval**. You can use the Cron expression helper to compile the expresssion and check the natural language schedule summary. What is a Cron expression? *** Cron is a widely used standard for describing time and date information. You use a cron expression to define complex intervals, for example, \`Run my process on minutes 3, 11, and 48 of every hour between 08:00 AM and 10:42 PM, only on Monday and Friday, from February to April, and in November. The scheduler keeps track of every minute and starts the process run when the Cron expression matches the bot’s time-date setting. You can trigger the event just once or at regular intervals. A date-time expression in the Cron format used by RPA Manager consists of five required settings in the following order: 1. Minutes (`0`\-`59`) 2. Hours (`0`\-`23`) 3. Day of month (`1`\-`31`) 4. Month (`1`\-`12`) 5. Day of the week (`0`\-`7`), where Sunday is either `0` or `7` The Scheduler component also supports the following special characters: - `*`: All values within the range of valid values. - `-`: Range of values within the range of valid values, for example, `1-3`. - `,`: Additional values within the range of valid values, for example, `1,7`. - `/`: Incremental values within the range of valid values starting with the first specified value, for example, `1/7`. You can set either the day of the week or day of the month, but not both. Replace either the day of the week or day of the month with an asterisk. The Scheduler supports most standard Cron expressions. Here are a few good and bad examples:
ExpressionBehaviorExplanation

5 4 3 2 1

At 04:05 AM on every Monday in every February and (?) on the 3rd of every February

This Cron expression is invalid. You can set either the day of the week or the day of the month, but not both. Replace either the day of the week or the day of the month with an asterisk. If you want to run a process exactly once at a specific time, you must specify the day of the month but not the day of the week. See the next two examples.

5 4 3 2 *

At 04:05 AM on the 3rd of every February

If you want to run a process exactly once at a specific time, you must specify the day of the month but not the day of the week. You can’t specify the year.

5 4 * 2 3

At 04:05 AM on every Wednesday of every February

If you want to run a process exactly once at a specific time, you must specify the day of the month but not the day of the week. You can’t specify the year.

*/7 * * * *

At minute 00, 07, 14, 21, 28, 35, 42, 49, 56 of every hour (of every day of every month on every weekday).

Starts at minute 0 because it’s the first of all values in the valid range (*).

45/05 * * * *

At minutes 45, 50, and 55 of every hour

* * * * *

Every minute forever

* 9-16 * * 1-5

Every minute, between 09:00 AM and 04:59 PM, Monday through Friday

00,10,42 9-16 1-10,20-30 2-7,12 *`

At 0, 10, and 42 minutes past the hour, between 09:00 AM and 04:59 PM, on day 1 through 10 and 20 through 30 of the month, and on Friday, only in February through July and December

You can combine lists and ranges.

Non-existent times, such as 'missing hours' during daylight savings conversion, never match the bot’s time-date setting, causing processes scheduled during the 'missing times' not to run. Times that occur more than once (again, during daylight savings conversion) cause matching processes to run twice. *** - **Calendar Scheduling** Use this option to edit run configurations that already use calendar scheduling. Add one or more fixed schedules within which RPA continuously executes the productive run. For each schedule, define time intervals within which RPA executes the process. RPA Manager combines all schedules to compute the execution times. How does calendar scheduling work? *** You can create multiple overlapping schedules. All schedules together make up a time frame within which the bots may start the process runs continuously. A new process run doesn’t start until all conditions are fulfilled. For this reason, the executing bot checks every minute whether it’s within a service time and whether the required process applications are outside all downtimes. The process isn’t executed if the executing bot is outside its service time or if one or more of the process applications used by the bot are within a downtime. Unless the computer on which the bot is installed crashes or an required application is down, running processes are always completed. When creating new schedules, pay attention to whether the new schedules overlap with schedules of other configurations and ensure that the executing bots have enough free sessions. Otherwise, the bot might skip process runs. Click on the button **Add Schedule** to assign a (further) schedule to this configuration and complete the **Create a new schedule** form: - **From**: Start of the time interval. As of this time, the scheduled action is executed. The start time must not be in the past and it must not be later than the end time. Even if you specify a Repeat on a specific day of the week or month that does not correspond to the start time, the schedule is started at this time anyway. The day specified under Repeat is then taken into account from the first repetition onward. - **To**: End of the time interval. As of this time, the scheduled action is no longer executed. The end time must not be earlier than the start time. If you use the Repeat option, the duration of the time interval is defined by the difference between the From and To times. - **All day**: Select the checkbox **All day** to execute the action throughout the day. It then begins on the first day at 12:00 midnight and stops being executed at 12:00 midnight of the next day (in the case of one-day intervals) or at 12:00 midnight on the day after the last day (in the case of multi-day intervals). - **Repeat**: Select the checkbox **Repeat** if the selected time interval is to be used repeatedly. Then, under **Repeats**, you can choose whether the **From-To** time interval is to be repeated every minute, hourly, daily, weekly, monthly, or yearly. The duration of the contained time interval and the start time are taken into account. The duration of the time interval is defined as the difference between the **From** and **To** times. The **From** time is the start time of the first execution. The start time of repetitions depends on the other set values. To execute the repeats only with reference to the time of day, you should ensure that the start and end dates are identical. If the interval specified covers multiple days, a new multi-day interval begins with every repetition. This can lead to a situation in which the scheduled time interval lasts longer than expected because the full number of days contained in the **From-To** interval is executed once again during the last repetition. With schedules that are not all day, the actions in each repetition are executed for the duration of the interval specified in the **From** and **To** fields. - **Repeat minutely**: If you select **Repeat minutely**, the planned action is executed every minute during the interval specified in the **To** and **From** fields. You can select whether you want to repeat the action every minute or only every _n_\-th minute. _n_ here stands for any integer number between 1 and 59. - **Repeat hourly**: If you select **Repeat hourly**, the planned action is executed hourly during the interval specified via **To** and **From**. You can select whether you want to repeat the action every hour or only every _n_\-th hour, where _n_ here stands for any integer number between 1 and 23. - **Repeat daily**: If you select **Repeat daily**, the planned action is executed daily during the interval specified via **To** and **From**. You can select whether you want to repeat the action every day or only every _n_\-th day. _n_ here stands for any integer number between 1 and 31. - **Repeat weekly**: If you select **Repeat weekly**, the planned action is executed weekly during the interval specified via **To** and **From**. You can select whether you want to repeat the action every week or only every _n_\-th week. _n_ here stands for any integer number between 1 and 52. You can also select the weekday on which the scheduled action is to be executed. - **Repeat monthly**: If you select Repeat monthly, the planned action is executed monthly during the interval specified via **To** and **From**. You can select whether you want to repeat the action every month or only every _n_\-th month. _n_ here stands for any integer number between 1 and 12. You can also choose whether the repeat refers to the day of the month or the day of the week. If the selected day is the last day of a month, you can also choose whether the execution day is always the last day of a month, as the number of days in each month is different. If the selected day is the fourth such weekday of a month, you can also choose whether the execution day is always the fourth or last such weekday of a month, as the number of weeks in each month is different. - **Repeat yearly**: If you select **Repeat yearly**, the planned action is executed annually during the interval specified via **To** and **From**. You can select whether you want to repeat the action every year or only every _n_\-th year. _n_ here stands for any integer number between 1 and 20. - **Ends**: If you select **Never** under Ends, the time period is repeated over and over. If you select **After n occurrences** under **Ends**, the time period is repeated _n_ times. _n_ here stands for any integer number between 1 and 100. If you select **Ends on **, the time interval is no longer repeated after this date. *** - **Bots**: Select all RPA Bots that are to carry out the production configuration. Select the checkbox **Show bots not enabled in this phase** to also show bots that aren’t intended for use in this phase. When you select a bot, ensure that it’s configured for the required session type, that it’s allowed to be deployed in the relevant phase, and that it can operate the required applications. If one of the selected bots isn’t configured appropriately, RPA Manager displays a notification, and you can’t proceed with the configuration. Hover the mouse pointer over the info label to display more detailed information about the cause of the warning or error in the form of a tooltip. Set the number of Secure Sessions for each bot. On-demand run configurations have only one session. 5. Click **Save**. ### Copy a Run Configuration Copy a run configuration if you need to change only a few parameters. You can also copy a scheduled or an invocable run configuration as an on-demand run configuration. To copy a run configuration: 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of a project to open it. 3. Click the **Copy** icon (![copy symbol](/mulesoft/current/en-us/rpa-manager/_images/copy-icon.png)) in the table row of the run configuration to copy. 4. Select the type of the copy. 5. Enter a new name for the copy of the run configuration. The copy contains all assets of the original. For on-demand run configurations, the number of sessions of all bots is set to 1. 6. Click **OK**. You can edit the copy after saving. ### Deploy Configurations Deploy configuration to run them fully automatically in a productive environment: 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of a project to open it. 3. Click **Select action**. 4. From the dropdown, select **Deploy process**. 5. In the window **Select Configuration to deploy**, check all configurations to run. 6. Click **Execute**. ### Run a Configuration Once The configuration to run once must either be invocable or marked as **Start Manually**. See [Create a Run Configuration](#production-configuration). To start the single process run: 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of a project to open it. 3. Click **Select action**. 4. From the dropdown, select **Run once**. 5. In the window **Select Configuration to Run once**, check all configurations to run. 6. Click **Execute**. The run starts directly. If an invocable configuration is triggered at the same time using the same session, the run waits for the invocable run to complete before starting. ### View Run Results View the run results to check if everything runs as predicted. In case of errors, download an analysis package and open it in RPA Builder. You can always transition the project back to build phase. To view the run results and to download an analysis package: 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of a project to open it. 3. In the panel **Run Results**, select a time interval and click **Update**. 4. View the run results in the table. 5. If you want details on a result, click a number. 6. In case of errors, click the **Download** icon. ## Publish a Process Automation Transition the project to the production phase and publish an invocable run configuration to use the process out of MuleSoft RPA, for example with one of the following products: - Anypoint Exchange - MuleSoft Composer - Salesforce Flow via Anypoint Exchange You can’t delete projects once they’re used in production. Deleted invocable run configurations aren’t deleted in Anypoint Exchange. Edited and updated invocable run configurations are published as new versions in Anypoint Exchange. Invocable configurations can run only if the following requirements are met: - The project is in the production phase. - At least one of the assigned bots is in the `OK` state. ### Transition Process to Production Phase Transition the tested process to production phase for running it fully automatically or for publishing it: 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of a project to open it. 3. Click **Publish (Production)**. 4. In the window **Release to Production**, add the needed applications. 5. Check **I confirm that the process should be released into the production phase and all responsible persons have agreed.** 6. Click **Release to Production** to confirm the transition. ### Create an Invocable Run Configuration You can publish an invocable run configuration after you save it. To create an invocable run configuration: 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of a project to open it. 3. Click **New** > **Invocable Run Configuration**. 4. Complete the **Create production configuration** form: - **Activity Parameter**: The activity parameters for each process are created in RPA Builder and given initial values there. You can overwrite these values with new initial values by double-clicking on the relevant field in the **Value** column. Set the value by entering text or by clicking on a checkbox, and complete your entries by pressing ENTER. Alternatively, you can set the values of the activity parameters by linking them with a global variable. To do this, click on the **Link a global activity parameter** icon. Only those variables assigned to the phase are displayed for linking. The variables are typed. You can only enter or link values of the same type. The values entered here are start values, which can be overwritten by other values during the process run. - **User Task**: User tasks are elements of a process model, which can’t be processed fully automatically by a bot, but which require the support of a human. Specify which users are to process the user tasks by clicking on the **User Assignment or User Group Assignment** icon. The number of assigned users and user groups is displayed in the table. You can specify both users and user groups at the same time. The user task is then displayed to each specified user until a user reserves it for processing. Select the checkbox **Send email notification to all related users** when the task is ready for processing if you want all specified users to receive an email as soon as they’re supposed to process a user task. This email contains the name of the user task, the process, and the project manager, as well as a prompt to review the pending tasks in the **My RPA** module. - **Execution**: Decide whether to carry out the invocable run in an existing console or RDP session or in a Secure Session, and specify an appropriate user. You can link the user with a global credential variable by clicking on the **Link a credential from credential pool** icon. Use the syntax `domain\username` instead of `username@domain.com` for domain users and `username` for local users, regardless of whether you enter the username manually or link a global credential. Ensure that the bot that you want to execute the process is configured for the execution type because you can’t save the run configuration otherwise. The bot can overtake the console or RDP session only if the specified user is logged in at runtime. If no user or another user is logged in at runtime, the process run results show the failure **No active session with the user '' could be found on the system**. > [!WARNING] Bots running an earlier version than 1.2.0 overtake an open console session > without checking if the logged-in user matches the specified user. If you want to watch the execution of the process in the **Process Streaming** view of the **Process Monitoring** module or if the process uses elements of the Windows operating system like the start menu or the task bar, check **Enable Taskbar (Start menu, taskbar buttons)**. - **Bots**: Select the RPA Bots to carry out the invocable configuration. Select the checkbox **Show bots not enabled in this phase** to also show bots that aren’t intended for use in this phase. When you select a bot, ensure that it’s configured for the required session type, that it’s allowed to be deployed in the relevant phase, and that it can operate the required applications. If one of the selected bots isn’t configured appropriately, RPA Manager displays a notification, and you can’t proceed with the configuration. Hover the mouse pointer over the info label to display more detailed information about the cause of the warning or error in the form of a tooltip. 5. Click **Save**. ### Publish an Invocable Run Configuration You can publish an invocable run configuration to Anypoint Exchange. To publish an invocable run configuration: 1. Open the **Process Management** view of the **Process Automation** module and click on the category name of your project. 2. Click on the name of a project to open it. 3. Click **Publish** (![cloud with arrow up symbol](/mulesoft/current/en-us/rpa-manager/_images/cloud-upload-icon.png)). 4. Click **Publish to Anypoint**. If you edit your process or project, republish it to Anypoint to create a new version there. ## See Also - [RPA Builder Overview](https://docs.mulesoft.com/rpa-builder/latest/) - [RPA Bot Overview](https://docs.mulesoft.com/rpa-bot/latest/) - [Secure Sessions](https://docs.mulesoft.com/rpa-home/automation-security-securesessions) - [Bot Management](https://docs.mulesoft.com/rpa-manager/botmanagement-overview) - [Connecting to RPA Processes from Salesforce Products](https://docs.mulesoft.com/rpa-manager/settings-connect) - [Connected Apps in Anypoint Platform](https://docs.mulesoft.com/access-management/connected-apps-overview) - [MuleSoft RPA Connector for Composer](https://docs.mulesoft.com/composer/ms_composer_rpa_reference) - [Salesforce: Use Flows with MuleSoft RPA](https://help.salesforce.com/s/articleView?id=platform.flow_build_use_flows_with_mulesoft_rpa.htm&type=5) --- product: RPA Manager --- # Deployment Map > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The deployment map shows the current status of the run configurations. The deployment map only shows run configurations of processes for which you’re a team member. The interrelationships of processes, RPA Bots, and configurations are mapped as a network. You can view and manage all your run configurations in one place: - Switch between test and production configurations. - Switch between hierarchical and star network views. - Filter the bots and configurations by status. - Switch directly to the detailed view of a process or a configuration. - Execute test configurations. - Execute, pause, and stop production configurations. You must manually keep configuration changes in RPA Manager and Anypoint Exchange in sync. Configurations might become out of sync in the following situations: - Invocable run configurations deleted in RPA Manager might still exist in Anypoint Exchange, but the bot can’t run them and they don’t appear in RPA Manager. - Invocable configuration assets deprecated in Anypoint Exchange might still appear in RPA Manager. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

View the process deployment map.

RPA Operations Viewer, RPA Operations Manager, RPA Administrator

Process Deployment Map Open

- You can only view processes for which you’re part of the process team. - To execute, pause, or stop configurations, obtain the needed team member permissions for the respective phase. - You can’t interact with invocable configurations. - The deployment map shows only bots that have configurations deployed. ## Filter Configurations by Status To show a subset of the map, filter the configurations by status. You can use the following filters: - Deployed: Show all process-configuration-bot combinations in which the configuration is deployed. - Undeployed Show all process-configuration-bot combinations in which the configuration is not deployed. - Paused Show all process-configuration-bot combinations in which the configuration is deployed. - Errors and warnings Show all process-configuration-bot combinations in which errors or warnings occur. You can refine the filter results using the same filters again. To filter configurations by status: 1. Open the **Deployment Map** view in the **Process Operations** module. 2. Click **Filter by state**. 3. Select a filter. 4. To refine the result, deselect the filters that you don’t want to use on the shown subset. The deployment map view is updated. To show the complete map again, click **Reset Filters**. ## Manage Configuration Executions The actions **Start**, **Deploy**, **Run Process Now**, **Pause**, **Continue**, and **Revoke process** refer to a single configuration. The action does not change identical configurations that are deployed to a different bot or different configurations that are deployed to the same bot. 1. Open the **Deployment Map** view in the **Process Operations** module. 2. Click on a process configuration element in the network and select the appropriate action from the context menu. ## See Also - [Deploying Automations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy) --- product: RPA Manager --- # Developing Automations > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The first phase of process automation is the **Design** phase. In this phase, the flow of the process is modeled using BPMN. You can create a new model, import a model that has been created with other tools and edit it or record a process with RPA Recorder. As an option, you can have the model tested for formal correctness and completeness while it is being created. This enables you to quickly detect and resolve errors in the structure. The second phase of process automation is the **Build** phase. In the build phase the elements of the process model are filled with concrete instructions in RPA Builder. RPA Bots execute these instructions when a process is deployed to them. As long as the project is in the build phase, it can be seen in the repository of RPA Builder. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Process Automation module.

RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Process Automation Open

Create processes.

RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Process Create

Record processes with RPA Recorder.

RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Process Recording

Implement process projects in RPA Builder

RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Builder Usage

Open and use the activity library in RPA Builder and the bot workflow library in RPA Manager.

RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Activity Library Open

Use and manage the activity library in RPA Builder and the bot workflow library in RPA Manager.

RPA Automations Manager, RPA Administrator

Activity Library Administration

- To record a process, RPA Recorder must be installed and connected to RPA Manager. - To build a process automation, RPA Builder must be installed and connected to RPA Manager. - A project must exist in the **Project Management** view of the **Process Automation** module. - Obtain the needed permissions as a member of the process team in the project data sheet in the **Project Management** view of the **Process Automation** module. ## Design a Process Model Create, record or import a model of the flow of the process using _Business Process Model and Notation (BPMN)_. The process model should include all possible paths and outcomes. You can add documentation to each element of the diagram. ### Model a Process Create a process model by arranging the BPMN elements on the workbench. Each model must consist at least of a **Start Event**, a **Bot Task** or a **User Task** and an **End Event**. All elements must be connected by **Sequence Flows**. RPA Manager automatically checks the syntax of the model. After saving the process model, move the project to the **Build** phase and open it in RPA Builder. The model can be edited in RPA Builder, too. 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of the project to open it. 3. In the panel **Automation**, on the workbench, click on an element to select the next step from the context pad or drag an element from the palette onto the workbench and connect it to the previous step with a **Flow** element. 4. Add documentation 5. Add, edit, and remove elements until the model is finished. 6. On the workbench, click the icon **Save**. ### Record a Process If you record a process the model is prefilled with instructions for RPA Builder to generate code. After saving the recorded process model, move the project to the **Build** phase and open it in RPA Builder. The model can be edited in RPA Builder, too. 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of the project to open it. 3. In the panel **Automation**, on the workbench, click on the icon **Record BPMN** to start RPA Recorder. 4. After recording, click the icon **Save** on the workbench. ### Import a Process Import a process model generated with another BPMN tool. Only the elements shown in the workbench are supported. Importing a model overwrites previously created models. After saving the recorded process model, move the project to the **Build** phase and open it in RPA Builder. The model can be edited in RPA Builder, too. 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of the project to open it. 3. In the panel **Automation**, on the workbench, click on the icon **Import BPMN** to select a file for import. 4. In the palette on the workbench, click the icon **Fit to Viewport** to see the complete model. 5. On the workbench, click the icon **Save**. ## Build a Process In the build phase, use RPA Builder to fill the process model with bot-readable code. ### Open a Process in RPA Builder Publish a project to build phase to open it in RPA Builder. The process is shown in the RPA Builder repository explorer while the project is in the build phase. 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of the project to open it. 3. Click **Publish**. 4. In the window **Release to Build**, add the needed applications. 5. Check **I confirm that the process should be released into the build phase and all responsible persons have agreed.** 6. Click **Release to Build** to confirm the transition. 7. Open RPA Builder. 8. In the explorer pane, in tab **Repository**, click ****. ### View a Process Build in RPA Manager View the project in RPA Manager after the implemented process has been uploaded from RPA Builder. Move the project to **Test** phase to test the build. 1. Open the **Process Management** view of the **Process Automation** module and click on the name of the category of your project. 2. Click on the name of the project to open it. 3. Click on a bot task in the diagram in the **Automation** panel to view the outline of the implementation in the panel **Implementation**. ## See Also - [Camunda BPMN Tutorial](https://camunda.com/bpmn/) - [RPA Recorder Overview](https://docs.mulesoft.com/rpa-recorder/latest/) - [RPA Builder Overview](https://docs.mulesoft.com/rpa-builder/latest/) --- product: RPA Manager --- # Finance Analysis > For the full documentation index, see: https://docs.mulesoft.com/llms.txt In the view **Finance Analysis**, you record, monitor, and analyze the financial aspects of a Process. You can enter all expenses for automation of the process. On the basis of the costs of manual execution of the process and the number of process runs already carried out automatically, and the expected future number of monthly process runs, the **Net profit** per month and the expected **Break-Even Point** of the process are calculated. Costs, savings, net profit, and break-even point are shown in line charts from the time of creation of the process. The data is shown from the start of automation within a configurable time period of a maximum of 60 months. Each change to the raw data is reflected directly in the graphic. This way, you can analyze when the process automation pays for itself. For the Finance Analysis, you require the following values: - Actual and expected number of process runs per month. - Costs of a process run if this is carried out by a human (**Cost per process run for manual process execution**). - Initial Investment for acquisition of the MuleSoft RPA solution and all other investments. - Period in months for depreciation of the initial investment and all other investments (**Depreciation period for initial invest (in month)**). - Monthly operating costs of process automation (**Operating costs**). If these details are incomplete or are missing entirely, incorrect values or no values at all (**n/a**) are displayed in the table. You can see the overview of all processes in the **Processes for finance analysis** view and the overview of a single process in the detailed view. ## See Also - [Finance Analysis Basics](https://docs.mulesoft.com/rpa-manager/processoperations-financeanalysis-basics) - [Analyze Costs and Savings](https://docs.mulesoft.com/rpa-manager/processoperations-financeanalysis-analyze) --- product: RPA Manager --- # Finance Analysis Basics > For the full documentation index, see: https://docs.mulesoft.com/llms.txt ![rpa\_processOperations\_FinanceAnalysis\_Details\_Overview](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_Overview.png) In the view **Finance Analysis**, you record, monitor, and analyze the financial aspects of a Process. You can enter all expenses for automation of the process. On the basis of the costs of manual execution of the process and the number of process runs already carried out automatically, and the expected future number of monthly process runs, the **Net profit** per month and the expected **Break-Even Point** of the process are calculated. Costs, savings, net profit, and break-even point are shown in line charts from the time of creation of the process. The data is shown from the start of automation within a configurable time period of a maximum of 60 months. Each change to the raw data is reflected directly in the graphic. This way, you can analyze when the process automation pays for itself. For the Finance Analysis, you require the following values: - Actual and expected number of process runs per month. - Costs of a process run if this is carried out by a human (**Cost per process run for manual process execution**). - Initial Investment for acquisition of the MuleSoft RPA solution and all other investments. - Period in months for depreciation of the initial investment and all other investments (**Depreciation period for initial invest (in month)**). - Monthly operating costs of process automation (**Operating costs**). If these details are incomplete or are missing entirely, incorrect values or no values at all (**n/a**) are displayed in the table. You can see the overview of all processes in the **Processes for finance analysis** view and the overview of a single process in the detailed view. In this topic fictitious data is used. The data is selected to enable interrelationships to be illustrated and it is not based on actual cases. ## Raw Data ### Process Costs The **Process Costs** consist of the **Investments** in acquisition, set-up, and extension of the MuleSoft RPA solution, spread over the **Depreciation period** and of the monthly **Operating Costs** for the use of the MuleSoft RPA solution. Process costs relate to a full month in each case. You can enter the costs of manual execution of a process in the evaluation of the process under **Costs**. ![rpa\_processOperations\_FinanceAnalysis\_Basics\_Process\_Evaluation\_Costs](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Basics_Process_Evaluation_Costs.png) When a project is created for this process, these costs are copied to the project data sheet under **Process Costs** and can be changed there. ![rpa\_processOperations\_FinanceAnalysis\_Basics\_Process\_Data\_ProcessCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Basics_Process_Data_ProcessCosts.png) In the **Finance Analysis** itself, you can adjust the process costs again if required and you can continue to maintain them. ![rpa\_processOperations\_FinanceAnalysis\_Details\_CostEntries](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_CostEntries.png) ### Number of Process Runs The number of process runs relates to a full month in each case. The number of process runs, for months in the past, equals the number of process runs actually carried out by bots plus the expected number of process runs for the current month and all remaining months. ## Results Data The results data is displayed graphically. It is calculated as follows. ### Fixed Costs Monthly **Fixed Costs** are the total of all depreciation amounts for one month. The monthly fixed costs can always be calculated in advance as the depreciation period has also been determined in advance. These costs can increase if new investments are made. #### Example: Calculation of the Monthly Fixed Costs ![rpa\_processOperations\_FinanceAnalysis\_Details\_MonthlyFixedCosts\_Example\_Investments](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_MonthlyFixedCosts_Example_Investments.png) In this example, an initial investment of 120,000 € was made on May 20 to buy the MuleSoft RPA solution and its environment. The specified depreciation period was 12 months. This resulted in a monthly depreciation amount of 10,000 € for the next 12 months. ![rpa\_processOperations\_FinanceAnalysis\_Details\_MonthlyFixedCosts\_Example\_Initial\_MonthlyFixedCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_MonthlyFixedCosts_Example_Initial_MonthlyFixedCosts.png) In the **Cost Evaluation** graphic, you can see this with the horizontal line at 10,000 €. In March 2021, an additional 10,000 € are invested for an extension of the automation. The depreciation period here is 10 months, which results in a monthly depreciation amount of 1000 €. From March 2021, this amount is added to the total of the monthly fixed costs. ![rpa\_processOperations\_FinanceAnalysis\_Details\_MonthlyFixedCosts\_Example\_Further\_MonthlyFixedCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_MonthlyFixedCosts_Example_Further_MonthlyFixedCosts.png) In the **Cost Evaluation** graphic, this is shown by the fact that the horizontal line rises by 1000 € and is then at 11,000 €. In April 2021, the final part of the initial investment is depreciated. From May 2021, therefore, the monthly fixed costs amount to only 1000 €. ![rpa\_processOperations\_FinanceAnalysis\_Details\_MonthlyFixedCosts\_Example\_FurtherReduced\_MonthlyFixedCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_MonthlyFixedCosts_Example_FurtherReduced_MonthlyFixedCosts.png) In the **Cost Evaluation** graphic, this is shown by the fact that the horizontal line falls by 10,000 € and is then at 1,000 €. ![rpa\_processOperations\_FinanceAnalysis\_Details\_MonthlyFixedCosts\_Example\_Deprecated\_MonthlyFixedCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_MonthlyFixedCosts_Example_Deprecated_MonthlyFixedCosts.png) When the final depreciation amounts of the second investment are posted, then, in our example, there are no longer any monthly fixed costs as of January 2022. The horizontal line in the **Cost Evaluation** graphic continues at 0 until new investments are made. ### Operating Costs The monthly **Operating Costs** are those costs that are incurred every month in addition to the fixed costs. They include rental costs and salaries, for example. You enter these costs in the **Finance Analysis: Cost entries** panel in the detailed view of the **Finance Analysis**. The specified monthly operating costs are in each case the total monthly operating costs from the specified month. The previously entered operating costs are only valid in each case until the previous month of the next entry of operating costs. Therefore, the new operating costs replace the old. ### Total Costs Total monthly costs (**Total Costs** ) equal the total of the monthly fixed costs and the monthly operating costs. #### Example: Calculation of the Total Monthly Costs ![rpa\_processOperations\_FinanceAnalysis\_Details\_MonthlyFixedCosts\_Example\_Investments](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_MonthlyFixedCosts_Example_Investments.png) ![rpa\_processOperations\_FinanceAnalysis\_Details\_MonthlyTotalCosts\_Example\_OperatingCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_MonthlyTotalCosts_Example_OperatingCosts.png) The monthly fixed costs and the monthly operating costs are included in the total monthly costs. ![rpa\_processOperations\_FinanceAnalysis\_Details\_MonthlyTotalCosts\_Example\_InitialTotalCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_MonthlyTotalCosts_Example_InitialTotalCosts.png) In May 2020, the total monthly costs amount to 10,200 €. This amount is calculated from the depreciation amount of 10,000 € and the monthly operating costs of 200 €. ![rpa\_processOperations\_FinanceAnalysis\_Details\_MonthlyTotalCosts\_Example\_1stIncreaseTotalCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_MonthlyTotalCosts_Example_1stIncreaseTotalCosts.png) In September 2020, with unchanged fixed costs, the monthly operating costs increase from 200 € to 500 €. The total monthly costs therefore increase to 10,500 €. ![rpa\_processOperations\_FinanceAnalysis\_Details\_MonthlyTotalCosts\_Example\_SequelTotalCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_MonthlyTotalCosts_Example_SequelTotalCosts.png) From then on, the total monthly costs initially follow the pattern of the fixed costs. ![rpa\_processOperations\_FinanceAnalysis\_Details\_MonthlyTotalCosts\_Example\_2ndIncreaseTotalCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_MonthlyTotalCosts_Example_2ndIncreaseTotalCosts.png) Since the operating costs are doubled in May 2022, the chart continues further above the fixed costs from that date. Since, at this time, all investments are now depreciated, the total costs now equal the operating costs. ### Cumulative Total Costs Cumulative monthly **Total Costs** equal the total of the cumulative monthly total costs of the previous month and the **Total Costs** of the current month. Each month, therefore, the current costs are added to the aggregated costs so far. #### Example: Calculation of the Cumulative Monthly Total Costs ![rpa\_processOperations\_FinanceAnalysis\_Details\_CumulativeTotalCosts\_Example\_InitialTotalCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_CumulativeTotalCosts_Example_InitialTotalCosts.png) Initially, the cumulative total monthly costs equal 10,200 €. ![rpa\_processOperations\_FinanceAnalysis\_Details\_CumulativeTotalCosts\_Example\_CumulativeTotalCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_CumulativeTotalCosts_Example_CumulativeTotalCosts.png) In August 2020, cumulative total costs after 4 months have reached 40,800 €, that is . ![rpa\_processOperations\_FinanceAnalysis\_Details\_CumulativeTotalCosts\_Example\_IncreasedCumulativeTotalCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_CumulativeTotalCosts_Example_IncreasedCumulativeTotalCosts.png) Since, from September 2020, the monthly operating costs increase by 300 €, the cumulative total costs at this point increase to 51,300 € instead of to 51,000 €, that is . ![rpa\_processOperations\_FinanceAnalysis\_Details\_CumulativeTotalCosts\_Example\_IncreasedCumulativeTotalCosts](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_CumulativeTotalCosts_Example_DecreasedCumulativeTotalCosts.png) From the month of March 2021, an additional monthly depreciation amount of 1000 € is added to this. The cumulative costs from this point, therefore, increase a little more, that is, to . In April 2021, the final amount of the initial investment is paid. From May 2021, therefore, the cumulative total costs no longer increase so steeply; they now total . ### Savings The monthly **Savings** achieved through automation are calculated from the total **Number of Process Runs** successfully carried out in one month by bots multiplied by the costs of the one-time manual execution of the process by a human . To calculate the savings, the number of actually executed process runs for each full month in the past is used. For the current month and future months, the expected number is used. #### Example: Calculation of the Process Runs Actually Carried Out If you prefer not to read the number of process runs actually carried out indirectly from the chart, but would rather calculate the number yourself, then open the **Run results** view in the detailed view of the process in **Process Management**. ![rpa\_processOperations\_FinanceAnalysis\_Details\_CostEvaluation\_Example\_Savings\_ProcessRuns\_Total\_Success](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_CostEvaluation_Example_Savings_ProcessRuns_Total_Success.png) Set the interval at a month and add up all entries from the column **Success**. If there are more than 100 executions, you must add the numbers from all pages of the table. This number is multiplied by the process costs to calculate the savings for the month. The data is determined from scratch each time so any change in the process costs leads to a different curve. #### Example: Calculation of the Monthly Savings ![rpa\_processOperations\_FinanceAnalysis\_Details\_CostEvaluation\_Example\_Savings\_ProcessRuns\_ActualAndForecast](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_CostEvaluation_Example_Savings_ProcessRuns_ActualAndForecast.png) In this example, the costs of the one-time execution of the process by a human are 70 €. We are now in May 2020. From the curve, we can see that the process was not carried out in the month of November ( ). In December, the process was carried out fifty times ( ), in January, 200 times ( ), in February, 25 times ( ), in March, 400 times ( ) and in April, 200 times ( ). The expected number of process executions was set at 300. Therefore, the savings from this month onwards equal 21,000 € consistently. As soon as the month of May is complete, the actual number of process executions is used to calculate the savings. ### Cumulative Savings Cumulative monthly **Savings** equal the total of the cumulative monthly savings of the previous month and the savings of the current month . #### Example: Calculation of the Cumulative Monthly Savings ![rpa\_processOperations\_FinanceAnalysis\_Details\_BreakEvenAnalysis\_Example\_Savings\_ProcessRuns\_ActualAndForecast](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_BreakEvenAnalysis_Example_Savings_ProcessRuns_ActualAndForecast.png) In this example, which was also used in the section **Savings**, the process was already executed automatically in the months of November through April. Since the execution of the process is dependent on conditions that cannot be influenced - in this case, for example, fluctuations in the number of book orders - the process was executed a different number of times each month. Since the overall trend was increasing, the forecast of future execution frequency was set to a value that reflects this trend. If the forecast is accurate, the savings grow with each month. To illustrate the situation, the savings achieved each month are added to the cumulative savings of the previous month. From the curve, we can see that in November, there have not yet been any cost savings. In December, the savings amount to 3,500 €, in January, an additional 14,000 € is saved so that the cumulative savings are now 17,500 € ( ), in February, then 19,250 € ( ), in March, 47,250 € ( ), and in April, 61,250 € ( ). As of the month of May, a further 21,000 € is added each month so that the curve climbs linearly from then on. ### Net Profit The monthly **Net Profit** is the result of the savings from automation less the total costs. #### Example: Monthly Net Profit ![rpa\_processOperations\_FinanceAnalysis\_Details\_CostEvaluation\_Example\_NetProfit\_Negative](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_CostEvaluation_Example_NetProfit_Negative.png) As long as the monthly **Total Costs** exceed the monthly **Savings** , the monthly **Net Profit** is negative. ![rpa\_processOperations\_FinanceAnalysis\_Details\_CostEvaluation\_Example\_NetProfit\_Positive](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_CostEvaluation_Example_NetProfit_Positive.png) As soon as the monthly **Savings** exceed the total monthly costs (**Total Costs** ), the monthly **Net Profit** is positive. For this reason, the curves intersect here in the month of April 2021, when the savings exceed the costs for the first time. The break-even point is not reached until later as it relates to the cumulative values. ### Cumulative Net Profit The **Cumulative Net Profit**, , equals the total of the cumulative monthly net profit of the previous month and the net profit of the current month . The cumulative net profit is not shown in any graphic but it is required for calculation of the **Break-Even Point**. ### Break-Even Point The **Break-Even Point** is the first month in which the cumulative net profit is positive - that is, greater than zero. From this point onwards, automation is profitable. #### The Position of the Break-Even Point ![rpa\_processOperations\_FinanceAnalysis\_Details\_BreakEvenAnalysis\_Example\_BreakEvenPoint\_MathVsMonth](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_BreakEvenAnalysis_Example_BreakEvenPoint_MathVsMonth.png) In mathematical terms, the break-even point is the exact point in time when cumulative savings equal cumulative total costs. In the graphic, this time is shown as the orange dotted vertical line. The red dotted vertical line marks the end of the month in which this equivalence was achieved for the first time. ![rpa\_processOperations\_FinanceAnalysis\_Details\_BreakEvenAnalysis\_Example\_BreakEvenPoint\_LocationMappingDependingOnRunNumbers](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_BreakEvenAnalysis_Example_BreakEvenPoint_LocationMappingDependingOnRunNumbers.png) If the intersection point of both curves is at the start of a month, the break-even point is displayed mathematically correctly; If the intersection is somewhere during the month, the break-even point is displayed at the end of this month. #### Example: Calculation of the Break-Even Point ![rpa\_processOperations\_FinanceAnalysis\_Details\_BreakEvenAnalysis\_Example\_BreakEvenPoint](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_FinanceAnalysis_Details_BreakEvenAnalysis_Example_BreakEvenPoint.png) In our example, the cumulative savings exceed the cumulative total costs in October 2021 for the first time. ## See Also - [Analyze Costs and Savings](https://docs.mulesoft.com/rpa-manager/processoperations-financeanalysis-analyze) --- product: RPA Manager --- # Getting to Know Bots > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Besides a name, a description, a version, and a host, bots have the following properties:
PropertyDescription

Bot State

State of the bot:

  • OK:

    The bot is ready for use.

  • STOPPED:

    The bot has been stopped.

  • OVERDUE:

    The bot is no longer connecting to RPA Manager.

  • UNKNOWN:

    The status of the bot cannot be determined.

  • RESTARTPENDING:

    The bot is restarting.

  • OUT OF SERVICE TIME:

    The bot is outside of its assigned service times.

Processing

  • Pause symbol:

    The bot is currently not running any deployed processes.

  • Play symbol:

    The bot is currently running deployed processes.

Test

  • Cross symbol:

    The bot should not be used in the test phase.

  • Check mark symbol:

    The bot can be used in the test phase.

Production

  • Cross symbol:

    The bot should not be used in the production phase.

  • Check mark symbol:

    The bot can be used in the production phase.

Timezone

The timezone that the bot’s installation computer uses. The bot interprets all times for which no time zone is assigned to be set in its own time zone.

Licensed sessions

  • Shield with a check mark symbol and a number:

    Maximum number of Secure Sessions the bot may use at the same time. This number depends on the hardware the bot is installed on.

  • Shield symbol:

    The bot has been configured for a Desktop Session. It cannot use Secure Sessions.

Deployed sessions

Number of sessions that have been deployed to the bot for executing processes. The number of deployed sessions can exceed the number of licensed sessions. This may cause individual process executions to be skipped.

## Before You Begin - At least one bot must be installed on a separate computer. - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Bot Management module and view the bots.

RPA Bots Manager, RPA Operations Viewer, RPA Operations Manager, RPA Administrator

Robot Management Open

## Find Bots Open the **Bots** view in the **Bot Management** module to view all bots connected to RPA Manager. Newly installed bots connect automatically. ## See Also - [Bot Management](https://docs.mulesoft.com/rpa-manager/botmanagement-overview) - [Supporting Bots](https://docs.mulesoft.com/rpa-manager/botmanagement-support) - [Managing Bots](https://docs.mulesoft.com/rpa-manager/botmanagement-manage) - [Troubleshooting Bots](https://docs.mulesoft.com/rpa-manager/botmanagement-troubleshoot) --- product: RPA Manager --- # Handling User Tasks > For the full documentation index, see: https://docs.mulesoft.com/llms.txt User tasks are elements of a process model, which cannot be processed fully automatically by a bot, instead requiring the support of a human. Examples of such tasks include the input of data that could not be read automatically, or decisions that must be reviewed by humans for legal reasons. If, during execution of a process, the bot comes across a user task, it shows the task to all assigned users. As soon as an employee has completed processing the user task, the bot resumes its work automatically with the next process step. ## Before You Begin - User tasks are configured in RPA Builder and show up during execution of the process. - The user assignment is done while the user creates the process run configuration. ## Claim a User Tasks Claim a user task to reserve processing of the user task for yourself. The user task is then moved to your personal task list in the **My User Tasks** view. 1. In the **Team Tasks** view of the **My RPA** module, click **Claim Task** in the row of the task you want to process. ## Process a User Task Open a user task and review or change its data to continue the process. After you complete the task, the bot carries on. 1. In the **My User Tasks** view of the **My RPA** module, click **Open Task** in the row of the task you want to process. 2. Review the data. 3. Input or change data if necessary. 4. Click **Finish**. --- product: RPA Manager --- # Manage Applications > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Process applications are third-party application installations that business experts use to execute a process. Manage a list of all applications and their downtimes. Create a new entry for each instance of an application, for example `FinWiz - Mythical University - Computer 1 - Tokyo` and `FinWiz - Mythical University - Computer 42 - San Francisco`. Applications are not available during downtimes or while deactivated. To avoid confusion, append the name of the time zone to the name of the application or the downtime. For example, name an application `Words - Tokyo` and a downtime `Electrical Power Outage Tokyo`. In the **Process Management** view, a member of the project team [assigns required applications to a process](https://docs.mulesoft.com/rpa-manager/myrpa-start#required-process-applications) at process automation creation or phase transition. In the **Bot Management** module, an administrator [assigns required applications to bots](https://docs.mulesoft.com/rpa-manager/botmanagement-manage#bot-assign-servicetimes-applications) that can access them. A member of the process team can deploy a process on a bot that has assigned the required applications. If an application becomes unavailable, the bot completes running processes using that application and restarts the processes when the downtime or deactivation period has ended. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Process Automation module.

RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Process Automation Open

Create and change process applications.

RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Bots Manager, RPA Administrator

Application Create, Application Edit

Delete process applications.

RPA Automations Manager, RPA Bots Manager, RPA Administrator

Application Delete

- Note the timezone of the computer that each application is installed on. ## View All Applications To view all existing applications for automation projects, open the **Process Applications** view of the **Process Automation** module. ## Create a Process Application Create one entry for each application instance required for the execution of processes. To create a process application: 1. Open the **Process Applications** view of the **Process Automation** module. 2. Click **Create**. 3. Complete the **Create a new application** form: - **Time Zone**: Time zone for defining downtimes. Specify a downtime in the time zone in which it occurs. If the bot that you assign the downtime to is installed on a computer that uses a different time zone, the downtime interval is converted to the bot’s time zone. If you assign the application to multiple bots in different time zones, all bots pause executing processes that use that application simultaneously. The time intervals might change, depending on daylight saving time. For example, if you specify a downtime that starts at 1:30 AM and ends at 5:30 AM in Tokyo time (JST (UTC +9)) and the bot is installed on a computer in San Francisco (PST (UTC -8)), the bot does not execute processes between 8:30 AM and 12:30 PM in San Francisco time. To avoid confusion, append the name of the time zone to the name of the downtime. For example, name your downtime `Electrical Power Outage Tokyo`. - **Downtimes** Click **Create** to add a downtime to the application. 4. Click **Save**. ## Edit an Application Edit an application to change its data or downtimes: 1. Open the **Process Applications** view of the **Process Automation** module. 2. Click **Create**. 3. Edit the **Edit the application** form. For an explanation of the properties, see [**Create an Application**](#form-create-process-applications). 4. Click **Save**. ## Deactivate or Activate a Process Application Deactivate an application if it is temporarily unavailable and you don’t know when it will be available again. Use downtimes to schedule maintenance and planned downtimes. Deactivation periods are not added to the list of downtimes. Applications are not available during downtimes or while deactivated. A member of the process team can deploy a process on a bot that has assigned the required processes. If an application becomes unavailable, the bot completes running processes using that application and restarts them when the downtime or deactivation period has ended. If an application is not available, deactivate it: 1. Open the **Process Applications** view of the **Process Automation** module. 2. Click **Deactivate** (![toggle-on symbol](/mulesoft/current/en-us/rpa-manager/_images/deactivate-icon.png)) on the panel of the application to deactivate. RPA Manager displays an **Inactive** label on the panel of the application. If a deactivated application becomes available again, activate it: 1. Open the **Process Applications** view of the **Process Automation** module. 2. Click **Activate** (![toggle-off symbol](/mulesoft/current/en-us/rpa-manager/_images/activate-icon.png)) on the panel of the application to activate. RPA Manager displays an **Active** label beneath the logo of the application. ## Remove a Process Application Remove an application if it is no longer available: 1. Open the **Process Applications** view of the **Process Automation** module. 2. Click **Remove** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) on the panel of the application to remove. 3. Confirm the removal. RPA Manager removes the application from all processes and bots to which it was assigned. ## See Also - [Assign Process Applications to an Automation Project](https://docs.mulesoft.com/rpa-manager/processautomation-manage#projectdata-processapplications) - [Assign Process Applications to a Bot](https://docs.mulesoft.com/rpa-manager/botmanagement-manage#bot-assign-servicetimes-applications) --- product: RPA Manager --- # Manage Categories > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Process team members organize projects into categories. Manage a set of categories from which process team members can choose one when they create a [process evaluation](https://docs.mulesoft.com/rpa-manager/processevaluation-propose#create-a-process-evaluation) or an [automation project](https://docs.mulesoft.com/rpa-manager/processautomation-manage#create-an-automation-project). A category describes the environment of a process in a few keywords, for example `Customer Support Mythical University` or `Finance`. A process can only belong to a single category. First, create a standard category, so the process team can start with process automation quickly. The team can change the category of a process later. After the team automates the first few projects, create an archive category to move the completed projects there. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Process Automation module.

RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Process Automation Open

## View All Categories To view all existing categories for automation projects, open the **Process Management** view of the **Process Automation** module. ## Create a Category Create a category that process team members can choose when they create a process evaluation or an automation project. The name of a category should consist of a unique set of distinct keywords that describe the common environment of a set of processes. To create a category: 1. Open the **Process Management** view of the **Process Automation** module. 2. Click **Create**. 3. Enter a name in the **Create a category** window. 4. Click **OK**. The category panel shows the number of contained projects and how many are in development and in production. ## Edit a Category Edit a category to render its name more precisely: 1. Open the **Process Management** view of the **Process Automation** module. 2. Click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) on the panel of the category to edit. 3. Change the name in the **Edit the category** window. 4. Click **OK**. ## Remove a Category Remove categories that are no longer needed. You can only remove categories that do not contain processes. To remove a category: 1. Open the **Process Management** view of the **Process Automation** module. 2. Click **Remove** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) on the panel of the category to delete. ## Open a Category To view the contained projects, open the category: 1. Open the **Process Management** view of the **Process Automation** module. 2. Click the name of the category. The project panels show the data and actions of the project. ## See Also - [Assign a Category to a Process Evaluation](https://docs.mulesoft.com/rpa-manager/processevaluation-propose#processevaluationdata-category) - [Assign a Category to an Automation Project](https://docs.mulesoft.com/rpa-manager/processautomation-manage#projectdata-category) --- product: RPA Manager --- # Manage Credentials > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). Credentials store login data for external applications or web services. By using a credential, a bot can log in to an application during process runs. Passwords are encrypted. Only affiliated users can view, edit, and use the credentials. You can create the following types of credentials: - **AWS Credentials** To access Amazon Web Services to use them with the RPA Builder [Document Processing with AWS](https://docs.mulesoft.com/rpa-builder/latest/toolbox-aws-document-processing) action steps. - **Connected App Credentials** To access MuleSoft Intelligent Document Processing (IDP) with RPA Builder [MuleSoft IDP](https://docs.mulesoft.com/rpa-builder/latest/toolbox-mulesoft-idp) action steps. - **Google API Service Account Credentials** To access the Google API with the [Google Drive operation](https://docs.mulesoft.com/rpa-builder/latest/toolbox-google-drive-operations) action steps. - **OAuth Credentials** To access the Microsoft Outlook and Gmail email applications with the RPA Builder [Mail Session (OAuth)](https://docs.mulesoft.com/rpa-builder/latest/toolbox-mail-operations-mail-session-oauth) action steps. - **User Account Credentials** To access all other kinds of applications. Use descriptive names for credentials and only use them in an appropriate context. For example, if the employee `Nina` has an account for two applications, `Letters` and `Numbers`, create either two credentials (`nina_account_letters` and `nina_account_numbers`) or a single credential that includes both applications in its name (`nina_accounts_letters_numbers`). Affiliated process team members can link global credentials to activity parameters in automations: - [Linkable Activity Parameters in Test Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#test-configuration-link-globals) - [Linkable Activity Parameters in Production Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#production-configuration-link-globals) Editing or deleting a credential affects all configurations that use the credential. Check the usage of a credential before changing or deleting it. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Process Automation module.

RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Process Automation Open

Create and change global variables and credentials to use in the test phase.

RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Global Variables Create for Test phase, Global Variables Edit for Test phase

Create and change global variables and credentials to use in the production phase.

PA Automations Contributor, RPA Automations Manager, RPA Administrator

Global Variables Create for Production phase, Global Variables Edit for Production phase

Delete global variables and credentials.

RPA Automations Manager, RPA Administrator

Global Variables Delete

- If you have access to an Amazon Web Services (AWS) account and want to create AWS credentials for RPA Builder [Document Processing with AWS](https://docs.mulesoft.com/rpa-builder/latest/toolbox-aws-document-processing) action steps, [configure the basic settings for the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html). - If you have access to a Microsoft Azure account and want to create OAuth credentials for RPA Builder [Mail Session (OAuth)](https://docs.mulesoft.com/rpa-builder/latest/toolbox-mail-operations-mail-session-oauth) action steps, follow these instructions: 1. [Create an application for Outlook.](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) 2. [Authenticate an EWS application by using OAuth.](https://learn.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-authenticate-an-ews-application-by-using-oauth) 3. [Authenticate an IMAP, POP, or SMTP connection using OAuth.](https://learn.microsoft.com/en-us/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth) - To autofill the Google API service account credentials, obtain the credentials JSON file from your Google Cloud Console administrator. If you have access to the Google Cloud console, follow the instructions in [Create credentials for a service account](https://developers.google.com/workspace/guides/create-credentials#create_credentials_for_a_service_account) to obtain credentials for your Google Cloud service account. - If you want to use RPA Builder to [generate a refresh token for your OAuth credentials](https://docs.mulesoft.com/rpa-builder/latest/toolbox-variable-handling-credentials-for-oauth#generate-oauth-token), ask an administrator to assign you the `Builder Usage` privilege. ## Create a Credential Create credentials that a bot can use to log in to an external application during process runs. To create a credential: 1. Open the **Credential Pool** view of the **Process Automation** module. 2. Click **Create**. 3. Complete the **Create a New Credential** form: - **User affiliation** Select users that may view, edit, and use the credential. Add yourself so that you can also view, edit, and use the credential. - **User group affiliation** Select user groups whose members may view, edit, and use the credential. If you use an Anypoint account to login to RPA Manager, user groups are replaced by teams. - **Phase affiliation** Phases in which the credential can be deployed. When you create or change the credential, your privileges determine which phases the user can select: - **Test** The credential can be deployed in the test phase. - **Production** The credential can be deployed in the production phase. - **Type** Type of the global credential, which determines where you can use it. The original value defined in RPA Builder is typed. Select one of the following types: - **AWS Credentials** Use this credential to access Amazon Web Services. Fill in the client ID, client secret, and region. The session token is optional. - **Connected App Credentials** Use this credential to access MuleSoft Intelligent Document Processing (IDP) via RPA Builder action steps. - **Client ID** Client ID of the connected app configured to call IDP. - **Client Secret** Client Secret of the connected app configured to call IDP. - **Google API Service Account Credentials** Use this credential to access the Google API with the [Google Drive operation](https://docs.mulesoft.com/rpa-builder/latest/toolbox-google-drive-operations) action steps. Click **Autofill from JSON** to import the authentication data from a credentials JSON file provided by your Google Cloud Console administrator. The JSON file must contain all properties of the form. - **OAuth Credentials** Use this credential to access the Microsoft Outlook or Google Gmail email applications. > [!IMPORTANT] In the current version of the **OAuth Credentials**, **OAuth Authorization > Endpoint** and **OAuth Token Endpoint** replace **OAuth Host**. Check your processes to > see if they exchanged the Activity Parameters and create new credentials to link. - **OAuth Host** The host address used to get the credentials. The default address for Outlook services is `[https://login.microsoftonline.com/common/oauth2/v2.0/](https://login.microsoftonline.com/common/oauth2/v2.0/)`. This address might change if the customer uses a self hosted service. - **OAuth Authorization Endpoint** The URL for the OAuth authentication endpoint. Defaults to the following values, depending on the selected provider: - **Outlook**: `https://login.microsoftonline.com/common/oauth2/v2.0/authorize` - **Google**: `https://accounts.google.com/o/oauth2/v2/auth` - **OAuth Token Endpoint** The URL for the OAuth Refresh Token process. Defaults to the following values, depending on the selected provider: - **Outlook**: `https://login.microsoftonline.com/common/oauth2/v2.0/token` - **Google**: `https://www.googleapis.com/oauth2/v4/token` - **Client ID** To authenticate with the OAuth Host, define an Azure application in your space. This Azure application has an ID, which is unique in the entire OAuth Host space, and that allows users to explicitly grant or revoke access for this Azure application to their accounts. For more information about how to create this Azure application for Outlook, see [Quickstart: Register an application with the Microsoft identity platform](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app). - **Client Secret** This secret enables RPA Manager to prove to the OAuth Host that it received permission to access user accounts on behalf of the registered Azure application. Without it, authentication is not possible. - **Redirect URI** The URI to which the OAuth Host redirects after the user completes the authentication attempt. This redirect URI must be registered with the Azure application. The OAuth Host allows authentication only if the entered redirect URI matches one of the registered URIs. - **Scopes** The scopes define which permissions you grant over your account to the Azure application. Separate the scopes to grant by blank spaces, for example `offline_access [https://outlook.office.com/IMAP.AccessAsUser.All](https://outlook.office.com/IMAP.AccessAsUser.All)`. If you leave the scopes field empty, RPA Manager grants the following scopes by default: - `offline_access` (**Required**) Enables access via a refresh token, which you can use to repeatedly log in to the mail services without requiring user interaction each time. - `[https://outlook.office.com/IMAP.AccessAsUser.All](https://outlook.office.com/IMAP.AccessAsUser.All)` (**Required** when using IMAP) Enables reading and moving emails from the Outlook IMAP server. - `[https://outlook.office.com/POP.AccessAsUser.All](https://outlook.office.com/POP.AccessAsUser.All)` (**Required** when using POP3) Enables reading emails from the Outlook POP3 server. - `[https://outlook.office.com/SMTP.Send](https://outlook.office.com/SMTP.Send)` (**Required** when using SMTP) Enables sending emails from the Outlook SMTP server. - `openid email` Enables RPA Manager to automatically detect the email account used to log in to the Azure application. If this scope is omitted, you must provide an email in RPA Builder. - **E-Mail Address** Specifies the email address for accessing Outlook. - **Refresh Token** Specifies the refresh token generated with the authentication properties. Learn how to [generate an OAuth refresh token with RPA Builder](https://docs.mulesoft.com/rpa-builder/latest/toolbox-variable-handling-credentials-for-oauth#generate-oauth-token). - **User Account Credentials** Use this credential to access all other types of applications. Fill in the username and password. 4. Click **OK**. ## Check the Usage of a Credential Before editing a credential, check its usage to avoid inadvertent side effects. You can check the usage of a credential only if you belong to the [affiliated users](#form-create-credential-useraffiliation) of that credential. To check the usage of a credential: 1. Open the **Credential Pool** view of the **Process Automation** module. 2. Click **Usage** (![binoculars symbol](/mulesoft/current/en-us/rpa-manager/_images/usage-icon.png)) in the row of the credential to check. A window with a table shows you the configurations that use the credential. ## Edit a Credential Edit a credential to change its data. You cannot change the type of a credential. You can edit a credential only if you belong to the [affiliated users](#form-create-credential-useraffiliation) of that credential. Check the usage of the credential first to avoid inadvertent side effects: 1. Open the **Credential Pool** view of the **Process Automation** module. 2. Click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the row of the credential to edit. 3. Change data in the **Edit the Credential** form. For an explanation of the properties, see [**Create a Credential**](#form-create-credential). 4. Click **Save**. The credential is changed everywhere it is used. ## Delete a Credential Delete credentials that are no longer needed. You cannot delete credentials linked in configurations. You can only delete a credential if you belong to the [affiliated users](#form-create-credential-useraffiliation) of that credential. To delete a credential: 1. Open the **Credential Pool** view of the **Process Automation** module. 2. Click **Delete** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) in the row of the credential to delete. 3. Confirm the deletion. ## See Also - [RPA Builder: Activity Parameters](https://docs.mulesoft.com/rpa-builder/latest/toolbox-variable-handling-activity-parameters) - [Linkable Activity Parameters in Test Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#test-configuration-link-globals) - [Linkable Activity Parameters in Production Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#production-configuration-link-globals) - [Linkable Activity Parameters in Invocable Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#invocable-configuration-link-globals) - [User Roles and Permissions](https://docs.mulesoft.com/rpa-home/automation-userrolesandpermissions) - [Assembling User Groups](https://docs.mulesoft.com/rpa-manager/usermanagement-assemble) --- product: RPA Manager --- # Manage Global Variables > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Global variables store values that are the same in multiple processes and that frequently change. By using them, you can reduce the time involved and the error rate in the maintenance of the processes. Examples use cases of global variables are: - Tax rates (floating point value) - File paths (alphanumeric value) - Email addresses (alphanumeric value) - Approval (boolean value) - Offset for determining a screen coordinate (coordinate value) The RPA developer defines [activity parameters](https://docs.mulesoft.com/rpa-builder/latest/toolbox-variable-handling-activity-parameters) for a process in RPA Builder. You create reusable global variables that process team members can link to an activity parameter in an automation to overwrite the initial value of the activity parameter: - [Linkable Activity Parameters in Test Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#test-configuration-link-globals) - [Linkable Activity Parameters in Production Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#production-configuration-link-globals) Use descriptive names for global variables and only use the variables in an appropriate context. For example, if the number 42 refers to both the number of employees in your company and the answer to a different question, then create two global variables (for example, `number_employees` and `answer`). Editing or deleting a global variable affects all configurations that use the variable. Check the usage of a variable before changing or deleting it. To store login data securely, use [credentials](https://docs.mulesoft.com/rpa-manager/processautomation-prepare-deployment-credential). ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Process Automation module.

RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Process Automation Open

Create and change global variables that can be used in the test phase.

RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Global Variables Create for Test phase, Global Variables Edit for Test phase

Create and change global variables that can be used in the production phase.

RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Global Variables Create for Production phase, Global Variables Edit for Production phase

Delete global variables.

RPA Automations Manager, RPA Administrator

Global Variables Delete

## Create a Global Variable Create a global variable that process team members can link to an activity parameter in an automation to overwrite the initial value of the activity parameter. To create a global variable: 1. Open the **Global Variables** view of the **Process Automation** module. 2. Click **Create**. 3. Complete the **Create a New Global Variable** form: - **Phase affiliation** Phases in which the variable is permitted to be deployed. When you create or change the variable, your individual privileges determine which phases you can select: - **Test** The variable can be deployed in the test phase. - **Production** The variable can be deployed in the production phase. - **Type** Type of the global variable. The type of variable determines where it can be used. The original value defined in RPA Builder is typed. Select one of the following types: - **Integer** An integer number. - **Alphanumeric** A character string. - **Boolean** A logical value. Select the **Value** checkbox for the value `true` or deselect for the value `false`. - **Float** A floating-point number. - **Coordinate** Combination of two integer values for an X-Y coordinate. - **Value** You can only enter values of the specified type. ## Check the Usage of a Global Variable Before editing a global variable, check its usage to avoid inadvertent side effects: 1. Open the **Global Variables** view of the **Process Automation** module. 2. Click **Usage** (![binoculars symbol](/mulesoft/current/en-us/rpa-manager/_images/usage-icon.png)) in the row of the global variable to check. A window with a table shows you the configurations that use the global variable. ## Edit a Global Variable Edit a global variable to change its name or value. You cannot change the type of a global variable. Check the usage of the variable first to avoid inadvertent side effects. To edit a global variable: 1. Open the **Global Variables** view of the **Process Automation** module. 2. Click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the row of the global variable to edit. 3. Change data in the **Edit the Global Variable** form. For an explanation of the properties, see [**Create a Global Variable**](#form-create-globalvariable). 4. Click **Save**. The variable is changed everywhere it is used. ## Delete a Global Variable Delete global variables that are no longer needed. You cannot delete variables linked in configurations. To delete a global variable: 1. Open the **Global Variables** view of the **Process Automation** module. 2. Click **Delete** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) in the row of the global variable to delete. 3. Confirm the deletion. ## See Also - [RPA Builder: Activity Paramters](https://docs.mulesoft.com/rpa-builder/latest/toolbox-variable-handling-activity-parameters) - [Linkable Activity Parameters in Test Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#test-configuration-link-globals) - [Linkable Activity Parameters in Production Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#production-configuration-link-globals) - [Linkable Activity Parameters in Invocable Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#invocable-configuration-link-globals) --- product: RPA Manager --- # Managing Automations > For the full documentation index, see: https://docs.mulesoft.com/llms.txt An RPA project consists of a business process to automate and the team responsible for the automation. When a project manager clicks **Start automation** for a process in the **My Backlog** view of the **My RPA** module, RPA Manager creates a project for the process automation. To automate a process already evaluated with a third-party tool, a project manager can alternatively create an automation project directly in the following RPA Manager views: - **RPA Home** - **My RPA** > **My Processes** - **Process Evaluation** > **Process Evaluation** - **Process Automation** > **Process Management** - **Process Automation** > **Process Management** > **** The **Process Management** view shows the projects organized by category. Within a category, you can manage the process automation projects: - Create, copy, edit, and delete projects. - View the status of projects, including financial analysis. - Transition projects forward and backward through all life-cycle phases. - Create boards for managing project tasks. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Process Automation module.

RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Process Automation Open

Create, edit, and delete process projects.

RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Project Manager, RPA Administrator

Process Create, Project Management

Copy projects.

RPA Automations Contributor, RPA Automations Manager, RPA Project Manager, RPA Administrator

Process create, Project Management, Builder Usage

Change the process owner.

RPA Automations Manager, RPA Administrator

Change Process Owner

Change the project manager.

RPA Automations Manager, RPA Administrator

Change Project Manager

- To transition a project to another phase, you must have the needed permissions as a member of the [process team](#projectdata-processteam). ## Create an Automation Project When a project manager clicks the icon **Start automation** for a process in the **My Backlog** view of the **My RPA** module, RPA Manager creates a project for the automation of the process. To automate a process already evaluated with a third-party tool, you can create an automation project inside a category directly in the **Process Automation** module: 1. Open the **Process Management** view of the **Process Automation** module. 2. Click on the name of the category in which you want to create the new project. 3. In the **** view, click **Create**. 4. Complete the form **Create process**: - **Setting**: - **Process Owner**: User who proposed the process for automation via a process evaluation. - **Required Applications for Process**: Select all applications here that are required to carry out the process. All applications that have been created in the **Process Applications** view of the **Process Automation** module are displayed in the drop-down list and can be removed from the input field by clicking the **X**. It is important to select all required applications here to ensure that the process can only be implemented subsequently by robots that can use these applications. - **Process Team**: The process team is a group of employees who work together on execution of the process automation. Select all team members from the text selection field. Then, by selecting the relevant checkboxes in the table, you can authorize the team members to work on the processes in the various phases. By default, each team member has authorization to transfer the process from their own phase to the next phase. If approval for the next phase is only to be carried out by specific team members, then select the checkbox **Advanced Permissions** to assign authorizations for approval separately. All team members have read access to the project in all phases. The project manager is always part of the team and also always has all authorizations. If the checkbox **Advanced Permissions** is deselected, the values of this column are no longer taken into account. In that case, only that user who has authorization to work on a phase can transfer the Process to the next phase. - **Category**: A category describes the environment of a process in a few keywords. Choose a category from the list. - **Use Process Board**: Select this checkbox to use a process board. Process boards contain administrative process tasks. The tasks transition from **To-do** via **In progress** to **Completed**. If you deselect this checkbox, the previous tasks remain, but are no longer displayed and are no longer considered for phase transitions. As soon as you select the checkbox again, the tasks are displayed and taken into account again. - **Create automatic Phase Release Tasks**: Select this checkbox to create automatic phase release tasks. Phase changes can only be made if the corresponding task has reached the status **Completed**. - **Process Costs**: - **Initial Investment for the Process Automation**: The initial investment for the acquisition of the MuleSoft RPA solution and the necessary infrastructure is required for the finance analysis. 5. Click **Save**. RPA Manager returns to the **** view and sorts your new project according to your workspace settings. ## Copy an Automation Project A copy of an automation project contains all information from the original project, including the most recent revision of all workflows, with the exception of the bot assignments to test and productive configurations. Copy a project to automate a similar process more quickly: 1. Open the **Process Management** view of the **Process Automation** module. 2. Click on the name of the category of the project that you want to copy. 3. In the **** view, click **Copy** (![copy symbol](/mulesoft/current/en-us/rpa-manager/_images/copy-icon.png))on the panel of the project you want to copy. 4. Check and edit the form **Copy process**: For an explanation of the properties, see [**Create process**](#form-createprocess). 5. Click **Save**. To complete copying the project: 1. Transition the project copy to the build phase. 2. Open the project copy in the [RPA Builder](https://docs.mulesoft.com/rpa-builder/latest/). 3. [Upload](https://docs.mulesoft.com/rpa-builder/latest/ui-overview#menu-bar) the project copy to RPA Manager. The project copy then receives its own identification values. Only after the copy process completes, the following actions are possible: - Another process team member can open the project copy in RPA Builder. - You or another process team member can transition the project copy to the test phase. ## Edit an Automation Project Edit an automation project to update it: 1. Open the **Process Management** view of the **Process Automation** module. 2. Click on the name of the category of the project. 3. In the **** view, click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) on the panel of the project to edit. 4. Check and edit the form **Copy process**: For an explanation of the properties, see [**Create process**](#form-createprocess). 5. Click **Save**. ## Change the Process Owner of an Automation Project Change the owner of a process to represent changed responsibilities: 1. Open the **Process Management** view of the **Process Automation** module. 2. Click on the name of the category of the project. 3. In the **** view, click **New Process Owner** (![user-with-crown symbol](/mulesoft/current/en-us/rpa-manager/_images/newprocessowner-icon.png)) on the panel of the project for which you want to change the process owner. 4. In the window **New process owner**, select a user. 5. Click **OK** RPA Manager adds the new process owner to the process team with read access. RPA Manager removes the previous process owner from the process team independent of their previous authorizations. You can add them again as a team member. ## Change the Project Manager of an Automation Project Change the manager of a project to represent changed responsibilities: 1. Open the **Process Management** view of the **Process Automation** module. 2. Click on the name of the category of the project. 3. In the **** view, click **New Project Manager** (![user-with-tie symbol](/mulesoft/current/en-us/rpa-manager/_images/newprojectmanager-icon.png)) on the panel of the project for which you want to change the project manager. 4. In the window **New project manager**, select a user. You can only select a user who has the privilege **Project Management**. 5. If you don’t want to include the previous manager into the project team, unselect the checkbox **Add the current Project Manager to the project team. The current Project Manager is added with no assigned phases and thus only able to see this project.** 6. Click **OK** You can assign additional permissions to the previous manager as a team member. ## Remove an Automation Project Remove automation projects you no longer need. This can’t be undone and is neither logged nor reported. The **Delete** icon is only displayed if the logged-in user is the project’s manager and the project has never been deployed productively. After an RPA bot has run the process in the production phase, you can no longer delete it. To remove a project: 1. Open the **Process Management** view of the **Process Automation** module. 2. Click on the name of the category of the project. 3. In the **** view, click **Remove** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) on the panel of the project to remove. 4. Confirm the prompt. ## Manage Process Project Tasks You can manage all tasks that arise in association with automating a process via an agile process board if you have [enabled it for the project](#projectdata-useprocessboard). A task consists of a name, description, owner, priority, due date, and effort estimate. You can drag tasks across the board to reflect their progress. A process board is a table with three columns, across which you can arrange task items: - **To-do** The **To-do** column contains all incomplete tasks. You create new tasks here. If you have [enabled the creation of automatically generated tasks for phase transitions](#projectdata-phasereleasetasks), RPA Manager creates a new corresponding task during each phase transition. Remember to move tasks in progress into the **In Progress** area. - **In Progress** The **In Progress** column contains all the tasks that someone is currently working on. Remember to move completed tasks into the **Completed** area. - **Completed** The **Completed** column contains all completed tasks. You can edit and move completed tasks. If you enabled the creation of automatically generated tasks for the phase transitions, RPA Manager enables the button for the transition to the next phase when all tasks are in the **Completed** column. Each user’s process tasks are also displayed in the **My Process Board** view of the **My RPA** module. Usually, the project manager decides during project creation if the project needs a process board. You can also decide to introduce a process board for any process later. ### Open a Process Board To open a process board: 1. Open the **Process Management** view of the **Process Automation** module. 2. Click on the name of the category of the project. 3. In the **** view, click **Open process board** (![column symbol](/mulesoft/current/en-us/rpa-manager/_images/processboard-icon.png)) on the project panel or in an already opened project. Click **Back to Process** to return to or open the project. ### Create a Task Create a process project task to enhance the automation. Examples of such tasks are `Design: Leaning (Remove superfluous elements from the graph, check for dead ends and double doors)`, `Add missing process documentation (Prepare decision table)` or `Kick-off Meeting`. To create a task: 1. [Open a process board](#openprocessboard). 2. Click **\+ Create Task** in the **To-do** column. 3. Complete the form **Create new task**: - **Task Owner**: The task owner is responsible for completing the task. Choose a user from the process team. The task item displays the user’s profile picture. RPA Manager shows all tasks of the task owners on their personal **My Process Board** view in the **My RPA** module. - **Priority**: You can set the priority of the task to low, medium, or high. The task item displays a gray, yellow, or red label, respectively. - **Due date**: Date on which the task must be complete. - **Effort**: Approximate amount of time that the task takes. 4. Click Save. ### Edit a Task Edit tasks to reflect changed requirements: 1. [Open a process board](#openprocessboard). 2. Click a task item. 3. Edit the form **Edit task**. For an explanation of the properties, see [**Create a task**](#form-createprocessboardtask). 4. Click **Save** ### Delete a Task Delete obsolete tasks: 1. [Open a process board](#openprocessboard). 2. Click a task item. 3. Click **Delete**. 4. Confirm the deletion. ### Move a Task Move tasks within a column to sort them or across columns to reflect their progress: 1. [Open a process board](#openprocessboard). 2. Drag a task item to its new place. If you enabled the creation of automatically generated tasks for the phase transitions, move this task to the **Completed** column after all other tasks are complete to enable the transition of the project to the next phase. ## Analyze the Financial Aspects of a Process Open the [**Finance Analysis** view](https://docs.mulesoft.com/rpa-manager/processoperations-financeanalysis) to record, monitor, and analyze the financial aspects of a process: 1. Open the **Process Management** view of the **Process Automation** module. 2. Click on the name of the category of the project. 3. In the **** view, click **Finance Analysis** (![analytics graph symbol](/mulesoft/current/en-us/rpa-manager/_images/financeanalysis-icon.png)) on the panel of the project you want to analyze. ## Transition an Automation Project to Another Phase When it’s ready, transition the project to its next lifecycle phase. You can always transition back to change the automation design or implementation. Design phase - Create or change a process model in RPA Manager. Already implemented activities retain their implementation unless you delete them. - Transition the automation containing the new or changed models to the build phase. Build phase - Download the model from RPA Manager. - Change the model. - Implement the activities. If you want to version workflows, create and reuse activities in the Activity Library. - Upload the changed and implemented model to the repository in RPA Manager. Only one version of a process exists in the repository in RPA Manager. If you accidentally delete an already implemented activity, a local version might be available in RPA Builder — as long as you don’t overwrite the model by downloading the newer one from RPA Manager. - Transition the automation back to the design phase. Already implemented activities retain their implementation unless you delete them. - Transition the automation on to the test phase. Test phase - Test the implemented process model in different configurations. - Transition the automation back to the build phase to change the implementation. You can reuse or edit the test run configurations when you transition the automation back to the test phase. - When the tests succeed, transfer the automation to the production phase. After the project has been deployed to an RPA Bot for processing in the production phase, you can no longer delete it. Production phase - Create and deploy a scheduled run configuration to run the process automatically at defined times. - Create and publish an invocable run configuration\* to use it within other Salesforce products. - Create an on-demand run configuration to start the process run manually. - If you use activities from the Activity Library, you can [change the deployed version](https://docs.mulesoft.com/rpa-manager/processoperations-upcomingprocesschanges) in the **Upcoming Process Changes** view of the **Process Operations Module**. - Transition the automation back to the test phase. You can reuse or edit the production run configurations when you transition the automation to the production phase again. ### Transition to the Next Phase After an automation project is ready, transition it to the next phase. RPA Manager retains your previously configured elements from each phase. 1. Open the **Process Management** view of the **Process Automation** module. 2. Click the category name for the project. 3. In the **** view, click the name of a project. 4. If the project uses a process board with automatic phase release tasks, complete that task to enable the transition. 5. In the header, click **Publish **. ### Transition to a Previous Phase To rework an automation project, transition it to a previous phase. RPA Manager retains your previously configured elements from each phase. 1. Open the **Process Management** view of the **Process Automation** module. 2. Click on the name of the category of the project. 3. In the **** view, click the name of a project. 4. In the header, click **Back **. 5. Repeat the previous step until you reach the desired phase. ## See Also - [Starting Automation of Approved Processes](https://docs.mulesoft.com/rpa-manager/myrpa-start) - [Manage Process Categories](https://docs.mulesoft.com/rpa-manager/processautomation-prepare-project-category) - [RPA Builder: Activity Library Explorer](https://docs.mulesoft.com/rpa-builder/latest/activity-library-explorer) - [Upcoming Process Changes](https://docs.mulesoft.com/rpa-manager/processoperations-upcomingprocesschanges) --- product: RPA Manager --- # Managing Bots > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Newly installed bots connect to RPA Manager automatically. As a bot administrator, you can manage the following properties of a bot: - Name and describe a bot. - Assign service times to a bot to determine their office hours. - Restrict bots to project phases. - Set the maximum number of sessions a bot can use. - Update the bot to a newer version. If a bot isn’t working properly, you can do the following: - Download the log files. - Restart the bot. - Delete the bot. ## Before You Begin - At least one bot must be installed on a separate computer. - On the computer where you want to run automations and where a bot therefore is installed, check the system data: - Operating system - RAM - Terminal Server software - Login data for the bot - RPA Bot Configurator settings - If you want to use Secure Sessions, read and pass on the following information: - Before deploying a run configuration on a bot that has only one licensed secure session, do not disconnect the session, instead sign out the specified user. - If you want to assign more than one secure session to a bot, make sure that a terminal server software is installed on the computer of the bot and refer to the [system and hardware requirements documentation](https://docs.mulesoft.com/rpa-bot/latest/hardware-software-requirements#requirements-for-secure-session-technology) to determine the maximum number of secure sessions for the bot. - Do not sign in to a computer where a bot with one licensed secure session is running a process. - If you want to use Desktop sessions, read and pass on the following information: - The specified user must be logged in to this session to deploy a run configuration. The console session must remain open and unminimized while the bot executes a process. - If you want to assign service times to a bot, you need to create them in the **Service Times** view of the **Bot Management** module first. - If you want to assign process applications to a bot, you need to create them in the **Process Applications** view of the **Process Automation** module first. - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Bot Management module and view the bots.

RPA Bots Manager, RPA Operations Viewer, RPA Operations Manager, RPA Administrator

Bot Management Open

License, edit, update, and remove bots.

RPA Bots Manager, RPA Operations Manager, RPA Administrator

Bot Management Administration

## Assign Sessions to Bots The bot runs a process configuration in a session on the computer where the bot is installed. If bots should run processes in a hidden session, assign the bot at least one Secure Session. The number of Secure Sessions that can be assigned and served by the bot depends on the hardware of the computer on which the bot is installed. Please refer to the system and hardware requirements topic to assess the maximum number of Secure Sessions for the bot. Enabling the same setting via the RPA Bot Configurator, limits but not overwrites this setting. 1. In the **Bots** view of the **Bot Management** module, click **Secure Session Assignment**. 2. Set the number of sessions the bot can use: - Session Assignment >= 1: - The bot consumes up to the specified number of Secure Sessions. - Session Assignment = 0 The bot consumes the Desktop session. 3. Click **Save**. ## Assign Service Times and Process Applications to Bots Assign service times to bots to determine when a bot may execute processes. Service times are repeatable time intervals that define when a service is available. Assign them to bots to determine when a bot can execute processes. Specify the service time in one time zone. If the bot that you assign the service time to is installed on a computer that uses a different time zone, the service time interval is converted to the bot’s time zone. If you assign the service time to multiple bots in different time zones, all bots execute processes simultaneously. The time intervals might change, depending on daylight saving time. For example, if you specify a service time that starts at 9:30 AM and ends at 5:30 PM in Buenos Aires time (ART (UTC -3)) and the bot is installed on a computer in Berlin (CET (UTC +1)), the bot executes processes between 1:30 PM and 9:30 PM in Berlin time. Learn how to [manage service times](https://docs.mulesoft.com/rpa-manager/botmanagement-support#manage-service-times). Assign process applications to bots that can access them. You can deploy a process on a bot that has assigned the required applications. Downtimes are repeatable time intervals that define when an application is unavailable. Processes whose applications are currently down are executed to completion and not restarted until the downtime period ends. Specify a downtime in the time zone in which it occurs. If the bot that you assign the downtime to is installed on a computer that uses a different time zone, the downtime interval is converted to the bot’s time zone. If you assign the application to multiple bots in different time zones, all bots pause executing processes that use that application simultaneously. The time intervals might change, depending on daylight saving time. For example, if you specify a downtime that starts at 1:30 AM and ends at 5:30 AM in Tokyo time (JST (UTC +9)) and the bot is installed on a computer in San Francisco (PST (UTC -8)), the bot does not execute processes between 8:30 AM and 12:30 PM in San Francisco time. Learn how to [manage applications](https://docs.mulesoft.com/rpa-manager/processautomation-prepare-project-application). 1. In the **Bots** view of the **Bot Management** module, click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the row of the bot to edit. 2. In the form **** click on all service times and applications you want to assign. 3. Click **Save**. ## Update a Bot Update your bots to the latest version to get the newest features, bug fixes, and security enhancements. The bot finishes all processes before updating and resumes them afterwards to avoid data loss. Alternatively, you can update single bots manually by downloading and installing the newer version from the **Download Applications** pane in the **Home** module of RPA Manager. You can automatically update bots that fullfil the following requirements: - The bot is in OK status. - The bot version is 1.5 or later. To update one or more bots automatically: 1. In the **Bots** view of the **Bot Management** module, click **Update**. 2. In the **Select Bots** pane, select the bots to update. 3. Click **Update**. RPA Manager creates an update task for each bot to be updated as soon as possible. You can view the status of the update task in the details view of each bot in the **Bots** view of the **Bot Management** module. ## Edit a Bot Edit a bot to change its properties. Hostname, IP address, version, and timezone are fixed values taken from the computer the bot is installed on. 1. In the **Bots** view of the **Bot Management** module, click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the row of the bot to edit. 2. Edit the **** form. 3. Click **Save**. ## Remove a Bot After deinstallation or reconfiguration, a bot is still shown in the **Bots** view. You need to manually remove the bot from the view. Deleted bots are removed from process configurations. Any active processes are terminated. 1. In the **Bots** view of the **Bot Management** module, click **Remove** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) in the row of the bot to remove. 2. Confirm the removal. If you accidentally remove a bot that is running, the bot shuts down and the API Key is deleted on the bot’s computer. You must uninstall and reinstall the bot with a new API Key. In this case, reassign the licenses, name, description, assigned process applications and service times, and tasks. ## See Also - [RPA - Secure Sessions](https://docs.mulesoft.com/rpa-home/automation-security-securesessions) - [RPA Bot - Hardware and Software Requirements](https://docs.mulesoft.com/rpa-bot/latest/hardware-software-requirements) - [RPA Bot Configurator](https://docs.mulesoft.com/rpa-bot/latest/configuration) - [Troubleshooting Bots](https://docs.mulesoft.com/rpa-manager/botmanagement-troubleshoot) - [Deploying Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy) --- product: RPA Manager --- # Managing the Bot Workflow Library > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The **Bot Workflow Library** view shows all bot workflows in the RPA Builder Activity Library. You can do the following to view and manage the workflows: - Create, edit, and delete tags for the library. - View an outline of a workflow. - Edit the description and the tags of a workflow. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Process Automation module.

RPA Administrator

Process Automation Open

Open the Bot Workflow Library.

RPA Automations Contributor, RPA Automations Manager

Activity Library Open

  • Create tags for the library.

  • Add, edit, and remove tags from bot workflows.

  • Add and edit bot workflow descriptions.

RPA Automations Manager

Activity Library Administration

## Viewing Bot Workflows Get an overview of all bot workflows. ### View the List of All Bot Workflows Open the **Bot Workflow Library** view in the **Process Automation** module to view the list of all bot workflows and see their purpose. ### View an Outline of a Bot Workflow View the outline of a bot workflow to better understand how it works: 1. Open the **Bot Workflow Library** view in the **Process Automation** module. 2. Click **Details** (![eye symbol](/mulesoft/current/en-us/rpa-manager/_images/show-icon.png)) in the panel of the workflow to view. 3. Click **Back** to view the list of all bot workflows. ## Managing Bot Workflows Change the descriptions and tags of bot workflows. ### Change the Description of a Bot Workflow Edit the description of a bot workflow tag to render it more precisely: 1. Open the **Bot Workflow Library** view in the **Process Automation** module. 2. Click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the panel of the workflow to edit. 3. In the **Edit ** window, change the description. 4. Click **Update**. ### Change the Tags of a Bot Workflow Add or remove tags of a bot workflow to define it more precisely: 1. Open the **Bot Workflow Library** view in the **Process Automation** module. 2. Click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the panel of the workflow to edit. 3. In the **Edit ** window, add or remove tags. 4. Click **Update**. ## Managing Bot Workflow Tags Create, edit, and delete bot workflow tags. Users assign the tags to bot workflows in RPA Manager and RPA Builder. Changes affect all tags, regardless of their assignment. ### Create a New Bot Workflow Tag Create a new bot workflow tag to categorize workflows: 1. Open the **Bot Workflow Library** view in the **Process Automation** module. 2. Click **Manage Bot Workflow Tags**. 3. In the **Bot Workflow Library Tags** view, click **Create**. 4. In the **Create Bot Workflow Library Tag** window, enter a name. 5. Click **Create**. ### Edit a Bot Workflow Tag Edit a bot workflow tag to define it more precisely: 1. Open the **Bot Workflow Library** view in the **Process Automation** module. 2. Click **Manage Bot Workflow Tags**. 3. In the **Bot Workflow Library Tags** view, click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the panel of the tag to edit. 4. In the **Edit Bot Workflow Library Tag** window, change the name. 5. Click **Update**. ### Delete a Bot Workflow Tag Delete a bot workflow tag if it’s no longer relevant: 1. Open the **Bot Workflow Library** view in the **Process Automation** module. 2. Click **Manage Bot Workflow Tags**. 3. In the **Bot Workflow Library Tags** view, click **Delete** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png))in the panel of the tag to delete. 4. Confirm the deletion. Assigned tags are removed from workflows upon deletion. ## See Also - [RPA Builder: Activity Library Explorer](https://docs.mulesoft.com/rpa-builder/latest/activity-library-explorer) - [Upcoming Process Changes](https://docs.mulesoft.com/rpa-manager/processoperations-upcomingprocesschanges) --- product: RPA Manager --- # Managing Users > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). If you use an Anypoint account to login to RPA Manager, refer to the [Anypoint Access Management documentation](https://docs.mulesoft.com/access-management/). > [!IMPORTANT] If you are your organization’s first admin user, you are responsible for creating all > other users. You can do this yourself or create another user with admin privileges to whom you > delegate this task. Manage the users of RPA Manager, RPA Recorder, and RPA Builder: - Create and delete users. - Edit the users' personal data. - Assign privileges or roles to users that enable them to work in specific modules and, access RPA Builder and RPA Recorder, and assume responsibility for process projects. - Assign a user to a process team. ## Before You Begin - The tenant admin is created first and can create other users. - If you are not a tenant admin, ask an administrator to [assign you the required privileges](#assign-privileges-to-a-user):
ActionRequired Privileges

Open the User Management module.

User Management Open

Create, edit, license, and delete users.

User Management Administration

## Create a User Create a user to give an employee access to RPA Manager, RPA Recorder, and RPA Builder. After creation RPA Manager sends an email with a one-time password to the new user. The new user needs to log in to RPA Manager and set a new password within the expiration time mentioned in the email. 1. Open the **Users** view of the **User Management** module. 2. Click **Create**. 3. Complete the form **Create a New User**: - **Login Name**: Name for the user to log on to RPA Manager. After creation, the login name can no longer be changed. - **Time Zone**: Time zone the user works in. All times not marked otherwise are shown in the time zone of the user. - **Available/Assigned Roles/Privileges**: Click on a role or privilege to assign it to or remove it from the user. 4. Click **Save**. ## Assign Privileges to a User A user needs privileges to view and use the RPA Manager modules. This ensures that only authorized users can access the modules. Assign privileges to a user when you create a new user or edit an existing user. 1. Open the **Users** view of the **User Management** module. 2. Click either **Create** in the header bar to create a new user or **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the panel of the user to edit. 3. In the form **<\[Create,Edit\]> a \[New\] User**, scroll down to the selection list **Available Privileges**. 4. Click a privilege to assign it to the user. 5. Repeat the previous step until the user has all needed privileges. 6. Click **Save**. ## Change Process Assignments of a User Instead of editing a project and adding a user to its project team, you can change several project assignments of a user at once: 1. Open the **Users** view of the **User Management** module. 2. Click **Assign Project** (![process-diagram symbol](/mulesoft/current/en-us/rpa-manager/_images/assignproject-icon.png)) in the panel of the user whose project assignments you want to change. The view **Assign Process** shows you a list of all processes where the user is part of the process team. To change permissions for assigned projects to reflect changed user responsibilities: 1. In the view **Assign Process**, for each process, select the checkboxes to permit the phases to the user. 2. Click **Save**. You cannot change permissions for the project manager, who always has permissions for every phase. The table does not show advanced permissions, which are sometimes needed to transfer a process to the next phase. To change these permissions, [edit the process data sheet](https://docs.mulesoft.com/rpa-manager/processautomation-manage#edit-an-automation-project) in the **Process Management** view of the **Process Automation** module. To assign additional processes to a user to support the process team: 1. In the view **Assign Process**, select a process from the dropdown **Select Process**. 2. In the table **Process List**, in the row of the added process, select the checkboxes of all phases the user needs to work in. 3. Click **Save**. To remove a user from a process team: 1. In the view **Assign process**, click **Delete** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) for each process to remove from the user. 2. Click **Save**. The project manager and the project owner cannot be deleted. To change them, use the function [**New Process Owner**](https://docs.mulesoft.com/rpa-manager/processautomation-manage#change-the-process-owner-of-an-automation-project) or [**New Project Manager**](https://docs.mulesoft.com/rpa-manager/processautomation-manage#change-the-project-manager-of-an-automation-project) in the **Process Management** view of the **Process Automation** module. ## Reset a User Password Reset a password if the user forgot it. RPA Manager sends an email that contains a new temporary password to the user. The user can then create a new password. 1. Open the **Users** view of the **User Management** module. 2. Click **Reset Password** (![key symbol](/mulesoft/current/en-us/rpa-manager/_images/resetpassword-icon.png)) in the panel of the user to edit. ## Change Your Password Change your own password regularly. You are logged out in the process and have to log in again. The password is used to log in to RPA Manager and RPA Builder. 1. Click on your user name in the navigation side bar. 2. Click **Profile** in the drop-down menu. 3. In the **Profile** view, click **Change password**. 4. Enter your old and new password. 5. Click **OK**. 6. Log in with your new password. ## Reset Your Password If you forget your password or if your one-time password expires, click the link on RPA Manager login page to reset it. You need to know your user name to reset your password. 1. Navigate to the RPA Manager login screen. 2. Click **Forgot your credentials?**. 3. In the **Forgot your credentials** form, enter your username. 4. Click **Continue**. A confirmation request for creating a new password is emailed to you. 1. Open the email in your email application. 2. Click **Request New Credentials**. A link to create a new password is emailed to you. The one-time password expires after 24 hours. 1. Open the email in your email application. 2. Copy or remember the one-time password. 3. Click **Sign In**. 4. In the RPA Manager login screen, enter your user name and the one-time password. > [!IMPORTANT] If you use two-factor authentication, append the time-based one-time password > (TOTP) to your one-time password (OTP) on login. > > For example, if your OTP is `Nz2tuQbtxpse?` and your TOTP password is `123456`, enter > `Nz2tuQbtxpse?123456` in the password field. 5. Click **Sign In**. 6. In the **Welcome to RPA Manager** form, enter a new password. 7. Confirm and remember the password. 8. Click **Reset Password**. ## Enable Two-Factor Authentication for Yourself Enable two-factor authentication (2FA) for extra security. When using two-factor authentication, you log in to the system with two mutually independent secret factors. The TOTP (Time-Based One-Time Password Algorithm) is set up in a special app on a mobile device. Every thirty seconds, a new password is generated and this can be used for authentication within this time period. Both the computer on which RPA Manager is installed, and the mobile device on which the app for generation of the one-time password is installed, must be able to determine the precise Unix time for verification of the user. For this reason, the time on the devices used should be synchronized with UTC (Universal Time Coordinated). 1. Click on your user name in the navigation side bar. 2. Click **Profile** in the drop-down menu. 3. In the **Profile** view, click **Enable Two-Factor Authentication**. 4. Follow the instructions in the window **Enable Two-Factor Authentication**. 5. Click **Enable Two-Factor Authentication**. Log in using your password and 2FA. > [!IMPORTANT] Append the time-based one-time password (TOTP) directly to your password on login. > > For example, if your password is `My1stPassword!` and your TOTP is `123456`, enter > `My1stPassword!123456` in the password field. ## Disable Two-Factor Authentication for Yourself Two-factor authentication can also be deactivated for you by an administrator. To disable two-factor authentication for yourself: 1. Click on your user name in the navigation side bar. 2. Click **Profile** in the drop-down menu. 3. In the **Profile** view, click **Disable Two-Factor Authentication**. Log in using only your password. You can [enable 2FA](#enable2faforyourself) again. ## Deactivate Two-Factor Authentication for a User To disable two-factor authentication for a user: 1. Open the **Users** view of the **User Management** module. 2. Click **Deactivate Two-Factor Authentication** (![user with open lock symbol](/mulesoft/current/en-us/rpa-manager/_images/userdeactivate2fa-icon.png)) in the panel of the user whose 2FA want to deactivate. 3. Confirm the deactivation. The user can [enable 2FA](#enable2faforyourself) again. ## Edit a User Edit users to change their data or permissions: 1. Open the **Users** view of the **User Management** module. 2. Click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the panel of the user to edit. 3. Edit the form **Edit a User**. For an explanation of the properties, see [**Create a new User**](#form-create-user). 4. Click **Save**. ## Remove a User Remove obsolete users. A user cannot be deleted if it is the owner or manager of a process. Deleted users cannot be restored. Use the **Deactivate** function to remove a user only temporarily. 1. Open the **Users** view of the **User Management** module. 2. Click **Delete** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) in the panel of the user to edit. 3. Confirm the removal. ## See Also - [User Roles and Permissions](https://docs.mulesoft.com/rpa-home/automation-userrolesandpermissions) --- product: RPA Manager --- # My RPA Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt In your personal module **My RPA**, you see an overview of your processes and your currently pending tasks. You can view process details, start automations and complete tasks. As a member of a center of excellence, in the **Team Backlog** view, you can assume responsibility for a previously evaluated process. As a project manager, you can start the automation of processes in the **My Backlog** view. The **My Processes** view lists all processes for which you are part of the process team. In the **My Process Board** view, you see your administrative process tasks. To view user tasks, which are to be processed by you or your center of excellence in ongoing productive processes, call up the **Team Tasks** view. User tasks, which you wish to process, are moved to your personal list **My User Tasks**. --- product: RPA Manager --- # Organization Management Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). If you use an Anypoint account to login to RPA Manager, refer to the [**Settings** documentation](https://docs.mulesoft.com/rpa-manager/settings-overview). If you use an RPA account to login to RPA Manager, the **Organization Management** module enables you to configure the currency and decimal sign to show in RPA Manager modules and configure your Anypoint Platform credentials, which enables you to publish a process automation to Anypoint Exchange. --- product: RPA Manager --- # Preparing Deployment > For the full documentation index, see: https://docs.mulesoft.com/llms.txt To reduce the time involved and the error rate in the maintenance of automations, you can create reusable data containers:
Data Container TypeUsageLinkable to

Global Variables

Store values of the types:

  • Alphanumeric

  • Integer

  • Float

  • Boolean

  • Coordinates

Activity parameters in run configurations of process automations

Credentials

Store login data for external applications and web services

Activity parameters in run configurations of process automations

## See Also - [RPA Builder: Activity Paramters](https://docs.mulesoft.com/rpa-builder/latest/toolbox-variable-handling-activity-parameters) - [Linkable Activity Parameters in Test Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#test-configuration-link-globals) - [Linkable Activity Parameters in Production Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#production-configuration-link-globals) - [Linkable Activity Parameters in Invocable Configurations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#invocable-configuration-link-globals) --- product: RPA Manager --- # Preparing Projects > For the full documentation index, see: https://docs.mulesoft.com/llms.txt A project defines the framework conditions for the automation of a process and is managed by a team. You must prepare some project properties before starting the automation of a process:
Project PropertyUsage

Category

A category describes the common environment of a set of processes in a few keywords, for example Customer Support Mythical University or Finance.

Process Applications

Process applications are third-party application installations that are required for the execution of a process, for example FinWiz - Mythical University - Computer 1 - Tokyo.

## See Also - [Create a Process Evaluation](https://docs.mulesoft.com/rpa-manager/processevaluation-propose#create-a-process-evaluation) - [Starting Automation of Approved Processes](https://docs.mulesoft.com/rpa-manager/myrpa-start) - [Create an Automation Project](https://docs.mulesoft.com/rpa-manager/processautomation-manage#create-an-automation-project) - [Assign Process Applications to Bots](https://docs.mulesoft.com/rpa-manager/botmanagement-manage#bot-assign-servicetimes-applications) - [Change Process Assignments of a User](https://docs.mulesoft.com/rpa-manager/usermanagement-manage#change-process-assignments-of-a-user) --- product: RPA Manager --- # Process Automation Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The **Process Automation** module is the heart of RPA Manager. After a citizen technologist evaluates processes and approves them for automation in the **Process Evaluation** module, you, as a project manager, create a project here for each suitable process by starting the automation from the **My RPA** module. A project defines the framework conditions for the execution of a process and is managed by a team. Processes go through several phases in sequence. 1. In the design phase, a citizen designer creates a model of the process using BPMN. 2. During the build phase, in RPA Builder, a RPA developer fills the model with concrete instructions for the bot. 3. In the test phase, a quality assurance team checks if the automated process delivers the required results. 4. Then you transfer the process to the production phase, where it is carried out fully automatically. The process team can revise the process continuously. ## Getting Started 1. List all applications required for the automation of a process in the **Process Applications** view of the **Process Automation** module. 2. Start the automation of a process in the **My Backlog** view of the **My RPA** module. 3. Create a project containing the settings and data of the process to be automated in the **Process Management** view of the **Process Automation** module. 4. In the design phase, record a process with RPA Recorder or model the process using BPMN. 5. In the build phase, use RPA Builder to edit or create a machine-readable program from the model. 6. In the test phase, run an automated process in a test environment. 7. In the production phase, deploy the automated process to a bot. Choose one or both of the following options: - Create a run configuration to execute the automated process by scheduling it in RPA Manager. - Create and publish an invocable configuration to Anypoint Exchange or Salesforce and use it with MuleSoft Composer or Salesforce Flow. ## Definitions ### BPMN _Business Process Model and Notation (BPMN)_ is a standard specification for diagrams to depict business processes. Such diagrams can be created directly by the process owner and easily translated into a machine-executable program. ## See Also - [Starting Automation of Approved Processes](https://docs.mulesoft.com/rpa-manager/myrpa-start) --- product: RPA Manager --- # Process Evaluation > For the full documentation index, see: https://docs.mulesoft.com/llms.txt A process evaluation comprises the benefits and feasibility of the automation of a real-life business process. To propose a process candidate for automation, you evaluate the candidate based on pre-configured criteria. As a project manager or a member of a center of excellence, you approve process candidates eligible for automation. ## Getting Started ### Think - What processes does your organization use? - Who is responsible for the processes? - Which criteria are necessary and suitable for evaluating the processes? - How can these criteria be described clearly and comprehensively? - Where does the data for evaluating the processes come from? - Which systems and data are needed for automating the processes? ### Prepare In the **User Management** module, give involved users the privileges and properties they need. After making the necessary systems available, define the applications, credentials, and global variables needed to automate the processes in the **Process Automation** module. ### Configure 1. In the **Evaluation Criteria** view, create the additional criteria needed to evaluate your processes. 2. In the **Evaluation Templates** view, compile the criteria needed to evaluate certain process types. ### Evaluate In the **Process Evaluation** view, create an evaluation based on a template for each of your processes. ### Automate Select the processes to automate and delegate the implementation to a project manager or a center of excellence. ### Administer Manage the automation projects in the **Process Management** view of the **Process Automation** module. ## Definitions ### Process Candidate A _process candidate_ is a real-life business process to propose for automation via a process evaluation. ### Project Manager A _project manager_ is responsible for the automation of a process across all automation phases. ### Center of Excellence If the users of a user group cover the entire range of competencies that are required for a specific part of the automation, the group is called a _center of excellence (CoE)_. Only user groups that are explicitly designated as centers of excellence can accept process automation tasks. ## See Also - [Considering Which Processes to Automate](https://docs.mulesoft.com/rpa-manager/processevaluation-consider) - [Configuring Process Evaluations](https://docs.mulesoft.com/rpa-manager/processevaluation-configure) - [Proposing a Process Candidate for Automation](https://docs.mulesoft.com/rpa-manager/processevaluation-propose) - [Approving a Process for Automation](https://docs.mulesoft.com/rpa-manager/processevaluation-approve) --- product: RPA Manager --- # Process Execution Plans > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The process execution plans show you the times processes are executed. Processes are executed if following prerequisites are fulfilled: - The current time lies inside the time interval defined by at least one schedule in the run configuration. - The current time lies inside the time interval defined by at least one service time of the bot. - The current time lies outside of all downtimes of all applications used by this process. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Process Execution Plans view and see all processes for which you are part of the process team.

RPA Operations Viewer, RPA Operations Manager, RPA Administrator

Process Execution Plans Open

Open the Process Execution Plans view and see all processes of all teams.

RPA Operations Manager, RPA Administrator

Global Process Execution Plans View

## View the Execution Timetable of a Process View the execution timetable to see the effective run time of a process. If there are more sessions assigned than free sessions available, the number of runs of a process within this timeframe depends on its priority. 1. In the **Process Execution Plans** view of the **Process Operations** module, click the icon **Execution timetable** in the row of the process you want to view. 2. Click on the Gantt chart of a configuration to view the composition of the effective runtime. ## See Also - [Deploying Automations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy) - [Queuing Process Sessions](https://docs.mulesoft.com/rpa-manager/processmonitoring-queue) --- product: RPA Manager --- # Process Monitoring > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The **Process Monitoring** module displays the execution of your processes in real time. In the **Bot State and Operation** view, you see the current status, the current deployment, and the number of completed tasks of each Bot. In the **Process Streaming** view, you see the number of configurations, RPA Bots, and sessions for each productive process. You can open a live view of the sessions of a process and watch the bot as it works. In the **Session Queues** view, you see the order of the process runs. The processes are queued according to their priority. ## See Also - [Streaming Processes](https://docs.mulesoft.com/rpa-manager/processmonitoring-stream) - [Queueing Process Sessions](https://docs.mulesoft.com/rpa-manager/processmonitoring-queue) --- product: RPA Manager --- # Process Operations > For the full documentation index, see: https://docs.mulesoft.com/llms.txt In the **Process Operations** module, you can get information about processes in the production phase: - View the execution timetables of processes that are currently in the production phase. - View and manage the deployment of processes. - View which user tasks have not been processed yet and reassign them. - View pending process changes and implement them. - View, record, monitor, and analyze the financial aspects of a process. --- product: RPA Manager --- # Profit Analysis: Process Frequency > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The widget **Profit Analysis: Process Frequency** shows how often a process has been executed productively within a specific interval compared to its previous frequency of execution. You can see at a glance whether a process can be executed more frequently by an bot or by a human employee, and to what extent the frequencies differ. ## Data Representation The execution duration of the individual configurations is shown as a line chart. A colored line corresponds to a configuration. The time interval is shown on the X axis, the execution duration of the individual runs is shown in seconds on the Y axis. The manual execution duration in seconds is represented by a horizontal red line. You can see the exact data if you hover the mouse over any point. If, in the evaluation of the Process, a value is entered under **Frequency per month**, this is displayed as a red line in the graphic. If you drag the mouse over a bar, you can see the exact number of Process executions on this day or in this month. If the display interval is less than one month, the value **Frequency per month** is divided by 30 to enable a comparison of the execution frequency of individual days. If the display interval is more than one month, the execution frequencies for each month are aggregated to enable a comparison of the monthly values. ## Configuration You can select an individual process, whose execution frequency is to be displayed, from the drop-down list. The processes are displayed below their category. Categories and processes are sorted alphabetically. You can only select from those processes for which you are a member of the process team. Other processes are not displayed. ## Drill-down This widget does not contain any drill-down data. --- product: RPA Manager --- # Profit Analysis: Process Time > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The widget **Profit Analysis: Process Time** shows the execution duration of a process by a bot compared to the time that a human requires to execute the same process. The times are shown individually for each configuration. ## Data Representation The execution duration of the individual configurations is shown as a line chart. A colored line corresponds to a configuration. The time interval is shown on the X axis, the execution duration of the individual runs is shown in seconds on the Y axis. The manual execution duration in seconds is represented by a horizontal red line. Drag the mouse over any point to see the exact data. ## Configuration You can select an individual process, whose execution duration is to be displayed, from the drop-down list. The processes are displayed below their category. Categories and processes are sorted alphabetically. You can only select from those processes for which you are a member of the process team. Other processes are not displayed. ## Drill-down This widget does not contain any drill-down data. --- product: RPA Manager --- # Proposing a Process Candidate for Automation > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You evaluate a process candidate to propose it for automation. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Process Evaluation module and view only processes that you have created yourself, that is, for which you are the process owner.

RPA Evaluations Viewer, RPA Evaluations Contributor, RPA Evaluations Manager, RPA Administrator

Process Evaluation Open

Display all processes in the Process Evaluation view.

RPA Evaluations Viewer, RPA Evaluations Contributor, RPA Evaluations Manager, RPA Administrator

Global Process Evaluation View

Create, edit, and delete evaluations.

RPA Evaluations Contributor, RPA Evaluations Manager, RPA Administrator

Process Evaluation Administration

Open the Evaluation Templates view.

RPA Evaluations Viewer, RPA Evaluations Contributor, RPA Evaluations Manager, RPA Administrator

Evaluation Templates Open

Create, change, and delete evaluation criteria.

RPA Evaluations Contributor, RPA Evaluations Manager, RPA Administrator

Evaluation Template Create, Evaluation Template Edit, Evaluation Template Delete

- Create appropriate categories in the view **Process Management** in the module **Process Automation**. Learn how to [manage categories](https://docs.mulesoft.com/rpa-manager/processautomation-prepare-project-category). ## Manage Process Evaluations Process evaluations assess the feasibility and benefits of a process’s automation. ### Create a Process Evaluation Create a process evaluation to propose a process candidate for automation: 1. In the **Process Evaluation** view of the **Process Evaluation** module click **Create**. 2. Complete the form **Create Evaluation**. 3. Click **OK** 4. Complete the form **Process Evaluation**: - **Manual process execution time**: Time that an employee requires to carry out the process once. In the list of evaluated processes, the value **Manual process execution time** is multiplied by the value **Frequency per month** to calculate the value **Effort/month**. - **Costs per process run**: Costs for a one-time execution of the process. In the list of evaluated processes, the value **Costs per process Run** is multiplied by the value **Effort/month** to calculate the **Costs/month** value. - **Frequency per month**: Number of times the process is carried out within a one-month period. This field can only be completed if a value exists in the **Manual process execution time** field. In the list of evaluated processes, the value **Frequency per month** is multiplied by the value **Manual process execution time** to calculate the **Effort/month** value. - **Category**: A category describes the environment of a process in a few keywords. Choose a category from the list. - **Qualifiers/Benefits**: Drag the slider to the appropriate values. **Exclude** unnecessary criteria. 5. Click **Save** ### Edit a Process Evaluation Edit a process evaluation to correct errors: 1. In the **Process Evaluation** view of the **Process Evaluation** module, click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the row of the evaluation to edit. 2. Edit the form **Process Evaluation**. 3. Click **Save**. ### Delete a Process Evaluation Delete process evaluations that you no longer need: 1. In the **Process Evaluation** view of the **Process Evaluation** module, click **Delete** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) in the row of the evaluation to delete. 2. Confirm the deletion. ## See Also - [Manage Process Categories](https://docs.mulesoft.com/rpa-manager/processautomation-prepare-project-category) --- product: RPA Manager --- # Queuing Process Sessions > For the full documentation index, see: https://docs.mulesoft.com/llms.txt When more process configurations are deployed than sessions are available, RPA Manager must decide the order in which the processes are executed. You set the priority of a process configuration by assigning it a number between 1 and 200. The smaller the number, the higher the priority. RPA Manager inserts the deployed configurations in the session queue, as soon they are started. Test configurations and invocable run configurations automatically have the highest priority. The processes are executed in the following order: 1. Invocable process configurations 2. Test configurations 3. Production configurations in ascending order of their assigned priority numbers If two or more configurations have the same priority, the ones deployed first are executed first. ## View the Queue View the currently processed, waiting, and future process runs in the **Session Queues** view. 1. Open the **Session Queues** view of the **Process Monitoring** module. 2. Select the time interval for the future processes and click **Apply**. ## See Also - [Deploying Automations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy) - [Process Monitoring](https://docs.mulesoft.com/rpa-manager/processmonitoring-overview) - [Streaming Processes](https://docs.mulesoft.com/rpa-manager/processmonitoring-stream) --- product: RPA Manager --- # Reassigning RPA Assets > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). If an RPA user or team is deleted or disabled in Access Management, the **Reassign Assets** tab in the **Admin Settings** view of the **Settings** module shows RPA assets that were assigned to this user or team. All users with the **Reassign Users** or **RPA Administrator** permission get an email when an RPA asset is orphaned because its last assigned user is deleted. The **Reassign Assets** tab can also show all RPA assets of an existing user. You can reassign the following RPA assets to another user: - Credentials - Process Evaluations - Process Projects - Process Board Tasks - Alert Targets The following assets are deleted on the deletion of the user: - Private dashboards - User API Keys User Tasks are not shown in the **Reassign Assets** view and can be reassigned via the **Unprocessed User Tasks** view or via the run configurations of a process. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

View configured settings for your organization.

RPA Administrator

Organization Management Open

Add or modify settings for your organization.

RPA Administrator

Organization Management Administration

Reassign RPA Assets.

RPA Administrator

Reassign Users

- Ensure that the user to whom you reassign an asset has the required permissions and knowledge to handle that asset. ## Reassign One RPA Asset Reassign one asset to another user: 1. Open the **Reassign Assets** tab in the **Admin Settings** view of the **Settings** module. 2. To reassign an asset of an existing user, click the **Unassigned assets** drop-down and select the user. You can also search for the user’s name to filter the list. 3. Click the **Reassign** on the panel of the asset to reassign. 4. Check and edit the **Reassign Owner** form: - In **Assign To**, select a user. - Select **Send email to the new owner** to inform the selected user about the reassignment. 5. Click **Save**. RPA Manager removes the reassigned asset from the list. A toast message informs you about the success of the reassignment. ## Reassign Several RPA Assets to One User Reassign several assets to another user at once: 1. Open the **Reassign Assets** tab in the **Admin Settings** view of the **Settings** module. 2. To reassign assets of an existing user, click the **Unassigned assets** drop-down and select the user. You can also search for the user’s name to filter the list. 3. Check the panel of every asset to reassign. 4. Check and edit the **Reassign Owner** form: - In **Assign To**, select a user. - Select **Send email to the new owner** to inform the selected user about the reassignment. 5. Click **Save**. RPA Manager removes the reassigned asset from the list. A toast message informs you about the success of the reassignments. ## See Also - [Access Management](https://docs.mulesoft.com/access-management/) --- product: RPA Manager --- # RPA Manager Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). RPA Manager is the cloud-based control plane for the automations that is integrated into Anypoint Platform. RPA Manager enables you to do the following: - Manage user access and permissions. - Evaluate the viability and financial benefits of implementing an automation. - Design and document RPA processes. - Test and deploy automations. - Manage and monitor deployed automations. To access RPA Manager, navigate to `[https://.rpa.mulesoft.com](https://\.rpa.mulesoft.com)`, where `` represents your organization’s instance. If you are not sure about this value, contact your organization’s administrator. Ensure that access to this URL is possible from your organization. RPA Builder, RPA Bot, and RPA Recorder use this URL to connect to your RPA Manager instance. ## Anypoint Platform Integration MuleSoft RPA is integrating with Anypoint Platform to unify the login experience and provide support for external identity providers (IdPs). Refer to [Anypoint Platform Integration Overview](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview) for an overview of the changes and requirements. If you are unsure whether your org is integrated, open the **Home** module in RPA Manager: - If you are using an RPA account for login, there is a quick link to Composer: ![Screenshot of the Composer quick link panel in the Home module of RPA Manager](/mulesoft/current/en-us/rpa-manager/_images/rpa-manager-home-premigration.png) - If you are using an Anypoint account for login, there is a quick link to Access Management: ![Screenshot of the Composer quick link panel in the Home module of RPA Manager](/mulesoft/current/en-us/rpa-manager/_images/rpa-manager-home-postmigration.png) ## See Also - [Anypoint Platform Integration Overview](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview) - [Access Management](https://docs.mulesoft.com/access-management/) - [What to Do if You Forgot Your Password](https://docs.mulesoft.com/rpa-manager/usermanagement-manage#iforgotmypassword) --- product: RPA Manager --- # Settings Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). If you use an RPA account to login to RPA Manager, refer to the [**Organization Management** documentation](https://docs.mulesoft.com/rpa-manager/organizationmanagement-overview). The **Settings** module enables you to do the following: - Create user API keys for connecting to RPA processes from Salesforce products. - Configure general settings. - Reassign the RPA assets of deleted or disabled users. --- product: RPA Manager --- # Starting Automation of Approved Processes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The **Team Backlog** view contains a list of all evaluated processes for which you can claim or reject responsibility as member of a center of excellence. If you claim a process, it is moved to your **My Backlog** view of the **My RPA** module. Your **My Backlog** view also contains processes approved directly to you as a project manager. You can start the automation of a process as a project manager from your backlog. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Start the automation of a process.

RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Administrator

Process Automation Open, Process Create

- If there is no fitting category for the process in the **Process Management** view of the **Process Automation** module, create a new one. ## Claim a Process Claim a process to assume the project manager role for the automation of this process. The process is moved to the **My Backlog** view of the **My RPA** module. 1. Open the **Team Backlog** view of the **My RPA** module 2. Click the icon **Claim**. ## Create a Process Project Create a project for the process that contains administrative data. On the **Settings** tab, you enter general data that is required for running the Process. This includes team members and applications for execution of the Process. On the **Process Costs** tab, you enter data with which you can calculate the costs and the break-even point of the process automation. This data is required in the Finance Analysis view in the Process Operations module. 1. Open the **My Backlog** view of the **My RPA** module. 2. Click the icon **Start automation**. 3. Complete the form **Create process**: - **Setting**: - **Process Owner**: User who proposed the process for automation via a process evaluation. - **Required Applications for Process**: Select all applications here that are required to carry out the process. All applications that have been created in the **Process Applications** view of the **Process Automation** module are displayed in the drop-down list and can be removed from the input field by clicking the **X**. It is important to select all required applications here to ensure that the process can only be implemented subsequently by robots that can use these applications. - **Process Team**: The process team is a group of employees who work together on execution of the process automation. Select all team members from the text selection field. Then, by selecting the relevant checkboxes in the table, you can authorize the team members to work on the processes in the various phases. By default, each team member has authorization to transfer the process from their own phase to the next phase. If approval for the next phase is only to be carried out by specific team members, then select the checkbox **Advanced Permissions** to assign authorizations for approval separately. All team members have read access to the project in all phases. The project manager is always part of the team and also always has all authorizations. If the checkbox **Advanced Permissions** is deselected, the values of this column are no longer taken into account. In that case, only that user who has authorization to work on a phase can transfer the Process to the next phase. - **Category**: A category describes the environment of a process in a few keywords. Choose a category from the list. - **Use Process Board**: Select this checkbox to use a process board. Process boards contain administrative process tasks. The tasks transition from **To-do** via **In progress** to **Completed**. If you deselect this checkbox, the previous tasks remain, but are no longer displayed and are no longer considered for phase transitions. As soon as you select the checkbox again, the tasks are displayed and taken into account again. - **Create automatic Phase Release Tasks**: Select this checkbox to create automatic phase release tasks. Phase changes can only be made if the corresponding task has reached the status **Completed**. - **Process Costs**: - **Initial Investment for the Process Automation**: The initial investment for the acquisition of the MuleSoft RPA solution and the necessary infrastructure is required for the finance analysis. 4. Click **Save** ## Reject a Process Project Reject processes that were approved to the wrong center of excellence. The process is removed from the **My Backlog** or the **Team Backlog** view in the **My RPA** module and appears with status **Rejected** in the **Process Evaluation** view in **Process Evaluation** module. 1. Open the **My Backlog** or the **Team Backlog** view of the **My RPA** module. 2. Click the icon **Reject**. --- product: RPA Manager --- # Streaming Processes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt In the **Process Streaming** view, you see the number of configurations, RPA Bots, and sessions for each productive process. You can open a live view of the sessions of a process and watch the bot as it works. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Process Streaming view.

RPA Operations Viewer, RPA Operations Manager, RPA Administrator

Process Streaming Open

- Only productive processes for which at least one configuration has been created and for which you are a member of the process team are displayed. - Check [**Enable Taskbar (Start menu, taskbar buttons)**](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#runconfig-execution-enabletaskbar) in the run configuration to view the desktop of the computer that runs the process. Otherwise, a black screen is shown. - [**Send images for process streaming**](https://docs.mulesoft.com/rpa-bot/latest/configuration#session-settings) must be enabled in the RPA Bot Configurator on the computer, where the process runs. ## Watch a Bot at Work Watch the process stream to see what is happening right now. 1. In the **Process Streaming** view of the **Process Monitoring** module, click the icon **Show process streams** in the row of the **Process** you want to watch. 2. Toggle **Off / On** to activate and deactivate a stream. 3. Click the **Full Screen** icon in the stream panel to display it in full-screen mode. 4. Press `ESC` to exit full-screen mode and return to the overview page. ## See Also - [Deploying Automations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy) - [RPA Bot Configurator - Session Settings](https://docs.mulesoft.com/rpa-bot/latest/configuration#session-settings) --- product: RPA Manager --- # Supporting Bots > For the full documentation index, see: https://docs.mulesoft.com/llms.txt A bot needs to know who it belongs to. You create API keys which the bots use to connect to RPA Manager. If a bot only needs to work at specific times, you assign it service times. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Bot Management module.

RPA Bots Manager, RPA Operations Viewer, RPA Operations Manager, RPA Administrator

Bot Management Open

Manage service times.

RPA Bots Manager, RPA Administrator

Servicetime Create, Servicetime Edit, Servicetime Delete

## Manage API Keys An API key is required during installation of a bot. The bot connects to RPA Manager with its API key. For security reasons, RPA Manager shows the API Key only during creation. Copy your API Key and save it to a secure place. If you lose an API Key, create a new one. ### Create an API Key Create a new API key for each bot before installation or when you lose access to one. To create an API key: 1. Open the **API Key** view of the **Bot Management** module. 2. Click **New API Key**. 3. In the **Create Bot API Key** window, enter a name and description and click **OK**. 4. In the **Key Created!** window, click **Copy to clipboard**. 5. Copy the API key to a secure place. 6. Click **Close**. Copy your saved API key into the configuration settings of the bot during installation. You can change the bot API Key with RPA Bot Configurator. ### Edit an API Key Edit an API key to change its name or description. To edit an API key: 1. Open the **API Key** view of the **Bot Management** module. 2. Click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the row of the API key to edit. 3. In the **Edit Bot API Key** window, change the name or description and click **OK**. ### Remove an API Key Remove API keys you no longer need. When you delete an API key, the system does not check whether the key is assigned to a bot. If you deleted an API key that is in use, the bot can no longer connect to RPA Manager until a new API key is assigned. To delete an API key: 1. Open the **API Key** view of the **Bot Management** module. 2. Click **Remove** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) in the row of the API key to remove. 3. Confirm the removal. ## Manage Service Times Service times are repeatable time intervals that define when a service is available. Assign them to bots to determine when a bot can execute processes. You can use a service time to simulate the regular weekly working hours at your company, for example. The bot can then work at the same time as its human colleagues if tasks are interdependent, or at different times if you want it to use resources that other employees are not currently using. Bots execute processes deployed to them only if they are within one of their service times. You can assign multiple service times to a bot. If you do not assign service times to a bot, it works 24/7. Specify the service time in one time zone. If the bot that you assign the service time to is installed on a computer that uses a different time zone, the service time interval is converted to the bot’s time zone. If you assign the service time to multiple bots in different time zones, all bots execute processes simultaneously. The time intervals might change, depending on daylight saving time. For example, if you specify a service time that starts at 9:30 AM and ends at 5:30 PM in Buenos Aires time (ART (UTC -3)) and the bot is installed on a computer in Berlin (CET (UTC +1)), the bot executes processes between 1:30 PM and 9:30 PM in Berlin time. You can create, edit, and remove service times. Learn how to [assign service times to a bot](https://docs.mulesoft.com/rpa-manager/botmanagement-manage#bot-assign-servicetimes-applications). ## Create a Service Time Create service times to coordinate bot working hours. The names of the service times do not have to be unique. To avoid misinterpreting the effective schedule runtimes, include the time zone in the name of the service time. For example, name your service time `Regular working hours - 9 AM - 5 PM - Mystical University - Buenos Aires (ART (UTC -3))` or `Low resource usage time - 5 PM - 9AM - Mystical University - Berlin (CET (UTC +1))`. 1. In the **Service Times** view of the **Bot Management** module, click **Create**. 2. In the **Create Service Time** window, complete the form: - **Timezone**: Specify a downtime in the time zone in which it occurs. If the bot that you assign the downtime to is installed on a computer that uses a different time zone, the downtime interval is converted to the bot’s time zone. If you assign the application to multiple bots in different time zones, all bots pause executing processes that use that application simultaneously. The time intervals might change, depending on daylight saving time. For example, if you specify a service time starting at 9:30 AM and ending at 5:30 PM in Buenos Aires time (ART (UTC -3)) and the bot is installed on a computer in Berlin (CET (UTC +1)), the bot executes processes between 1:30 PM and 9:30 PM in Berlin time. - Interval: - **From**: Start of the time interval. As of this time, the scheduled action is executed. The start time must not be in the past and it must not be later than the end time. Even if you specify a Repeat on a specific day of the week or month that does not correspond to the start time, the schedule is started at this time anyway. The day specified under Repeat is then taken into account from the first repetition onward. - **To**: End of the time interval. As of this time, the scheduled action is no longer executed. The end time must not be earlier than the start time. If you use the Repeat option, the duration of the time interval is defined by the difference between the From and To times. - **All day**: Select the checkbox **All day** to execute the action throughout the day. It then begins on the first day at 12:00 midnight and stops being executed at 12:00 midnight of the next day (in the case of one-day intervals) or at 12:00 midnight on the day after the last day (in the case of multi-day intervals). - **Repeat**: Select the checkbox **Repeat** if the selected time interval is to be used repeatedly. Then, under **Repeats**, you can choose whether the **From-To** time interval is to be repeated every minute, hourly, daily, weekly, monthly, or yearly. The duration of the contained time interval and the start time are taken into account. The duration of the time interval is defined as the difference between the **From** and **To** times. The **From** time is the start time of the first execution. The start time of repetitions depends on the other set values. To execute the repeats only with reference to the time of day, you should ensure that the start and end dates are identical. If the interval specified covers multiple days, a new multi-day interval begins with every repetition. This can lead to a situation in which the scheduled time interval lasts longer than expected because the full number of days contained in the **From-To** interval is executed once again during the last repetition. With schedules that are not all day, the actions in each repetition are executed for the duration of the interval specified in the **From** and **To** fields. - **Repeat minutely**: If you select **Repeat minutely**, the planned action is executed every minute during the interval specified in the **To** and **From** fields. You can select whether you want to repeat the action every minute or only every _n_\-th minute. _n_ here stands for any integer number between 1 and 59. - **Repeat hourly**: If you select **Repeat hourly**, the planned action is executed hourly during the interval specified via **To** and **From**. You can select whether you want to repeat the action every hour or only every _n_\-th hour, where _n_ here stands for any integer number between 1 and 23. - **Repeat daily**: If you select **Repeat daily**, the planned action is executed daily during the interval specified via **To** and **From**. You can select whether you want to repeat the action every day or only every _n_\-th day. _n_ here stands for any integer number between 1 and 31. - **Repeat weekly**: If you select **Repeat weekly**, the planned action is executed weekly during the interval specified via **To** and **From**. You can select whether you want to repeat the action every week or only every _n_\-th week. _n_ here stands for any integer number between 1 and 52. You can also select the weekday on which the scheduled action is to be executed. - **Repeat monthly**: If you select Repeat monthly, the planned action is executed monthly during the interval specified via **To** and **From**. You can select whether you want to repeat the action every month or only every _n_\-th month. _n_ here stands for any integer number between 1 and 12. You can also choose whether the repeat refers to the day of the month or the day of the week. If the selected day is the last day of a month, you can also choose whether the execution day is always the last day of a month, as the number of days in each month is different. If the selected day is the fourth such weekday of a month, you can also choose whether the execution day is always the fourth or last such weekday of a month, as the number of weeks in each month is different. - **Repeat yearly**: If you select **Repeat yearly**, the planned action is executed annually during the interval specified via **To** and **From**. You can select whether you want to repeat the action every year or only every _n_\-th year. _n_ here stands for any integer number between 1 and 20. - **Ends**: If you select **Never** under Ends, the time period is repeated over and over. If you select **After n occurrences** under **Ends**, the time period is repeated _n_ times. _n_ here stands for any integer number between 1 and 100. If you select **Ends on **, the time interval is no longer repeated after this date. ## Edit a Service Time Edit a service time if it has changed. If a changed service time is already used by a bot, it is updated automatically there. 1. In the **Service Times** view of the **Bot Management** module, click **Edit** (![pen-to-paper symbol](/mulesoft/current/en-us/rpa-manager/_images/edit-icon.png)) in the row of the service time to edit. 2. In the **Edit Service Time** window, change the data and click **OK**. ## Remove a Service Time Remove service times no longer effective. The deleted service time is also removed from the service times of a bot. If the deleted service time is the only one that was used by a bot, the bot uses the default service time (24/7). 1. In the **Service Times** view of the **Bot Management** module, click **Remove** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) in the row of the service time to remove. 2. Confirm the removal. ## See Also - [RPA Bot Installation](https://docs.mulesoft.com/rpa-bot/latest/installation) - [RPA Bot Configuration](https://docs.mulesoft.com/rpa-bot/latest/configuration) - [Deploying Automations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy) --- product: RPA Manager --- # Troubleshooting Bots > For the full documentation index, see: https://docs.mulesoft.com/llms.txt If a bot has status **OK**, but seems not to work properly, download its log files or restart the bot. If the bot has status **SUSPENDED**, review the execution plans. If a bot has status **STOPPED**, **OVERDUE**, or **UNKNOWN**, an IT administrator needs to log on to the computer the bot is installed on and needs to troubleshoot it there. If a process execution fails when a bot runs correctly, turn on debug logging to get help detecting the cause. ## View the Planned Process Executions If you’re not sure why a bot isn’t processing, review the execution plans: 1. In the module **Bot Management**, open the view **Bot Execution Plans**. 2. In the table, click **Execution timetable** (![calendar symbol](/mulesoft/current/en-us/rpa-manager/_images/executiontimetable-icon.png)) in the row of the bot you want to check. The execution timetable shows the effective runtime of all calendar scheduled run configurations assigned to the bot. The execution timetable does not show run configurations using other types of scheduling, such as on-demand, interval or cron-expression. 1. Click **Configure Execution Timetable** (![wrench symbol](/mulesoft/current/en-us/rpa-manager/_images/configure-icon.png)) to change the time interval of the table and to select the shown configurations. 2. Click **OK**. 3. In the **Execution Timetable**, click a colored bar in the row of the configuration you want to check to view the composition of the effective runtime. The bot runs a process when the bot’s service time overlaps with the configuration schedule. If the process uses applications, the bot doesn’t run the process during the downtimes of any of those applications. RPA Manager displays all times in your local time. Times from bots and applications living in other time zones are converted to your local time. Hover over the bars to see which service times, downtimes, and schedules are contained in the execution times. ### Example of the Effective Runtime Composition ![Overview of how the effective runtime is composed from schedules, service times and downtimes](/mulesoft/current/en-us/rpa-manager/_images/rpa_botmanagement_botexecutionplans_example_effectiveschedulecomposition.png) This example shows the planned process executions from the view of a user who lives in Rome (GMT+01:00). All shown times are converted to the user’s time zone. The production configuration uses a schedule that is repeated daily from 12:30 PM to 20:30 PM regardless of time zones. The bot is installed on a computer that uses the UTC timezone. It has an assigned service time defined in Japanese time (GMT+09:00). The process uses an application installed on a computer in Buenos Aires (GMT-03:00). There was a power outage during which the application was down from 10:00 AM until 10:30 AM. When schedules and service times overlap and no used applications is down, the bot executes the process. In this example, a downtime takes place in the middle of the scheduled time. The execution is interrupted during that time. Because the service time ends before the scheduled run time, the effective runtime is shortened. As you can see in the **Schedule Chart**, the service times and the downtimes are converted to the bot’s timezone. They are observed simultaneously across all time zones. The bots interpret the schedule to be valid for their own time zone. It is observed at different times across all time zones. Learn how to [manage service times](https://docs.mulesoft.com/rpa-manager/botmanagement-support#manage-service-times). Learn how to [manage applications](https://docs.mulesoft.com/rpa-manager/processautomation-prepare-project-application). Learn how to create [production](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#production-configuration) and [invocable](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#invocable-configuration) configurations. ## View the Bot Log Messages The bot log messages contain detailed information about a process run. RPA Manager lists each bot activity with information about the run result and displays bot messages contained in activities under **Additional Customer Info**. To view the bot log messages: 1. Open the **Process Run Statistics** view in the **Bot Management**. Alternatively, in the **Process Automation** module: - From within a project in the test or production phase, click on a run result number in the **Run Results** panel. 2. Click **Bot Message Log** (![list symbol](/mulesoft/current/en-us/rpa-manager/_images/botmessagelog-icon.png)) in the table row of the bot you want to read messages from. Bot messages might be concatenated and truncated. To view the complete bot log, download the log files. ## Download the Log Files of a Bot Download the zipped bot log files to check for error or warning messages or to view screenshots. The package contains the folders `BotTrace` and `RpaBotLogfiles`. The trace folder contains the log files of the Secure Sessions, while the log files folder contains the installation and configuration data, as well as the execution log of the bot. This option is only available when the bot has the status OK. An IT administrator can configure the content of the package in the RPA Bot Configurator on the computer where the bot is installed. 1. Open the **Bots** view of the **Bot Management** module. 2. Click **Download Logfiles** (![disk-with-downwards-arrow symbol](/mulesoft/current/en-us/rpa-manager/_images/download-icon.png)) in the row of the bot you want to read the log files from. 3. Extract the contents and view the relevant files. ## Turn On Debug Logging Debug Logging is supported by RPA Bots with version 1.3.4 and later. If a process execution fails when a bot runs correctly, turn on debug logging for at least the time span of the next process run to get help detecting the cause. Then download the log files of the bot and send them to the support team if you need help analyzing the cause of the failure. To turn on debug logging, complete the following steps: 1. Open the **Bots** view of the **Bot Management** module. 2. On the panel of the bot to debug, click **Turn on debug logging** (![bug symbol](/mulesoft/current/en-us/rpa-manager/_images/debug-icon.png)). 3. In the **Enable time limited debug logging** window, enter a time interval in minutes and click **Start debug logging**. After the time interval lapses, the log level returns to the default. If a user sets a new debug interval while the bot is still in debug mode, the interval restarts with the new value. You cannot see the interval for which the bot is in debug mode or if it is in this mode. ## Restart a Bot Use this function to restart a bot to ensure that all the processes the bot is currently executing are completed properly before the bot is stopped. Before a process is started, the bot has to check a variety of conditions. For example, whether it’s within its assigned service time and whether all the applications that the process needs for execution are available. The bot divides these tasks, which are independent from one another, into threads, which can run simultaneously (asynchronously). The bot then waits until all the tasks are complete and then either continues with starting the process or checks the conditions again. In rare cases, an individual thread might have an error due to unforeseen circumstances, but can’t report it back to the bot. In this case, the Bot remains in wait status and can’t execute any more processes. The latter might be the case when the bot has the status OK and a deployed process is within an effective runtime interval, but no process has been started for several minutes. When you restart the bot, the bot and all of its threads are initially stopped after the bot has completed the pending tasks. The restart is then performed in a clean environment, which means the problem should no longer occur. Restarting a bot only works if that bot has the status OK. Otherwise RPA Manager places the restart in the task list and executes it as soon as the bot is OK again. 1. In the **Bots** view of the **Bot Management** module, click the **Restart** icon in the row of the bot you want to restart. 2. Wait a few seconds and refresh the browser to see the effect. ## See Also - [RPA Builder: Toolbox - Write Bot Message](https://docs.mulesoft.com/rpa-builder/latest/toolbox-system-write-bot-message) - [Known Issues](https://help.salesforce.com/s/issues) --- product: RPA Manager --- # Upcoming Process Changes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The activity library of RPA Builder enables RPA developers to save activities that can be reused in different processes, such as login procedures or the creation of data sets. To reuse a saved activity, an RPA developer can import a reference to this activity into a bot task. To reuse a saved activity, an RPA developer can import a reference to this activity into a bot task. If an RPA developer edits a referenced activity, RPA Manager shows a label with the number of changed activities next to the navigation items **Process Operations** and **Upcoming Process Changes**. The **Upcoming Process Changes** shows which processes contain the changed activities and enables you to deploy the latest version. ## Before You Begin - Ask an organization administrator in Access Management to assign you the required permissions:
ActionRPA PermissionDeprecated RPA Permission

Open the Upcoming Process Changes view of the Process Operations module and view the changes.

RPA Operations Manager, RPA Administrator

Upcoming Process Changes Open

Deploy upcoming process changes.

RPA Operations Manager, RPA Administrator

Upcoming Process Changes Administration

- To deploy a process change, the project must be in the design, build, or test phase. ## View Upcoming Process Changes When an RPA developer edits a deployed activity in the activity library in RPA Builder, a label with the number of affected instances shows next to the **Process Operations** or **Upcoming Process Changes** navigation entry. To view the changes: 1. Open the **Upcoming Process Changes** view in the **Process Operations** module. 2. View the descriptions in the table. 3. Click **Show Changes** (![eye symbol](/mulesoft/current/en-us/rpa-manager/_images/show-icon.png)) in the row of the edited activity to compare the deployed version with the latest version of that activity. ## Map BPMN Elements to Process Activities If a process contains the same activity more than once, use your browser’s developer tools to find out which BPMN element contains the referenced activity revision: 1. Open the **Upcoming Process Changes** view in the **Process Operations** module. 2. Right-click on a process name and open the project in another tab. 3. In the new tab, open the **Automation** panel. 4. Right-click on one of the possible activities and choose **Inspect** from the browser’s context menu. The **Elements** panel of the browser shows the highlighted source code of the element. To map this element to an element shown in the **Upcoming Process Changes** table: 1. In the **Elements** panel, look up the text next to **data-element-id=** contained in the source code belonging to the highlighted text. 2. Switch back to the **Upcoming Process Changes** tab. 3. Compare the **data-element-id** with the **BPMN Element** id in the list of all process changes. Matching activities have the same id. ![Screenshots of the Upcoming Process Changes table and the Automation Panel’s developer tools elements view with an element highlighted. An arrow shows matching IDs.](/mulesoft/current/en-us/rpa-manager/_images/rpa_processOperations_UpcomingProcessChanges_WhichBPMNElement.png) ## Deploy the Latest Version of an Activity To ensure that the processes use an appropriate version of a referenced activity, deploy the latest version to processes in the design, build, or test phase. Before you deploy the latest version of an activity: - [View the upcoming process changes](#view-upcoming-process-changes). - If a process contains the same activity more than once, [ensure that you know which activity to select](#map-bpmn-elements-to-process-activities). - If processes containing an upcoming change are in the produtcion phase, transfer the processes to the test phase to deploy the changed activity. To deploy the latest version of an activity: 1. Open the **Upcoming Process Changes** view in the **Process Operations** module. 2. Select the activities to deploy. 3. Click **Deploy**. Test the updated processes before transfering them to production phase. ## Deploy An Earlier Version of an Activity To ensure that a process uses an appropriate version of a referenced activity or to undo a prior deployment, change the version of a referenced activity in RPA Builder: 1. Transfer the process to the build phase. 2. Open the process in RPA Builder. 3. [Change the revision of the referenced activity using RPA Builder](https://docs.mulesoft.com/rpa-builder/latest/activity-library#change-the-revision-of-a-referenced-activity). 4. Upload the process to RPA Manager. 5. Transfer the process to the next phase. Test the updated process before transferring it to the production phase. ## See Also - [RPA Builder: Activity Library Explorer](https://docs.mulesoft.com/rpa-builder/latest/activity-library-explorer) --- product: RPA Manager --- # Usage Summary > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Create a usage report for the selected date range. The report shows automation usage for your organization and is useful for reviewing consumption, planning, and billing. ## Create a Usage Report Follow these steps to create a usage report in RPA Manager: 1. Open the **Process Operations** module. 2. Click **Usage Summary**. 3. Specify the desired date range and click **Create Usage Summary**. 4. Optionally, click **Print** (![The Print icon](/mulesoft/current/en-us/rpa-manager/_images/print-icon.png)) to print or download the report. ## See Also - {xref to new Automation Credits location}. --- product: RPA Manager --- # Used Bot Minutes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt In the **Used Bot Minutes** widget, you see how many minutes all bots have used in the selected time interval. ## Data Representation The used bot minutes are displayed as a number. ## Configuration This widget cannot be configured. ## Drill-down This widget has no drill-down. --- product: RPA Manager --- # User Management Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This topic is affected by the [Anypoint Platform integration](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview). If you use an Anypoint account to login to RPA Manager, refer to the [Anypoint Access Management documentation](https://docs.mulesoft.com/access-management/). In the **User Management** module, you manage the users of RPA Manager and RPA Builder: - Create and delete users. - Edit a user’s personal data. - Assign privileges or roles to a user that enable a user to work in specific modules. - Create roles to combine privileges. - License users for RPA Builder access. - Mark a user as project manager. - Assemble teams for task sharing. - Mark teams as centers of excellence. - Create user API keys to configure an API connector in MuleSoft Composer. --- product: RPA Manager --- # Widgets > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The dashboard information consists of the contents of various widgets. A widget is a movable and scalable pane. We can roughly divide widgets into two groups. There are widgets that monitor the current situation and, for which, a shorter analysis interval and more frequent refreshes are appropriate. The second group of widgets enables an overview of the development of process automation over longer time periods. The widgets that are used to assess the current situation include **Analysis Packages**, **Current Bot Status**, **Bot Workload**, **Used Bot Minutes**, and **Business Process Performance**. If you keep an eye on these widgets, you can allocate resources flexibly and react quickly to problems. The widgets that provide a more general overview of the progress of process automation in your company include **Automation Management**, **Profit Analysis: Process Time**, **Profit Analysis: Process Frequency**. These widgets help you to identify unexploited potential and to plan over the long term. You can see at a glance what advantages have accrued from the automation of a process.