# mulesoft RPA - Full Documentation --- product: RPA --- # Anypoint Access Management RPA Permissions > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Administrator The RPA Administrator permission includes all other permissions, except for the RPA Project Manager permission. A user with this permission can only view or administer automation projects if the user is part of the process team. RPA Automations Designer The RPA Automations Designer permission enables an RPA developer, citizen technologist, or knowledge source (such as a business analyst or process owner) to do the following in RPA Manager: - Create automation projects. - Record or design models of business processes that a process manager or center of excellence approved for automation. - Document and edit the applications required for performing the processes. The RPA Automations Designer permission contains the following deprecated RPA permissions: - Application Create - Application Edit - Process Automation Open - Process Create - Process Recording RPA Automations Contributor The RPA Automations Contributor permission enables an RPA developer, citizen technologist, or knowledge source (such as a business analyst or process owner) to do the following: - In RPA Manager: - Create automation projects. - Record or design models of business processes that a process manager or center of excellence approved for automation. - Document and edit the applications required for performing the processes. - Create and edit global variables to link to activity parameters created with RPA Builder. - In RPA Builder: - Build the automation based on the model. - Reuse activities from the Activity Library. The RPA Automations Contributor permission contains the following deprecated RPA permissions: - Activity Library Open - Application Create - Application Edit - Builder Usage - Global Variables Create for Productionphase - Global Variables Create for Testphase - Global Variables Edit for Productionphase - Global Variables Edit for Testphase - Process Automation Open - Process Create - Process Recording RPA Automations Manager The RPA Automations Manager permission enables an RPA developer, citizen technologist, or knowledge source (such as a business analyst or process owner) to do the following: - In RPA Manager: - Create automation projects. - Record or design models of business processes that a process manager or center of excellence approved for automation. - Document and manage the applications required for performing the processes. - Create and manage global variables to link to activity parameters created with RPA Builder. - Change the owners and managers of processes. - Reassign unprocessed user tasks - In RPA Builder: - Build the automation based on the model. - Reuse and manage activities from the Activity Library. The RPA Automations Manager permission contains the following deprecated RPA permissions: - Activity Library Administration - Activity Library Open - Application Create - Application Delete - Application Edit - Builder Usage - Change Process Owner - Change Project Manager - Global Variables Create for Productionphase - Global Variables Create for Testphase - Global Variables Edit for Productionphase - Global Variables Edit for Testphase - Global Variables Delete - Process Automation Open - Process Create - Process Recording - Unprocessed Task List Edit - Unprocessed Task List Open RPA Bots Manager The RPA Bots Manager permission enables the user to do the following in RPA Manager: - Monitor and manage all RPA Bots, including the following: - Manage service times. - View session queues. - Manage the applications required for performing the processes, including downtimes. The RPA Bots Manager permission contains the following deprecated RPA permissions: - Application Create - Application Delete - Application Edit - Process Monitoring Open - Robot Management Administration - Robot Management Open - Robot State and Operation Open - Service Time Create - Service Time Delete - Service Time Edit RPA Evaluations Viewer The RPA Evaluations Viewer permission enables a user to do the following in RPA Manager: - View all process evaluations, regardless of whether the user belongs to the process team. - View: - Evaluation criteria - Evaluation templates The RPA Evaluations Viewer permission contains the following deprecated RPA permissions: - Evaluation Criteria Open - Evaluation Templates Open - Global Process Evaluation View - Process Evaluation Open RPA Evaluations Contributor The RPA Evaluations Contributor permission enables a user to do the following in RPA Manager: - View all process evaluations, regardless of whether the user belongs to the process team. - View, create, and edit: - Evaluation criteria - Evaluation templates - View, create, edit, and delete process evaluations. The RPA Evaluations Contributor contains the following deprecated RPA permissions: - Evaluation Criteria Create - Evaluation Criteria Edit - Evaluation Criteria Open - Evaluation Templates Create - Evaluation Templates Edit - Evaluation Templates Open - Global Process Evaluation View - Process Evaluation Administration - Process Evaluation Open RPA Evaluations Manager The RPA Evaluations Manager permission enables a user to do the following in RPA Manager: - View all process evaluations, regardless of whether the user belongs to the process team. - View, create, edit, and delete: - Evaluation criteria - Evaluation templates - Process evaluations - Approve evaluated processes to a center of excellence or a project manager for automation. The RPA Evaluations Manager contains the following deprecated RPA permissions: - Evaluation Criteria Create - Evaluation Criteria Delete - Evaluation Criteria Edit - Evaluation Criteria Open - Evaluation Templates Create - Evaluation Templates Delete - Evaluation Templates Edit - Evaluation Templates Open - Global Process Evaluation View - Process Evaluation Administration - Process Evaluation Approval to a CoE - Process Evaluation Approval to a Project manager - Process Evaluation Open RPA Operations Viewer The RPA Operations Viewer permission enables a user to do the following in RPA Manager: - View all aspects of the following RPA assets: - Alerts - Bots - Dashboards - View the following information for processes for which the user belongs to the process team: - Deployment maps - Execution plans - Session queues - Watch the bot at work via process streaming. The RPA Operations Viewer contains the following deprecated RPA permissions: - Alerting Open - Dashboard Open - Process Deployment Map Open - Process Execution Plans Open - Process Monitoring Open - Process Streaming Open - Robot Management Open - Robot State and Operation Open RPA Operations Manager The RPA Operations Manager enables a user to do the following in RPA Manager: - View and manage the following RPA assets: - Alerts - Bots - Dashboards - Unprocessed user tasks - Upcoming process changes - Analyze finance aspects and billing reports - View the following information for processes for which the user belongs to the process team: - Deployment maps - Execution plans - Session queues - Watch the bot at work via process streaming. The RPA Operations Viewer contains the following deprecated RPA permissions: - Alerting Administration - Alerting Open - Dashboard Open - Process Deployment Map Open - Process Execution Plans Open - Process Monitoring Open - Process Streaming Open - Robot Management Open - Robot State and Operation Open - Billing Report Open - Dashboard Administration - Finance Analysis Edit - Finance Analysis Open - Global Finance Analysis View - Global Process Execution Plans View - Unprocessed Task List Edit - Unprocessed Task List Open - Upcoming Process Changes Administration - Upcoming Process Changes Open RPA Performance Analyzer The RPA Performance Analyzer permission enables the user to do the following in RPA Manager: - Analyze the financial aspects (such as the break-even point) of all processes. - View the billing reports. The RPA Performance Analyzer permission contains the following deprecated RPA permissions: - Billing Report Open - Finance Analysis Edit - Finance Analysis Open - Global Finance Analysis View RPA Project Manager The Project Manager permission enables a user to be assigned as a project manager of automation projects in RPA Manager. For a user to function as a project manager, the user must also have one of the following permissions: - RPA Automations Designer - RPA Automations Contributor - RPA Automations Manager - RPA Administrator The RPA Project Manager permission contains the following deprecated RPA permissions: - Project Management --- product: RPA --- # Anypoint Platform Integration Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt On July 26th, 2023 MuleSoft RPA integrated with Anypoint Platform to unify the login experience and support external identity providers (IdP). All new customers that bought the MuleSoft Automation bundle after this date are ready to take advantage of all the new features and improvements from the integration. The migration process does not affect new customers. If you are an existing MuleSoft RPA customer and your organization is ready to start the migration: 1. Ensure you follow the [pre-migration steps](#pre-migration). 2. Ask your organization’s administrator to email [rpa\_migration\_support@salesforce.com](mailto:rpa_migration_support@salesforce.com) requesting to start the migration process. For additional questions, contact us at [rpa\_migration\_support@salesforce.com](mailto:rpa_migration_support@salesforce.com). ## Summary of Changes After your organization is integrated into Anypoint Platform: - Users log in to RPA Manager, RPA Builder, and RPA Recorder using their Anypoint Platform account. - Administrators configure RPA users, teams, and permissions using Access Management instead of the **User Management** module in RPA Manager. - RPA Manager deprecates roles and user groups and starts using teams from Anypoint Platform instead. - RPA Manager supports using Connected Apps to connect with Anypoint Platform, which provides a more secure and improved authentication mechanism than API keys. - RPA Manager supports deleting users who have assigned processes and reassigning those processes to other users or teams. See [Reassigning RPA Assets](https://docs.mulesoft.com/rpa-manager/settings-adminsettings-reassignassets) for instructions. - For non-federated orgs, MuleSoft automatically creates teams in Anypoint Platform to match the existing roles and user groups in RPA Manager: Team names are restricted to alphanumeric characters, hyphens, underscores, and spaces. If your role or user group contains unsupported characters, these characters are omitted when creating the new team name. - Roles migrate to teams using the following naming convention: `RPA Role - `. These new teams have the same Anypoint permissions for RPA privileges that the role had in RPA Manager. - User Groups migrate to teams using the following naming convention: `RPA User Group - `. - Users assigned to roles and user groups in RPA Manager migrate to the corresponding team in Anypoint Platform. ## Pre-migration Steps To prepare your organization for the migration, ensure that all your RPA Manager users have an account in Anypoint Platform or the external identity provider (IdP) your organization uses to log in. - Federated orgs If your Anypoint organization is using an external IdP, the administrator must ensure the RPA users have a matching account and the proper access. See [Configuring Identity Management in Anypoint Platform](https://docs.mulesoft.com/access-management/external-identity) for instructions and prerequisites to configure identity management for your Anypoint Platform organization. - Non-federated orgs If your Anypoint organization does not use an external IdP, MuleSoft matches RPA accounts and Anypoint accounts based on the email address. - If the RPA user already has an Anypoint account with the same email, the account linking is automatic. After the migration, the user accesses RPA resources using the Anypoint account, retaining the same level of permissions. - If the RPA user has multiple Anypoint accounts with the same email address, Anypoint Platform prompts the user to select the account to link when logging in. - If the RPA user does not already have an Anypoint user with the same email, MuleSoft sends an invite automatically before the migration so the user can join Anypoint Platform. The user must configure 2FA for their new Anypoint Platform account. ## See Also - [Anypoint Access Management RPA Permissions](https://docs.mulesoft.com/rpa-home/automation-userrolesandpermissions-anypointrpapermissions) --- product: RPA --- # Create an RPA Project > For the full documentation index, see: https://docs.mulesoft.com/llms.txt An RPA project consists of a business process to be automated and a team that is responsible for the automation. You can create projects in the following **RPA Manager** views: - **RPA Home** - **My RPA** > **My Backlog** - **My RPA** > **My Processes** - **Process Evaluation** > **Process Evaluation** - **Process Automation** > **Process Management** - **Process Automation** > **Process Management** > **** ## 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

## Create a Project From RPA Home Create a project from the RPA Manager home page: 1. Open the **Home** module of RPA Manager. 2. Click the quick link **New Process or Evaluation**. 3. Click **Process**. 4. Complete the [**New Process** form](#process-project-data). 5. Click **Start Automation**. ## Create a Project by Starting Automation from an Approved Evaluation The standard way of automating a process begins with evaluating the feasibility and benefits of the process automation in the **Process Evaluation** module. RPA Manager shows approved processes in the backlog views of the **My RPA** module. Learn how to start the automation of approved processes from there in topic [Starting Automation of Approved Processes](https://docs.mulesoft.com/rpa-manager/myrpa-start). ## Create a Project From Other Views To create a new project from any of the views listed at the beginning of this article: 1. Open the view. 2. Click **New Process**. 3. Complete the [**New Process** form](#process-project-data). 4. Click **Start Automation**. ## Process Project Data - **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. ## See Also [Preparing Projects](https://docs.mulesoft.com/rpa-manager/processautomation-prepare-project) --- product: RPA --- # Finding Information in a PDF > For the full documentation index, see: https://docs.mulesoft.com/llms.txt First, you need to find the order ID in the PDF. As you can see in [the image of the order confirmation letter](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction#confirmationletter-image), the order ID is always listed in a table next to the entry 'Order ID'. You can use this information to implement the workflow that contains the following steps: 1. Copy the content of the order confirmation to a text file. 2. Read the text file line by line to find the one containing the order ID. 3. Check if the order ID is found. 4. Cut out the order ID from the text and store it in an activity parameter. ![The Workflow contains the steps in the form of action steps. Some of the action steps are nested.](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-extractformpdf-workflow-overview.png) ## 1\. Copying Text From a PDF to a Text File To open the PDF, you use the **Read PDF file** action step. Then, you use the returned `ReadText` as input for the **Write to Text File** to save the content as a text file on your computer. ![An out-filled pin symbol next to the input field shows that the variable is mapped to the text extracted from the PDF in a previous action step.](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-extractformpdf-workflow-pdftotxt.png) The following image shows the result of storing the text content. Each line of the PDF has a corresponding line in the text file. Images are omitted. ![](/mulesoft/current/en-us/rpa-home/_images/extractorderid-workflow-resultpdftotxt.png) ## 2\. Looping Over All Lines of a Text File To loop over all lines of the text file, you first need to count the number of lines by reading the entire file using the action step **Read from Text File**. You use the returned `line count` as the maximum value for the iteration counter. The counter also functions as the number of the line to read with **Read from Text File** in each iteration. ![](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-extractformpdf-workflow-loopovertextfilelines.png) ## 3\. Checking a Case and Catching Errors Because you don’t know which line contains the order ID, you use **Select Case** to differentiate between the two possibilities. If you find the order ID, you copy it from the text and store it in the activity parameter `order_id`. If you didn’t, which happens in each other line, you still want to complete the loop and the workflow and use **Force OK State** to avoid returning an error. The criteria for deciding whether you found the order ID is that the string `Order ID` is part of the current line. ![To add a case, you must first pin the compare value to the action step.](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-extractformpdf-workflow-checkcaseandproceed.png) ## 4\. Retrieving a Substring and Saving It to a Variable Because you know that the order ID is written after the text `Order ID`, you can remove these first nine characters from the current line (which contains the substring `Order ID`) by using the **Trim left (remove first characters)** operations of the **String Operations** action step. The rest of the string is the order ID. You store it in the Activity Parameter with the same name by using the result of the string operation as a Pin Variable in the **Set Variable** action step. ![](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-extractformpdf-workflow-cutsubtringoutoftext.png) ## See Also - [RPA Builder Action Step: Read PDF File](https://docs.mulesoft.com/rpa-builder/latest/toolbox-file-operations-read-pdf-file) - [RPA Builder Action Step: Write to Text File](https://docs.mulesoft.com/rpa-builder/latest/toolbox-file-operations-write-to-text-file) - [RPA Builder Action Step: Read from Text File](https://docs.mulesoft.com/rpa-builder/latest/toolbox-file-operations-read-from-text-file) - [RPA Builder Action Step: Select Case](https://docs.mulesoft.com/rpa-builder/latest/toolbox-flow-control-select-case) - [RPA Builder Action Step: Force OK State](https://docs.mulesoft.com/rpa-builder/latest/toolbox-flow-control-force-ok-state) - [RPA Builder Action Step: String Operations](https://docs.mulesoft.com/rpa-builder/latest/toolbox-variable-handling-string-operations) - [RPA Builder Action Step: Set Variable](https://docs.mulesoft.com/rpa-builder/latest/toolbox-variable-handling-set-variable) [Usecase: Extract Data from a Legacy System](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction) [Interacting with a Screen of a Legacy Application](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction-extractfromscreen) --- product: RPA --- # Glossary > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The following glossary helps you understand MuleSoft RPA terminology. ## A Action Step The smallest components in a Workflow. Use action steps to build logical blocks and transactions in RPA Builder. Activity A single unit of work in the automation project. An activity can be a bot task and its linked workflow, or a user task. Activity Library A collection of assets that enables you to reuse certain activities that repeat during the automation of business processes, such as a login, to avoid creating the same workflow multiple times. Activity Parameter Map variables that you can use both in the Workflow and in the activities of the business process and gateways. Analysis Package A ZIP file containing workflow run logs and error screenshots. Importing the package in RPA Builder shows information in the same format as when the workflow executes locally. ## B Bot Tasks Contains the activities for the RPA bot to execute. BPMN (Business Process Model and Notation) 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. BPMN Editor An editor that is available both inside RPA Manager and RPA Builder to modify existing BPMs. ## C Center of Excellence (CoE) A group of users that cover the entire range of competencies required for a specific part of the automation. Only user groups explicitly designated as Centers of Excellence can accept process automation tasks. Composer Task An action executed on a MuleSoft Composer Connector, including but not limited to read, create, update, and delete. ## I IDP (Intelligent Document Processing) A technology solution that implements AI to read documents, extract data, and organize information from different document sources. Invocable Run Configuration A run configuration that RPA Manager uploads to Anypoint Exchange as an invocable API to be called by other services, such as Composer. ## M MuleSoft Automation Automates workflows that contain time-consuming manual tasks and integrate them with your MuleSoft Composer flows. ## O Optical Character Recognition (OCR) A technology that convert images of texts into machine-encoded text. Organization The container for everything in your RPA Platform account. ## P Properties A group of values that define the settings of a specific element. Process Candidate A real-life business process about to be proposed for automation via process evaluation. Project Manager A project manager is responsible for the automation of a process across all automation phases. ## R Regular Expression A sequence of characters and symbols that specify a match pattern to be searched in text. Run Configuration A set of execution parameters and run conditions for an automated process that includes a name, run schedule, activity parameters' starting values, and assigned user tasks and bots. RPA (Robotic Process Automation) Automates business processes and tasks by using bots, which helps save time and prevent introducing human errors. RPA Bot A software robot that runs in an on-premises environment and executes the assigned automation. You can manage bots from RPA Manager. RPA API Call An API invocation made by a customer to perform an operation, including, but not limited to lookup, validate, create, update, or delete data in a system as part of an RPA process. See the [Automation Credits Usage and Rates](https://docs.mulesoft.com/general/automation-credits-usage-and-rates) for additional details. RPA Bot Minute The number of minutes running process automations across all bot sessions. A single bot may run multiple parallel sessions, with RPA Bot Minutes counting for each parallel session. Multiple bots may be configured to run the same process, with RPA Bot Minutes counting for each of these separate bot sessions. Test runs or process runs in the test phase are also counted towards RPA Bot Minutes. See the [Automation Credits Usage and Rates](https://docs.mulesoft.com/general/automation-credits-usage-and-rates) for additional details. RPA Builder An on-premises application that enables you to build automations by specifying the steps of the process. RPA Manager The cloud-based control plane for the automations that is integrated into Anypoint Platform. RPA Recorder An on-premises tool that assists during the process design phase by recording all user actions, creating click path documentation, and generating additional data to automatically create action steps in the build phase. ## S Secure Session 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. ## T Text Modules A set of encoded values that can map to a certain special character, a macro, a script variable, or an environment variable. Toolbox The container for the action steps that you implement in RPA Builder to automate a process. ## U User Task An element of a process model, which cannot be processed fully automatically by a Robot, instead requiring the support of a human. ## V Variable A value of a defined type that you can store and change during a process. ## W Workflow A set of action steps that is linked to an activity. Workbench The area of RPA Builder where you can visualize and modify a workflow. --- product: RPA --- # Hardware and Software Requirements > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Before using MuleSoft RPA, ensure that your environment meets the minimum hardware and software requirements to use the cloud-based control plane and the on-premise RPA applications. ## RPA Manager - Use any of the supported web browsers to access the platform: - Microsoft Edge - Google Chrome - Apple Safari - Mozilla Firefox - Ensure you have access to your organization’s RPA Manager instance The URL to access RPA Manager is `https://.rpa.mulesoft.com`, where `` represents your organization’s instance. If you are not sure about the name of your instance, contact your organization’s administrator. ## RPA Builder 6.7 ### Hardware Requirements
MinimumRecommended

Dual-core 2 GHz CPU (MMX/SSE compatible)

Dual-core 2 GHz CPU (MMX/SSE compatible)

4 GB of RAM

8 GB of RAM

30 GB of disk space

30 GB (SSD) of disk space

Graphics Accelerator Card

### Software Requirements
SoftwareRequired version

Microsoft .NET Framework

4.8

Operating System

Any of the following:

  • Windows 10 (64 bit)

    • Professional

    • Professional for Workstations

    • Enterprise

      No support for Enterprise multi-session (Windows 10 Enterprise for Virtual Desktops).

    • Enterprise LTSC

  • Windows 11

    • Professional

    • Professional for Workstations

    • Enterprise

      No support for Enterprise multi-session (Windows 11 Enterprise for Virtual Desktops).

  • Windows Server 2019

  • Windows Server 2022

Java

Any of the following:

  • Java Runtime Environment 11 (JRE, 64-bit version)

  • Adoptium 11 (JRE, 64-bit version)

#### File System Permission Requirements RPA Builder needs full write access to folders that are critical to its functioning. To avoid issues during the setup process and subsequent RPA Builder executions, ensure that: - You install RPA Builder as an administrator If you don’t run the setup file as an administrator, the installation process might not finish successfully. If this happens, make sure you reinstall RPA Builder by running the setup file as an administrator. - RPA Builder has full write access to these folders and any subfolders and files inside them: - `C:\Users\\Documents\Mulesoft` - `C:\Users\Public\Documents\Mulesoft` - `C:\Users\\AppData\Local\MuleSoft_LLC` - `C:\Users\\AppData\Roaming\MuleSoft` - `C:\ProgramData\Mulesoft\RPABuilder\Cache` - Your environment isn’t blocking the execution of any RPA process The operating system can block the execution of certain files. Make sure that all executable (`.exe`) files inside the RPA Builder home directory and its subfolders are allowed to run. #### Check for Software Interference Some software can prevent RPA Builder from working properly. Resolve any software issues you find before installing RPA Builder.
SoftwareProblemSolution

Microsoft OneDrive

Microsoft OneDrive is an application for backing up data from a computer.

When you turn on Microsoft OneDrive backup for the Documents folder on your computer, it moves this folder to a different location. When RPA Builder starts, it tries to clean up the cache folder, but OneDrive redirects this to the new location where RPA Builder doesn’t have permission to write:

  • From: C:\Users\<username>\Documents\Mulesoft\Cache

  • To: C:\Users\<username>\OneDrive\Documents\Mulesoft\Cache

This causes an error that you can find in the log files:

System.IO.IOException: Access to the path 'C:\Users\<username>\OneDrive\Documents\Mulesoft\Cache' is denied.

A user describes this problem in detail in a Microsoft Community thread.

If you use RPA Builder on a computer that has OneDrive, don’t let OneDrive back up your Documents folder.

The Microsoft OneDrive documentation explains how to exempt the Documents folder from the OneDrive backup.

### Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

For Hardware and Software requirements for earlier RPA Builder versions, refer to the corresponding product documentation: - [RPA Builder 6.6 Hardware and Software Requirements](https://docs.mulesoft.com/rpa-builder/6.6/hardware-software-requirements) ## RPA Recorder 6.6 ### Hardware Requirements
MinimumRecommended

Dual-core 2 GHz CPU (MMX/SSE compatible)

Dual-core 3 GHz CPU (MMX/SSE compatible)

8 GB of RAM

16 GB of RAM

5 GB of disk space

10 GB (SSD) of disk space

### Software Requirements
SoftwareRequired version

Microsoft .NET Framework

4.8

Operating System

Any of the following:

  • Windows 10 (64 bit)

    • Professional

    • Professional for Workstations

    • Enterprise

      No support for Enterprise multi-session (Windows 10 Enterprise for Virtual Desktops).

    • Enterprise LTSC

  • Windows 11

    • Professional

    • Professional for Workstations

    • Enterprise

      No support for Enterprise multi-session (Windows 11 Enterprise for Virtual Desktops).

  • Windows Server 2019

  • Windows Server 2022

#### Recommended System Settings - Display resolution: Full HD 1080p (1920 × 1080) or higher #### File System Permission Requirements RPA Recorder needs full write access to folders that are critical to its functioning. To avoid issues during the setup process and subsequent RPA Recorder executions, ensure that: - You install RPA Recorder as an administrator If you don’t run the setup file as an administrator, the installation process might not finish successfully. If this happens, ensure you reinstall RPA Recorder by running the setup file as an administrator. - RPA Recorder has full write access to the following folders and any subfolders and files inside them: - `C:\Program Files\MuleSoft\RPARecorder` - `C:\RPARecorder` - Your environment is not blocking the execution of any RPA process The operating system can block the execution of certain files. Ensure that all executable (`.exe`) files inside the RPA Recorder home directory and its subfolders are allowed to run. ### Compatibility
ApplicationVersion

RPA Builder

6.6.0 and later

RPA Bot

1.4.0 and later

For Hardware and Software requirements for earlier RPA Recorder versions, refer to the corresponding product documentation: - [RPA Recorder 6.5 Hardware and Software Requirements](https://docs.mulesoft.com/rpa-recorder/6.5/hardware-software-requirements) ## RPA Bot 1.7 ### Hardware Requirements - For optimal performance, use a dedicated computer for running the RPA Bot. - The following table shows the minimum and the recommended hardware requirements for running one process:
MinimumRecommended

Dual-core 2 GHz CPU (MMX/SSE compatible)

Dual-core 3 GHz CPU (MMX/SSE compatible)

8 GB of RAM

16 GB of RAM

30 GB of disk space

30 GB (SSD) of disk space

To run more than one process in parallel, when using Secure Sessions, you must add 2 GB of RAM plus the RAM needed to run the process for each parallel run to these recommended values. For example, to run two different processes in parallel: - Process 1 requires one GB of RAM and runs 10 times in parallel. - Process 2 requires three GB of RAM and runs five times in parallel. In this case, use the following formula to calculate that you need a computer with a minimum of 63 GB of RAM: #### Unsupported Hardware Configurations - Notebooks with Intel Graphics 520 and 530 ### Software Requirements
SoftwareRequired version

Microsoft .NET Framework

  • 4.5

  • 4.7.2

Operating System

Any of the following:

  • Windows 10 (64 bit)

    • Professional

    • Professional for Workstations

    • Enterprise

      No support for Enterprise multi-session (Windows 10 Enterprise for Virtual Desktops).

    • Enterprise LTSC

  • Windows 11

    • Professional

    • Professional for Workstations

    • Enterprise

      No support for Enterprise multi-session (Windows 11 Enterprise for Virtual Desktops).

  • Windows Server 2019

  • Windows Server 2022

#### System Settings - Display resolution: - Minimum: 1280 x 1080 - Recommended: Full HD 1080p (1920 × 1080) or higher - `Custom scaling` of text and other items on the screen: 100% - `ClearType`: turned off #### Requirements for the Secure Session Technology Secure Sessions are hidden Desktop sessions that run in the background and are accessible only to the bot. An additional advantage of using Secure Sessions is that the bot can multiply itself to run several process instances in parallel. To use Secure Sessions you must ensure that all prerequisites are met and all responsible persons are informed. - You can’t use Secure Sessions with any operating system running on the Microsoft Azure Virtual Desktop Infrastructure (VDI). - The RPA Bot service runs under the `Local System` account per default. - To use another account, ensure that it has permission to run Windows services. - The RPA Bot service runs processes under user accounts on the same computer or within the same domain. - Use dedicated accounts and a user-naming scheme to differentiate between local users and domain users and between human users and bot users. - User accounts used by the bot to run processes must belong to the `Remote Desktop Users` group and must have permission to establish a local RDP session via the local loopback address 127.0.0.2. - To enable a bot to run more than one (Windows 10, Windows 11) or two (Windows Server) Secure Sessions simultaneously, ensure that a terminal server software with enough licensed users is installed on the computer where the bot is installed. The computer must have enough resources to execute several processes simultaneously: 2 GB or more RAM per session. Although other terminal server software can work, RPA has been validated with the following terminal server software: - [Microsoft Remote Desktop Services](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/overview) - [TSplus MuleSoft RPA Connector](https://www.tsplus-rpa.com/) - 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. - Do not sign in to a computer where a bot with one licensed Secure Session is running a process. #### File System Permission Requirements RPA Bot needs full write access to some folders that are critical to its functioning. To avoid issues during the setup process and later RPA Bot executions, ensure that: - You install RPA Bot as an administrator If you don’t run the setup file as an administrator, the installation process might not finish successfully. If this happens, ensure you reinstall RPA Bot by running the setup file as an administrator. - RPA Bot has full write access to the following folders and any subfolders and files inside them: - `C:\Program Files\Mulesoft\RPABot` - `C:\ProgramData\Mulesoft\RPABot` - Your environment is not blocking the execution of any RPA process The operating system can block the execution of certain files. Ensure that all executable (`.exe`) files inside the RPA Bot home directory and its subfolders are allowed to run. #### Internet Requirements RPA Bot requires a stable internet connection to poll tasks from RPA Manager. During downtime of the service or of the region where RPA Manager runs, the bot can’t receive new tasks until connectivity is reestablished. To communicate with RPA Manager, RPA Bot requires you to enter the following Internet route in the **RPA Manager to connect** field on the RPA Bot Configurator pop-up: - `https://[your subdomain].rpa.mulesoft.com` In addition, it is also necessary to open the internally used URL `https://*.cloudfront.net`, which is done typically by your network or security team. See [Configuring RPA Bot](https://docs.mulesoft.com/rpa-bot/latest/configuration#common-settings) for more information about the RPA Bot Configurator pop-up. ### Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

For Hardware and Software requirements for earlier RPA Bot versions, refer to the corresponding product documentation: - [RPA Bot 1.6 Hardware and Software Requirements](https://docs.mulesoft.com/rpa-bot/1.6/hardware-software-requirements) ## See Also - [Tutorial: Create an Automation from Start to Finish](https://docs.mulesoft.com/rpa-home/automation-tutorial-introduction) --- product: RPA --- # Interacting with a Screen of a Legacy Application > For the full documentation index, see: https://docs.mulesoft.com/llms.txt With the order ID, you can now get the corresponding tracking number from the legacy system: 1. Run your legacy application. 2. Search for the word `Order-ID` on the screen, click in the edit field next to it, enter the order ID, and click **Search**. 3. If the search returns a result, copy the found tracking number to the activity parameter and set the gateway variable `is_orderid_found` to true. If there is no result, set the gateway variable `is_orderid_found` to false. ![The Workflow contains the steps in the form of action steps. Some of the action steps are nested.](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction.png) ## 1\. Run a Legacy Desktop Application To run the legacy desktop order-tracking application, select the path to the executable file in the **Run program** action step. You set the start mode of the application to `Maximized` to open the application in a maximized window. This process ensures that the UI elements are always in the same position on the screen, which is important because you later use action steps that work with screen coordinates. You select `Wait for Window to appear` and specify the window title to ensure that the following action steps won’t return an error because the window isn’t there yet. ![](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction-run.png) ## 2\. Enter Text into a Screen Element and Click a Button To search for the tracking number, you have to enter the order ID in the search field and click the search button. To find the search field, you need to find the word `Order ID` next to it on the application screen first. You use the **Search Pattern** action step to capture and compare the pattern: ![When you capture a pattern, the screen freezes. You draw a box around the pattern and the search area on the frozen screen.](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction-capturepattern.png) ![](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction-searchpattern.png) Finding the pattern returns a coordinate that you use in the next step to determine where to input the order ID. You use the **Mouse Action** action step to click the search field next to the `Order ID` label. ![The coordinates from the found pattern are used in the Relative To field of the Mouse Action action step.](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction-mouseaction.png) The search field now has the focus, so you can enter the order ID with a simulated keyboard. Instead of recording keystrokes, you use the Activity Parameter `order_id` with the **Enter String** action step to copy the order ID into the field: ![](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction-enterstring.png) You use **Mouse Action** again to start the search. To determine the position of the search button to click, you reuse the location of the `Order id` pattern to record the click position. ![](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction-mouseaction-clickbutton.png) ## 3\. Check the Results The search is successful when a result is listed. As you can see on [the screen](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction#trackingsystem-allentries-image), the tracking number is listed in the column of the same name, so you search for that column first, using `Tracking No.` as the search pattern: ![](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction-searchpattern-text.png) Because the order might not have a corresponding tracking number in the system and you don’t want to falsely return the initial value of the variable as tracking number, you check this case first using the **Managed** action step. In **DoAction**, which works like a try element, you check if the result list is empty. As you can see on [the screen](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction#trackingsystem-noentries-image), in case of no results, an up arrow shows directly below the empty space where the results should have been. You use the **Search Pattern** action step to search for this arrow up symbol and limit the search area to the space directly below the column name. If the bot doesn’t find the pattern, which means that the system found a corresponding tracking number, **Search Pattern** returns an error. To continue the workflow, you must force an OK state in the **OnError** section. ![](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction-searchpattern-relatedcoordinates.png) If the legacy application returns the tracking number, the number of found patterns matching the arrow up symbol is zero. You use this information as a case differentiator in the **Select Case** action step. ![The Select Case action step uses Found Matched Pattern Count as Pin Variable Found Matched Pattern Count. The case compares the value to zero.](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction-selectcase.png) If the search returns a result, you set the gateway variable `is_orderid_found` to `true`. ![](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction-selectcase-orderfoundtrue.png) Then, you use AI-enhanced optical character recognition to extract the tracking number with the **AI OCR (screen-based)** action step using the `Recognition Only` search mode. ![](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction-aiocr.png) As before, you use the pattern `Tracking No.` as the anchor for the search area. ![](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction-trackingno-searcharea.png) You save the extracted tracking number to the Activity Parameter so you can return it at the end of the process. ![The text returned by the OCR action step is stored in the Pin Variable named Recognized Text.](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-screeninteraction-getregocnizedtext.png) If the tracking number is not returned by the search, you set the gateway variable `is_orderid_found` to `false` and force an OK state to continue the process. ## See Also - [RPA Builder Action Step: Run Program](https://docs.mulesoft.com/rpa-builder/latest/toolbox-control-run-program) - [RPA Builder Action Step: Search Pattern](https://docs.mulesoft.com/rpa-builder/latest/toolbox-checks-search-pattern) - [RPA Builder Action Step: Mouse Actions](https://docs.mulesoft.com/rpa-builder/latest/toolbox-control-mouse-actions) - [RPA Builder Action Step: Enter String](https://docs.mulesoft.com/rpa-builder/latest/toolbox-control-enter-string) - [RPA Builder Action Step: Managed](https://docs.mulesoft.com/rpa-builder/latest/toolbox-flow-control-managed) - [RPA Builder Action Step: Select Case](https://docs.mulesoft.com/rpa-builder/latest/toolbox-flow-control-select-case) - [RPA Builder Action Step: AI OCR (Screen-Based)](https://docs.mulesoft.com/rpa-builder/latest/toolbox-text-recognition-ai-ocr-screen-based) - [RPA Builder Action Step: Set Variable](https://docs.mulesoft.com/rpa-builder/latest/toolbox-variable-handling-set-variable) [Finding Information in a PDF](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction-extractfrompdf) [Reacting to Different Outcomes](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction-reacttodifferentoutcomes) --- product: RPA --- # Invoke RPA Services from Composer > For the full documentation index, see: https://docs.mulesoft.com/llms.txt MuleSoft RPA Connector for MuleSoft Composer enables you to invoke RPA processes and configure polling triggers from your Composer flows. You can use the RPA connector to invoke an RPA process, pass data to an RPA process and retrieve results from the RPA process. The RPA connector for MuleSoft Composer enables you to: - **Invoke RPA Process** This feature enables you to make sync and async calls to RPA processes. - Sync calls wait for the RPA process to finish before continuing with the Composer flow execution. - Async calls invoke an RPA process and continue the Composer flow execution while the RPA process executes in parallel. - **RPA Poll Trigger** This feature enables you to create listeners that check the status of an specific RPA process. When the RPA process finishes the execution, the polling trigger starts processing the configured activities in the Composer flow. This functionality is useful for retrieving results from RPA processes that take a long time to finish and are not suitable for synchronous consumption. Refer to the [MuleSoft RPA Connector for Composer](https://docs.mulesoft.com/composer/ms_composer_rpa_reference) documentation for configuration and usage details. ## Before You Begin - Before you can invoke an RPA process, you must publish it to Exchange. See [Create an invocable run configuration](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#create-an-invocable-run-configuration) for instructions to create and publish an invocable RPA process. - Using the RPA connector features in Composer requires you to connect with your MuleSoft RPA account by configuring the corresponding API key and RPA API URL: - See [Create an API Key for a User](https://docs.mulesoft.com/rpa-manager/usermanagement-connect#create-an-api-key-for-a-user) for instructions to create API Keys. - The RPA API URL is the RPA Manager URL with `/rpa/api/v1` appended to it. For example, if your RPA Manager URL is `https://myOrg.rpa.mulesoft.com`, then the value to set in the RPA API URL field is `https://myOrg.rpa.mulesoft.com/rpa/api/v1`. ## See Also - [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) --- product: RPA --- # List of Privileges by Module > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Manager has the following privileges, which can be assigned to individual users. To open any module, you always require the privilege for which the name ends in **Open**. Privileges that end with **Administration** allow a user to create, change, and delete all types of objects in the corresponding module. If the authorization only applies to a single type of object in a module, the corresponding privileges end with **Create**, **Edit**, and **Delete**. Privileges named **Global <…​> View** allow a user to see all the processes in the relevant view. A user who does not have this privilege can only see processes for which they belong to the project team. If you assign a role to a user, the user receives all the privileges contained in the role. These privileges are not displayed in the **Privileges** field in the user’s profile. ## Privileges for the Organization Management Module
PrivilegePermitted Action

Organization Management Open

Open all views of the Organization Management module

Organization Management Administration

Create, change, and delete objects in the Organization Management module.

## Privileges for the User Management Module
PrivilegePermitted Action

User Management Open

Open all views of the User Management module.

User Management Administration

Create, change, and delete objects in the User Management module.

User Api Key Create

Create user API keys. This privilege must be combined with the privilege User Management Administration to create a user key for another user. A user with only the privilege User API Key Create can create an API key for himself.

User Api Key Edit

Change user API keys. This privilege must be combined with the privilege User Management Administration.

User Api Key Delete

Delete user API keys. This privilege must be combined with the privilege User Management Administration.

User Group Create

Create user groups

User Group Edit

Change user groups

User Group Delete

Delete user groups

## Privileges for the Bot Management Module
PrivilegePermitted Action

Robot Management Open

Open all views of the Bot Management module.

Robot Management Administration

Create, change, and delete objects of the Bot Management module.

Service Time Create

Create bot service times.

Service Time Edit

Change bot service times.

Service Time Delete

Delete bot service times.

## Privileges for the Process Evaluation Module
PrivilegePermitted Action

Process Evaluation Open

Open the Process Evaluation view.

Process Evaluation Administration

Create, change, and delete objects of the Process Evaluation module.

Global Process Evaluation View

Authorization to view all processes in the Process Evaluation view, regardless of whether the current user belongs to the process team.

Evaluation Criteria Open

Open the Evaluation Criteria view.

Create Evaluation Criteria

Create evaluation criteria.

Edit Evaluation Criteria

Change evaluation criteria.

Delete Evaluation Criteria

Delete evaluation criteria.

Process Evaluation Approval to a CoE

Assign a process automation to a center of excellence. A center of excellence is a user group that is assigned Center of Excellence in the User Management module.

Process Evaluation Approval to a Project Manager

Assign a process automation to a project manager. A project manager is a user with the Project Management privilege.

Open Evaluation Templates

Open the Evaluation Templates view.

Create Evaluation Templates

Create and copy evaluation templates.

Edit Evaluation Templates

Change evaluation templates.

Delete Evaluation Templates

Delete evaluation templates.

## Privileges for the Process Automation Module
PrivilegePermitted Action

Process Automation Open

Open all views of the Process Automation module.

Process Create

Create and copy a process project. To copy a project, you also need the privilege Builder Usage.

Project Management

Function as a project manager of a process project.

Change Process Owner

Change the process owner of a process project.

Change Project Manager

Change the project manager of a process project.

Application Create

Create an application in the Process Applications view.

Application Edit

Change an application in the Process Applications view.

Application Delete

Delete an application in the Process Applications view.

Global Variables Create for Production phase

Create global variables in the Global Variables view for use project configurations in the production phase.

Global Variables Create for Test phase

Create global variables in the Global Variables view for use project configurations in the test phase.

Global Variables Delete

Delete global variables in the Global Variables view.

Global Variables Edit for Production phase

Edit global variables in the Global Variables view for use project configurations in the production phase.

Global Variables Edit for Test phase

Edit global variables in the Global Variables view for use project configurations in the test phase.

Process Recording

Use the RPA Process Recorder.

## Privileges for the Process Operations Module
PrivilegePermitted Action

Process Execution Plans Open

Open the Process Execution Plans view.

Global Process Execution Plans View

Authorization to view all processes in the Process Execution Plans view, independently of whether the current user is a member of the process team.

Process Deployment Map Open

Open the Deployment Map view.

Upcoming Process Changes Open

Open the Upcoming Process Changes view.

Upcoming Process Changes Administration

Administer objects in the Upcoming Process Changes view.

Finance Analysis Open

Open the Finance Analysis view with processes for which the current user is a member of the process team.

Global Finance Analysis View

Open the Finance Analysis view with all processes, independently of whether the current user is a member of the process team.

Finance Analysis Edit

Change finance analyses.

Billing Report Open

Open the Usage Summary view.

## Privileges for the Process Monitoring Module
PrivilegePermitted Action

Process Monitoring Open

Open all views of the Process Monitoring module.

Robot State and Operation Open

Open the Robot State and Operation view.

Process Streaming Open

Open the Process Streaming view.

## Privileges for the My RPA Module
PrivilegePermitted Action

Global Process Evaluation View

View all processes in the views Process Evaluation and My RPA > Team Backlog, regardless of whether the user belongs to the process team.

Unprocessed Task List Open

Open the Unprocessed Tasks view.

Unprocessed Task List Edit

Change the Unprocessed Tasks view.

## Privileges for the Dashboard Module
PrivilegePermitted Action

Dashboard Open

Open all views of the Dashboard module.

Dashboard Administration

Create, change, and delete objects of the Dashboard module.

## Privileges for the Alerting Module
PrivilegePermitted Action

Alerting Open

Open all views of the Alerting module.

Alerting Administration

Create, change, and delete objects of the Alerting module.

## Privileges of the RPA Builder Category The **Activity Library** is managed only in the RPA Builder. Learn how to [use the Activity Library in RPA Builder](https://docs.mulesoft.com/rpa-builder/latest/activity-library).
PrivilegePermitted Action

Builder Usage

Use the RPA Builder.

Activity Library Administration

Manage the Activity Library in the RPA Builder.

Activity Library Open

Open the Activity Library in the RPA Builder.

--- product: RPA --- # Publishing Automation Assets to Anypoint Exchange > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You can connect RPA Manager with your Anypoint Platform account, which enables you to publish a process automation to Exchange. Connecting RPA Manager with your Anypoint Platform account requires a Connected App with the scope RPA Integrator configured in Access Management. To publish automation assets to Exchange: 1. [Configure a Connected App in Access Management](#configure-connected-app-rpa). 2. Connect RPA Manager with your Anypoint Platform Account. See [Configure Anypoint Platform Credentials](https://docs.mulesoft.com/rpa-manager/organizationmanagement-settings#configure-anypoint-credentials) for instructions. 3. Publish a Process Automation to Anypoint Exchange. See [Publish a Process Automation to Anypoint Exchange](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#publish-automation) for instructions. ## Configure a Connected App in Access Management To create a Connected App in your Anypoint Platform account: 1. Log in to [Anypoint Platform](https://anypoint.mulesoft.com/). 2. Open **Access Management**. 3. On the navigation panel, click **Connected Apps**. 4. Click **Create App**. 5. Specify a **Name** for the Connected App. 6. In **Type**, select **App acts on its own behalf(client credentials)**. ![The Connected App creation window](/mulesoft/current/en-us/rpa-home/_images/share-assets-connected-app-type.png) 7. Click **Add Scopes**. 8. In the filter box, type **RPA** and select **RPA Integrator** among the results. ![The Scopes selection window](/mulesoft/current/en-us/rpa-home/_images/share-assets-connected-app-scopes.png) 9. Click **Next**. 10. Select a **Business Group** and click **Review**. 11. Click **Add Scopes** to confirm. 12. Click **Save**. ### See the Client ID and Client Secret of a Connected App After you create a Connected App, it shows in the **Connected Apps** section of Access Management, where you can see the Connected App’s Client ID and Client Secret. ![The Connected Apps section in Access Management](/mulesoft/current/en-us/rpa-home/_images/share-assets-connected-app-credentials.png) Click either **Copy ID** or **Copy Secret** to copy the corresponding value to the clipboard for further use. ## See Also - [Create an Anypoint Platform Account](https://docs.mulesoft.com/access-management/managing-your-account#how-to-create-your-account) --- product: RPA --- # Reacting to Different Outcomes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt In the model of the process, you use an exclusive gateway to determine how to proceed with different outcomes of the tracking number extraction. In RPA Builder, you configure the gateway using the `is_ordeid_found` Activity Parameter. ![The condition expression is 'is\_orderid\_found == true'.](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-gateway.png) ## See Also - [RPA Builder: Connecting Activity Parameters to a Gateway](https://docs.mulesoft.com/rpa-builder/latest/toolbox-variable-handling-activity-parameters#connecting-activity-parameters-to-a-gateway) [Interacting with a Screen of a Legacy Application](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction-extractfromscreen) [Returning Values](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction-returnvalues) --- product: RPA --- # Returning Values > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Each value saved to an Activity Parameter is returned at the end of the process. In this example, you use a User Task to inform the user about the outcome of the search in RPA Manager after the process is deployed. ![The User Tasks contains the description 'The order with the following oder ID and tracking number was found in the Order Tracker: '. The order ID and tracking number are included as Read-Only Activity Parameters.](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-usertask.png) ## See Also - [RPA Manager: Handling User Tasks](https://docs.mulesoft.com/rpa-manager/myrpa-handle) [Reacting to Different Outcomes](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction-reacttodifferentoutcomes) --- product: RPA --- # RPA Bot 1.6.0 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## February 21, 2024 ## What’s New - The System Settings panel now has a `Bot Service State` entry, which shows the current Windows Service state and configuration. - The **Password** and **Current User** fields on the Session Settings panel are renamed **Default Session User Password** and **RPA Bot Configurator User** respectively. - A warning message has been added to indicate that if a deployed process is running on the bot instance, the process may be canceled if RPA Bot is restarted as a result of a change made to the RPA Bot Configurator. - When a change is made to the RPA Bot Configurator while a process is running, you can now select from multiple restart, exit, and cancel options to decide how you want to proceed with the process that is running and the changes to the RPA Bot Configurator. - The RPA Bot Configurator now includes a Diagnostic Infos panel to help you identify current and potential problems with RPA Bot. - Redundant third party assemblies have been removed. - Dynamic process execution throttling has been added to reduce the number of times RPA Bot attempts to restart a failing process. - You can now view the path to the analysis packages on the default run result message in RPA Manager if the setting to write an analysis packages is enabled on RPA Bot. - You can now define the folder location for analysis packages of failed and successful workflow runs, using the **Custom Analysis package folder of failed workflows** and **Custom Analysis package folder of succeeded workflows** fields on the Session Monitoring panel of the RPA Bot Configurator. The folder that is selected in either field is maintained by the user. ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

## Fixed Issues
Issue ResolutionID

The RPA Bot daily midnight job now executes once daily at 0:00 UT.

W-14807645

Updated all copyrights to 2024.

W-14820545

The RPA Bot connection test is now performed with the correct RPA Manager URL.

W-14835335

Credential recognition is now working correctly with domain users.

W-15019592

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.6.2 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## March 25, 2024 ## Fixed Issues
Issue ResolutionID

The custom message created from the Write Bot Message action step now displays the full 2,000 characters and no longer truncates the message after 1,000 characters.

W-15252227

RPA Bot now removes sessions that are in a state of "Disconnected" to prevent RPA Bot from attempting to connect to and create Secure Sessions from "Disconnected" sessions.

W-15241413

## February 21, 2024 ## What’s New - The System Settings panel now has a `Bot Service State` entry, which shows the current Windows Service state and configuration. - The **Password** and **Current User** fields on the Session Settings panel are renamed to **Default Session User Password** and **RPA Bot Configurator User** respectively. - A warning message is added to indicate that if a deployed process is running on the bot instance, the process might cancel if RPA Bot is restarted as a result of a change made to the RPA Bot Configurator. - When a change is made to the RPA Bot Configurator while a process is running, you can now select from multiple restart, exit, and cancel options to decide how to continue with the process that is running and the changes to the RPA Bot Configurator. - The RPA Bot Configurator now includes a Diagnostic Infos panel to help you identify current and potential problems with RPA Bot. - Redundant third-party assemblies are removed. - Dynamic process execution throttling is added to reduce the number of times RPA Bot attempts to restart a failing process. - You can now view the path to the analysis packages on the default run result message in RPA Manager if the setting to write an analysis package is enabled on RPA Bot. - You can now define the folder location for analysis packages of failed and successful workflow runs, using the **Custom Analysis package folder of failed workflows** and **Custom Analysis package folder of succeeded workflows** fields on the Session Monitoring panel of the RPA Bot Configurator. The folder that is selected in either field is maintained by the user. ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

## Fixed Issues
Issue ResolutionID

The RPA Bot daily midnight job now executes once daily at 0:00 UT.

W-14807645

Updated all copyrights to 2024.

W-14820545

The RPA Bot connection test is now performed with the correct RPA Manager URL.

W-14835335

Credential recognition is now working correctly with domain users.

W-15019592

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.0 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## August 19, 2024 ## What’s New - You can now set a display name for the RPA Bot during the installation. - You can now configure retries for the creation of the Secure Session. - RPA Bot now automatically detects and uses the proper RDP port. - Added support for new scheduling types in RPA Manager. - Updated the FreeRDP library to 3.5.1. ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

## Fixed Issues
Issue ResolutionID

Secure Session creation no longer fails when the user name includes a blank space.

W-15456958

Executions no longer fail with NullReferenceException errors when multiple sessions run in parallel.

W-15212084

Starting the execution of a process on demand no longer causes a NullReferenceException.

W-16185405

Invocable runs no longer show state Suspended when running.

W-16282214

Uninstalling RPA Bot is no longer possible if the RPA Bot Configurator is open.

W-15304241

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.1 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.2](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.2-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.10 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## May 20, 2025 ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

## Fixed Issues
Issue ResolutionID

The bot no longer ignores the Analysis Picture Count value when taking screenshots.

W-18356764

The bot no longer loses the connection if there are network issues during process streaming.

W-18379559

The bot no longer creates an error run result if there are no more sessions available.

W-18347801

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.11 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.14](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.14-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.12 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.14](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.14-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.13 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.14](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.14-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.14 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## July 31, 2025 ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

## Fixed Issues
Issue ResolutionID

RPA Bot no longer causes incorrect process execution on the RPA Manager due to network timeout errors.

W-19074454

RPA Bot no longer creates invalid analysis packages with incompatible path separators.

W-19074394

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.15 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.18](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.18-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.16 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. This version is deprecated. All of the features and fixed issues for this version are in version [1.7.18](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.18-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.17 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.18](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.18-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.18 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## November 14, 2025 ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

## Fixed Issues
Issue ResolutionID

RPA Bot no longer consumes excessive memory during execution.

W-19836005

RPA Bot no longer stops executing processes after network connectivity issues.

W-20207390

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.19 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premises environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.22](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.22-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.2 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## October 11, 2024 ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

## Fixed Issues
Issue ResolutionID

RPA Bot no longer closes a Secure Session unexpectedly.

W-16808007

RPA Bot no longer stops executing processes unexpectedly.

W-16548283

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.20 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premises environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.22](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.22-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.21 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premises environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.22](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.22-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.22 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## March 7, 2026 ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

## Fixed Issues
Issue ResolutionID

RPA Bot no longer returns an error when the session user’s password contains a double quote character.

W-21173699

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.23 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premises environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.24](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.24-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.24 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## March 26, 2026 ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

## Fixed Issues
Issue ResolutionID

RPA Bot no longer terminates processes when screenshot uploads exceed 30 seconds, ensuring the connection to the Session Runner (StSec) remains stable during longer upload durations.

W-21523306

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.3 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.4](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.4-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.4 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## December 16, 2024 ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

## Fixed Issues
Issue ResolutionID

An Remoting Exception no longer occurs when you create an analysis package on a low-performing system and experience a long wait time.

W-17318237

A Null Reference Exception no longer occurs on closing a Desktop Session.

W-17318518

An Internal Error no longer occurs when you install a MuleSoft RPA Bot on a computer with an existing Salesforce RPA Robot. Instead, the setup prompts you to uninstall the Salesforce RPA Robot first.

W-17334782

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.5 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.8](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.8-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.6 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.8](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.8-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.7 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.8](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.8-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.8 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## February 25, 2025 ## What’s New - Reported security vulnerabilities are now fixed - Updated the FreeRDP library to version 3.10.3 - Updated Nuget packages to address reported security vulnerabilities ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

RPA Recorder

6.4.0 and later

## Fixed Issues
Issue ResolutionID

Processes running in Secure Sessions no longer fail with error There are not enough sessions free.

W-17427528 / W-17529095

Updated Nuget packages to address reported security vulnerabilities.

W-17452040

An incorrect error message no longer shows in logs.

W-17586187

Process executions no longer fail to start with message Error while trying to evaluate if applications are active.

W-17764023

Remote application tests no longer fail to start the configured application.

W-17774289

Error logs no longer repeat the error message every two seconds when the bot reaches the session limit.

W-17853084

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Bot 1.7.9 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Bot is a software robot that runs in an on-premise environment and executes the assigned automations. This version is internal only. All of the features and fixed issues for this version are in version [1.7.10](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.10-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.6.0 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## April 29, 2024 ## What’s New - The new Submit Document to MuleSoft IDP action step enables you to send documents to IDP and process them with your published document actions. - The new Retrieve Results from MuleSoft IDP action step enables you to retrieve the results of a document processed by IDP after using the Submit Document to MuleSoft IDP action step. - The new Extract Pages From a PDF File action step enables you to extract, split, and merge PDF files. - The new `ErrorOut` global variable enables you to capture error messages from action steps. You can select between overriding or appending error messages in the new **Error Handling** tab in the workflow initialization settings. - The Read PDF File action step can now read forms and annotations. - The Set Variable action step wizard now supports Pin variables. - You can now specify a custom error message in the Force Error State action step. - RPA Recorder is now integrated with RPA Builder, enabling you to start a recording from different sections: - From Web Session action steps by using the wizard’s **Start Recording** button. - From the App Session action step by using the wizard’s **Start Recording** button. - From the Workbench by using the **Record** button. - From the Workflow by using the **Record Into**, **Record Before**, and **Record After** context menu items. - RPA Builder now includes new variable types as Activity Parameters: **Execution ID** and **Connected App Credentials**. - RPA Builder now notifies you when a new version is available to download. You can download and install new versions from the **Help** option in the menu bar. - The **Help** option in the menu bar now enables you to export log files, enable DEBUG level logs for RPA Builder and RPA Recorder, and select between appending or overwriting trace log files. - The workflow script logfile in analysis packages now includes the current base path. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

The BPMN Panel no longer shows empty when editing a Workflow in the Activity Library.

W-15606460

The JSONPath Expression Builder no longer shows empty values when editing and adding new filters.

W-15294418

Web Automation action steps no longer require manually scrolling to find and click buttons in forms.

W-15261043

RPA Builder no longer shows an incorrect error message when the login session expires.

W-15259497

Downloading a process with a missing Process Owner or Project Manager no longer causes an error.

W-14899347

The JSONPath Expression Builder no longer keeps filters from a file imported before when you import a new file.

W-14547303

The Check RegEx action step no longer logs the whole content of the output variable.

W-14454589

Run Results markings in the Workbench are no longer truncated

W-13902897

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.6.1 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premise application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. This version is internal only. All features and fixed issues for this version are implemented in version [6.6.2](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.6.2-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.6.2 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## May 17, 2024 ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

Web Session action steps no longer fail with message the maximum message size quota for incoming messages.

W-15702848

Workflows no longer fail the validation when you define empty variables.

W-15755711

Google Chrome processes no longer remain open after successfully running a process with the Web Session (Chrome) action step.

W-15756793

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.6.3 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premise application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. This version is internal only. All features and fixed issues for this version are implemented in version [6.6.4](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.6.4-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.6.4 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## May 27, 2024 ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

The MuleSoft IDP action steps now show all available document actions and enable you to search them within the action step.

W-15811626

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.6.5 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premise application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. This version is internal only. All features and fixed issues for this version are implemented in version [6.6.6](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.6.6-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.6.6 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## June 27, 2024 ## What’s New - The Tomcat dependency is upgraded to version 9.0.90 to address reported security vulnerabilities. - The CefSharp.Common library is upgraded to version 126.2.70 to address reported security vulnerabilities. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

Read PDF File no longer reads the entire PDF when you define a reading area.

W-16080478

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.6.7 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premise application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. This version is internal only. All features and fixed issues for this version are implemented in version [6.6.8](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.6.8-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.6.8 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## July 23, 2024 ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

Specifying a port in Web Session (Chrome) and Web Session (MS Edge) no longer causes an error.

W-16284120

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.0 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## August 27, 2024 ## What’s New - Execute macros on an Excel file with the new Execute Excel Macro action step. - Download or export files from your Google Workspace with the new Download from Google Drive action step. - Upload files to your Google Workspace with the new Upload to Google Drive action step. - Search files or folders in your Google Workspace and retrieve their name and ID with the new Search in Google Drive action step. - Mail Session (Outlook with OAuth) is renamed to Mail Session (OAuth) and now supports configuring a Gmail account. - The OAuth Credentials activity parameter now supports configuring Google as a mail provider. See [Migrating OAuth Credentials](#migrating-oauth-credentials) for instructions to migrate your existing OAuth Credentials activity parameters. - You can now configure the new Google API Service Account Credentials activity parameter to use for authentication with the Google Drive action steps. - RPA Builder now uses the system’s browser to authenticate the user. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

Append to Array no longer returns an empty result when appending to arrays that exceed 10100 characters.

W-16194888

RPA Builder no longer crashes when you push an activity paramater into a workflow and a generated Websession activity parameter is available.

W-16438279

The RPA Builder installer now links to the English version of the Adoptium OpenJDK download page.

W-15929142

## Migrating OAuth Credentials As part of the enhancement to Mail Session (OAuth) and the OAuth Credentials activity parameter, RPA Builder 6.7.0 automatically detects and updates any existing OAuth Credentials and removes all existing mappings of this activity parameter. RPA Builder appends `_updated` to migrated activity parameters. If your automation projects used OAuth Credentials, follow these steps after upgrading to RPA Builder 6.7.0 to complete the migration process: 1. In RPA Builder, locate the updated OAuth Credentials activity parameters. 2. Add the updated activity parameters to the corresponding workflows and map them to the corresponding Mail Session (OAuth) action steps. 3. In RPA Manager, create a new OAuth Credential global variable in the credential pool. 4. Map the new global variable with the updated OAuth Credentials activity parameters in the corresponding run configurations. ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.1 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premise application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. This version is internal only. All features and fixed issues for this version are implemented in version [6.7.2](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.2-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.10 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## April 8, 2025 ## What’s New - The CefSharp.Common library is upgraded to version 131.3.50 to address reported security vulnerabilities. - The Tomcat dependency is upgraded to version 9.0.105 to address reported security vulnerabilities. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

The copyright info no longer shows outdated.

W-18213300

RPA Builder no longer shows an incorrect error message when an email address is entered in the RPA Manager URL field.

W-18168131

RPA Builder no longer shows a Log file is used by another process error when trying to export log files.

W-17691093

The browser Wizard no longer fails to display pages that use a specific authorization token.

W-17441100

RPA Builder setup no longer fails to start due to error RPA Builder is running, please close it first and run this setup again when RPA Builder was closed successfully.

W-17699307

## Migrating OAuth Credentials As part of the enhancement to Mail Session (OAuth) and the OAuth Credentials activity parameter, RPA Builder 6.7.0 and later versions automatically detect and update any existing OAuth Credentials and remove all existing mappings of this activity parameter. RPA Builder appends `_updated` to migrated activity parameters. If your automation projects used OAuth Credentials, follow these steps after upgrading from a version earlier than RPA Builder 6.7.0 to complete the migration process: 1. In RPA Builder, locate the updated OAuth Credentials activity parameters. 2. Add the updated activity parameters to the corresponding workflows and map them to the corresponding Mail Session (OAuth) action steps. 3. In RPA Manager, create a new OAuth Credentials global variable in the credential pool. 4. Map the new global variable with the updated OAuth Credentials activity parameters in the corresponding run configurations. ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.11 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. This version is internal only. All features and fixed issues for this version are implemented in version [6.7.12](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.12-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.12 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## July 31, 2025 ## What’s New - The CefSharp.Common library is upgraded to address reported security vulnerabilities. - The Tomcat dependency is upgraded to version 9.0.106 to address reported security vulnerabilities. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

RPA Builder now accepts both Unix and Windows ZIP file formats for analysis packages, preventing loading errors when packages use different internal path separators.

W-19076042

The Tomcat dependency is upgraded to version 9.0.106 to address reported security vulnerabilities

W-18849660

The OAuth login dialog no longer throws assembly loading errors when authenticating.

W-19083573

The CefSharp.Common library is upgraded to address reported security vulnerabilities.

W-18748769

## Migrating OAuth Credentials As part of the enhancement to Mail Session (OAuth) and the OAuth Credentials activity parameter, RPA Builder 6.7.0 and later versions automatically detect and update any existing OAuth Credentials and remove all existing mappings of this activity parameter. RPA Builder appends `_updated` to migrated activity parameters. If your automation projects used OAuth Credentials, follow these steps after upgrading from a version earlier than RPA Builder 6.7.0 to complete the migration process: 1. In RPA Builder, locate the updated OAuth Credentials activity parameters. 2. Add the updated activity parameters to the corresponding workflows and map them to the corresponding Mail Session (OAuth) action steps. 3. In RPA Manager, create a new OAuth Credentials global variable in the credential pool. 4. Map the new global variable with the updated OAuth Credentials activity parameters in the corresponding run configurations. ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.13 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. This version is internal only. All features and fixed issues for this version are implemented in version [6.7.14](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.14-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.14 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## October 21, 2025 ## What’s New - The Tomcat dependency is upgraded to version 9.0.108 to address reported security vulnerabilities. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

The Read mail action no longer fails when saving email attachments with long filenames that exceed Windows file path limitations.

W-19615020

## Migrating OAuth Credentials As part of the enhancement to Mail Session (OAuth) and the OAuth Credentials activity parameter, RPA Builder 6.7.0 and later versions automatically detect and update any existing OAuth Credentials and remove all existing mappings of this activity parameter. RPA Builder appends `_updated` to migrated activity parameters. If your automation projects used OAuth Credentials, follow these steps after upgrading from a version earlier than RPA Builder 6.7.0 to complete the migration process: 1. In RPA Builder, locate the updated OAuth Credentials activity parameters. 2. Add the updated activity parameters to the corresponding workflows and map them to the corresponding Mail Session (OAuth) action steps. 3. In RPA Manager, create a new OAuth Credentials global variable in the credential pool. 4. Map the new global variable with the updated OAuth Credentials activity parameters in the corresponding run configurations. ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.15 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. This version is internal only. All features and fixed issues for this version are implemented in version [6.7.16](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.16-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.16 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## March 6, 2026 ## What’s New - You can now enable detailed debug logging in the trace log during execution without manually editing the configuration. To enable this feature, go to **Settings Action Steps** → **Error Handling Settings**. - The Tomcat dependency is upgraded to version 9.0.115 to address reported security vulnerabilities. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

RPA Builder no longer experiences memory problems from unused WorkflowRunProtocol functionality during long workflow runs (over six hours).

W-21258536

The page load strategy in the Chrome Web Session is now set correctly.

W-21357835

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.17 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. This version is internal only. All features and fixed issues for this version are implemented in version [6.7.18](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.18-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.18 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## April 27, 2026 ## What’s New - The Tomcat dependency is upgraded to version 9.0.117 to address reported security vulnerabilities. - The bundled AutoIt setup is upgraded to version 3.3.18.0 to address reported security vulnerabilities. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.19 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. This version is internal only. All features and fixed issues for this version are implemented in version [6.7.20](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.20-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.2 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## September 27, 2024 ## What’s New - The `StNetSh.exe` tool, part of the RPA Builder setup, now includes a digital signature to prevent security warnings. - The Google Chrome driver is updated to version 130. - The MS Edge driver is updated to version 129. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

Execute Excel Macro no longer shows an incorrect error message when including it inside an Excel Session.

W-16603539

Run Program no longer truncates the command line to 1024 characters.

W-16721834

Read Email no longer fails to download and save mail attachments.

W-16723360

The logfile no longer shows entire array values to improve readability.

W-16760451

RPA Builder no longer causes an error when using Json Query inside a loop.

W-16766643

Using the Exchange protocol in Mail Session no longer throws an error.

W-16793354

## Migrating OAuth Credentials As part of the enhancement to Mail Session (OAuth) and the OAuth Credentials activity parameter, RPA Builder 6.7.0 and later versions automatically detect and update any existing OAuth Credentials and remove all existing mappings of this activity parameter. RPA Builder appends `_updated` to migrated activity parameters. If your automation projects used OAuth Credentials, follow these steps after upgrading from a version earlier than RPA Builder 6.7.0 to complete the migration process: 1. In RPA Builder, locate the updated OAuth Credentials activity parameters. 2. Add the updated activity parameters to the corresponding workflows and map them to the corresponding Mail Session (OAuth) action steps. 3. In RPA Manager, create a new OAuth Credential global variable in the credential pool. 4. Map the new global variable with the updated OAuth Credentials activity parameters in the corresponding run configurations. ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.20 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## May 12, 2026 ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

RPA Builder no longer crashes when clicking Print Workflow after opening a process diagram for editing.

W-22271049

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.21 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. This version is internal only. All features and fixed issues for this version are implemented in version [6.7.22](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.22-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.22 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## June 24, 2026 ## What’s New - The Tomcat dependency is upgraded to version 9.0.118 to address reported security vulnerabilities. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.23 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. This version is internal only. All features and fixed issues for this version are implemented in version [6.7.24](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.24-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.24 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## August 14, 2026 ## What’s New - The **Tomcat** dependency is upgraded to version 9.0.120 to address reported security vulnerabilities. - The **Camunda** engine is upgraded to version 7.23.00. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

The transitive commons-fileupload dependency is updated to address reported security vulnerabilities.

W-23610276

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.25 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. This version is internal only. All features and fixed issues for this version are implemented in version [6.7.26](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.26-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.26 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## September 25, 2026 ## What’s New - The **Tomcat** dependency is upgraded to version 9.0.122 to address reported security vulnerabilities. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.3 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. This version is internal only. All features and fixed issues for this version are implemented in version [6.7.4](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.4-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.4 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## January 13, 2025 ## What’s New - Submit Document to MuleSoft IDP and Retrieve Results from MuleSoft IDP action steps now include these inbound variables: - **Action ID** - **Action Version** - **Anypoint URL** - **Organisation ID** See [Submit Document to MuleSoft IDP](https://docs.mulesoft.com/rpa-builder/latest/toolbox-mulesoft-idp-submit-document-to-mulesoft-idp#inbound-variables). - You can now define a custom attribute to read from when using the Get Web Element Text action step. - RPA Builder now shows a detailed error message if an installed service or component is missing. - The `stc_trace.log` file now includes the OS process ID in the workflow header section. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

Read Mail no longer saves attachments outside of the specified folder.

W-16942473

Saving mail attachments with invalid file names no longer causes an error. RPA Builder replaces the invalid characters and saves the file with the new name.

W-17201344

Read From Excel File no longer parses cell values incorrectly if the value starts with the n character.

W-17246126

Log files no longer show an incorrect display name when the Iterate Over Files action step executes.

W-17259672

The RPA Builder setup no longer fails to detect some Java editions during the installation process.

W-17339515

The AI OCR (screen-based) action step no longer shows an error message the first time you click OK in the wizard.

W-17395176

## Migrating OAuth Credentials As part of the enhancement to Mail Session (OAuth) and the OAuth Credentials activity parameter, RPA Builder 6.7.0 and later versions automatically detect and update any existing OAuth Credentials and remove all existing mappings of this activity parameter. RPA Builder appends `_updated` to migrated activity parameters. If your automation projects used OAuth Credentials, follow these steps after upgrading from a version earlier than RPA Builder 6.7.0 to complete the migration process: 1. In RPA Builder, locate the updated OAuth Credentials activity parameters. 2. Add the updated activity parameters to the corresponding workflows and map them to the corresponding Mail Session (OAuth) action steps. 3. In RPA Manager, create a new OAuth Credentials global variable in the credential pool. 4. Map the new global variable with the updated OAuth Credentials activity parameters in the corresponding run configurations. ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.5 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. This version is internal only. All features and fixed issues for this version are implemented in version [6.7.6](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.6-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.6 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## January 30, 2025 ## What’s New - The Tomcat dependency is upgraded to version 9.0.98 to address reported security vulnerabilities. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Fixed Issues
Issue ResolutionID

RPA Builder no longer fails to start due to an incorrect configuration of the Java Home path.

W-17637404

## Migrating OAuth Credentials As part of the enhancement to Mail Session (OAuth) and the OAuth Credentials activity parameter, RPA Builder 6.7.0 and later versions automatically detect and update any existing OAuth Credentials and remove all existing mappings of this activity parameter. RPA Builder appends `_updated` to migrated activity parameters. If your automation projects used OAuth Credentials, follow these steps after upgrading from a version earlier than RPA Builder 6.7.0 to complete the migration process: 1. In RPA Builder, locate the updated OAuth Credentials activity parameters. 2. Add the updated activity parameters to the corresponding workflows and map them to the corresponding Mail Session (OAuth) action steps. 3. In RPA Manager, create a new OAuth Credentials global variable in the credential pool. 4. Map the new global variable with the updated OAuth Credentials activity parameters in the corresponding run configurations. ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.7 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. This version is internal only. All features and fixed issues for this version are implemented in version [6.7.8](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.8-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.8 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## April 8, 2025 ## What’s New - The Tomcat dependency is upgraded to version 9.0.102 to address reported security vulnerabilities. - The AutoIT version bundled with RPA Builder is upgraded to version 3.3.18.0 to address reported security vulnerabilities. ## Compatibility
ApplicationVersion

RPA Recorder

6.6.0 and later

RPA Bot

1.0.0 and later

## Migrating OAuth Credentials As part of the enhancement to Mail Session (OAuth) and the OAuth Credentials activity parameter, RPA Builder 6.7.0 and later versions automatically detect and update any existing OAuth Credentials and remove all existing mappings of this activity parameter. RPA Builder appends `_updated` to migrated activity parameters. If your automation projects used OAuth Credentials, follow these steps after upgrading from a version earlier than RPA Builder 6.7.0 to complete the migration process: 1. In RPA Builder, locate the updated OAuth Credentials activity parameters. 2. Add the updated activity parameters to the corresponding workflows and map them to the corresponding Mail Session (OAuth) action steps. 3. In RPA Manager, create a new OAuth Credentials global variable in the credential pool. 4. Map the new global variable with the updated OAuth Credentials activity parameters in the corresponding run configurations. ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Builder 6.7.9 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Builder is the on-premises application that enables you to build automations by specifying the action steps of the process. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. This version is internal only. All features and fixed issues for this version are implemented in version [6.7.10](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.10-release-notes). ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Manager Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Manager is the cloud-based control plane for your automation projects. ## May 20, 2025 ### What’s New - You can no longer publish an invocable run configuration directly to Salesforce. Use [Anypoint Exchange](https://help.salesforce.com/s/articleView?id=platform.flow_build_use_flows_with_mulesoft_rpa.htm&type=5) or [API Catalog](https://help.salesforce.com/s/articleView?id=platform.api_catalog.htm&type=5) instead. Invocable run configurations already published to Salesforce remain active. The **Published to Salesforce** badges are removed from all published invocable run configurations. ### Fixed Issues
Issue ResolutionID

You can now re-assign bots of deployed invocable run configurations.

W-17807695

Process executions no longer return an error when they exceed the number of assigned sessions.

W-18380196

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user isn’t available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions isn’t available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## November 13, 2024 ### Fixed Issues
Issue ResolutionID

Interval scheduling no longer shows incorrect times for the time zones of the logged-in user.

W-16739470

Activity parameters within a run configuration are no longer blocked from editing.

W-16821955

The list of run configurations in the production phase no longer sorts incorrectly when clicking the Type column.

W-16887965

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user isn’t available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions isn’t available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## August 21, 2024 ### What’s New - The new **Process Publish Restriction for Production Phase** permission prevents a user from moving a process from Testing to Production. ### Fixed Issues
Issue ResolutionID

The Categories page in Process Management no longer shows a duplicate alert.

W-14436611

The Finance Analysis view no longer shows an incorrect Process Manager assignment.

W-14851495

Create Evaluation now shows an input character counter for the Name field.

W-15301328

RPA Manager no longer deletes assigned applications during a phase change from Build to Test or from Test to Production.

W-16380363

You can now update multiple RPA Bots in parallel.

W-16382151

You can no longer create a Category with an empty name.

W-16393605

RPA Bots can no longer receive the same task for executing the same run configuration.

W-16436289

Editing a deactivated Alert Rule no longer reactivates it.

W-16528085

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user isn’t available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions isn’t available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## August 19, 2024 ### What’s New - You can now configure additional types of process executions: interval trigger, cron trigger, and on-demand executions. These are supported by bots running version 1.7.0 or later. ### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user isn’t available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions isn’t available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## July 19, 2024 ### Fixed Issues
Issue ResolutionID

RPA Manager now properly saves changes made to the schedule of a process trigger execution for a run configuration in the production phase.

W-16169918

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user isn’t available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions isn’t available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## July 5, 2024 ### Fixed Issues
Issue ResolutionID

RPA Manager now properly saves the changes when you assign multiple sessions to an invocable run configuration.

W-16169918

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user isn’t available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions isn’t available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## June 28, 2024 ### Fixed Issues
Issue ResolutionID

You can now configure and save the execution timetable settings.

W-16110013

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user isn’t available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions isn’t available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## June 26, 2024 ### Fixed Issues
Issue ResolutionID

Updating the WebDriver while testing the Chrome Web Session or Edge Web Session action steps in RPA Builder no longer fails.

W-16080683

Activity Parameter values in JSON format no longer change when passed from one Activity to another.

W-15881024

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## June 20, 2024 ### Fixed Issues
Issue ResolutionID

Opening modals no longer fails.

W-16043771

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## June 13, 2024 ### Fixed Issues
Issue ResolutionID

The Usage Summary view no longer shows iconsistent data.

W-15286541

The Session Queues view no longer shows Max Sessions = 0 for a new bot running in Desktop Session mode.

W-15448320

Global variables no longer appear in the Unassigned Assets list after creation.

W-15450123

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## April 29, 2024 ### What’s New - RPA Manager now supports the new Intelligent Document Processing (IDP) action steps. ### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## April 24, 2024 ### What’s New - You can now publish invocable run configurations to Salesforce and use them as invocable actions in Flow. ### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## April 22, 2024 ### Fixed Issues
Issue ResolutionID

Process names with Japanese characters no longer get split on a process tile.

W-14835485

The content of table cells no longer gets truncated when there’s more space available.

W-15242583

The text of downloadable applications on the RPA Manager homepage no longer extends outside the buttons.

W-15312305

The field To (email) in an Alert Target is now enforced as a mandatory field.

W-11716347

The email address in an Alert Target is now verified.

W-11720892

Modifying an inactive Alert Rule no longer activates it.

W-15424278

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## April 09, 2024 ### What’s New - The taskbar elements of a run configuration’s **Execution** are now enabled by default. - The **Contact Support** link now redirects to the Salesforce help page. ### Fixed Issues
Issue ResolutionID

The Cost entries dialog of the Finance Analysis now shows the correct Investment string.

W-13863725

The start and end date of a Dashboard’s Analysis Interval is now set correctly.

W-14673236

The number of total entries shown at the end of the Analysis Packages widget now reflects the correct number.

W-14809568

A deleted alert rule no longer shows after deactivating it and activating another alert rule.

W-14845072

The Description field in the Bot Workflow Library no longer resizes incorrectly while editing it.

W-14866579

The Execution Timetable now shows tooltips while hovering the schedules.

W-14911375

A user is no longer able to reset the password of another inactive user in a non-migrated (legacy) organization.

W-15091753

The process monitor icon now shows in the Bot State and Operation view.

W-15106942

The tooltip of Process Board tasks now disappears when the mouse leaves the focus.

W-15233192

Deployed run configurations no longer show as available in the list of the Deploy process action.

W-15243974

You can now configure the option to send an email for user tasks when editing a scheduled run configuration.

W-15292890

Updating a reference to a Credential in a run configuration now shows the correct error if the user does not have ownership of the credential.

W-15303044

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## March 25, 2024 ### What’s New - RPA Manager now doesn’t pause a run configuration when a process execution fails because an RPA Bot can’t establish a secure session. - You can now create new projects from the following views: - **RPA Home** - **My RPA** > **My Backlog** - **My RPA** > **My Processes** - **Process Evaluation** > **Process Evaluation** - **Process Automation** > **Process Management** - **Process Automation** > **Process Management** > **** ### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## March 12, 2024 ### Fixed Issues
Issue ResolutionID

Selecting a process in Process Matrix now filters the selected process.

W-14657931

You can now remove all team assignments of a Credential.

W-14693509

Email notifications no longer contain a malformed URL.

W-14693359

Copying a process does no longer duplicate activity parameters.

W-14999548

The user workspace now saves changes properly.

W-15147413

The list of tags in the Bot Workflow Library Tags view now shows properly.

W-15156528

Saving public dashboards as private ones no longer fails.

W-15212411

Claiming or rejecting processes on the second page of the team backlog no longer fails.

W-15130497

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## February 28, 2024 ### What’s New - RPA Manager now supports automatic RPA Bot updates for bots running version 1.5.0 or later. ### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

An RPA Bot shows an error in Tasks when a user tries to update the bot while the bot is already executing an update task.

Ignore the error message, the first task updates the bot successfully regardless of the message.

W-15129879

## February 15, 2024 ### Fixed Issues
Issue ResolutionID

The Qualifiers and Benefits columns within the Process Evaluation module no longer show incorrect values.

W-14657848

The Process Streaming module no longer shows a Gateway Timeout error.

W-14826933

You can now edit a process when the process owner is not specified.

W-14899326

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## January 31, 2024 ### What’s New - RPA Manager now supports automatic RPA Bot updates for bots running version 1.5.0 or later. When a new version of RPA Bot is available, RPA Manager shows the **Update** button in the **Bots** view of the **Bot Management** module, which enables you to update installed RPA Bots to the latest version. ### Fixed Issues
Issue ResolutionID

You can now edit and delete run configurations that show on the second and all following pages.

W-14820123

You can now open the Test tab in Deployment Map even if the project manager of one of the processes has been deleted.

W-14808512

Finance Analysis no longer shows an error if the process owner of one of the processes has been deleted.

W-14820620

Bot Workflow Library is now available in Japanese.

W-14836772

The tooltips and descriptions on the details panel of the Bot Workflow Library now show properly.

W-14852032

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## January 15, 2024 ### What’s New - You can now reassign assets from one user to another. ### Fixed Issues
Issue ResolutionID

Republishing a process to Anypoint Exchange now updates the asset’s description.

W-11865540

Deleting a test plan in a process' test phase no longer revokes all other test plans.

W-14665127

You can now remove a user from a process' test plan in the test phase.

W-14666270

The Bots tab in a scheduled or invocable run configuration now shows tooltips while you hover over the indicator that precedes the RPA Bot’s name.

W-14686687

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## December 12, 2023 ### What’s New - RPA Manager now implements Anypoint Audit Logging, which enables you to see a queryable history of actions performed with RPA objects. - The **Usage Summary** is now grouped by process category. - The **Usage Summary** now shows the Cumulated Bot Run Time and Average Bot Run Time additionally in _hh:mm:ss_ format. ### Fixed Issues
Issue ResolutionID

The Upcoming Process Changes view no longer shows an error when selecting the table header Last edited.

W-14293208

Process Run Results no longer show Endtime and Duration if the respective process is in status running.

W-14311008

You can now download RPA Bot logs in the Bot Management when the RPA Bot is in status out of service time.

W-14378109

You can now use the same name for global variables and credentials in different organizations. Names are unique within the same organization.

W-14378876

The close button of the videos player in the home page no longer dissappears after resizing the browser’s window.

W-14387182

You can now create a global variable of type integer with a negative value.

W-13460628

The dashboard widget Business Process Performance now aggregates successful and failed process executions.

W-14438065

The Upcoming Process Changes view no longer shows copied processes that have not been uploaded from RPA Builder at least once.

W-14292949

You can now modify users assigned to user tasks in a run configuration.

W-14588383

You can now modify the name of RPA Bot API keys.

W-14614289

### Known Issues
Known IssueWorkaroundID

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## November 3, 2023 ### Fixed Issues
Issue ResolutionID

Global variables and credentials in the credentials pool no longer have a limitation.

W-14321062

Processes no longer stop executing on RPA Bots.

W-14329929

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## October 19, 2023 ### Fixed Issues
Issue ResolutionID

Making a copy of a copied process no longer causes an error.

W-14194459

The Bot Workflow Library menu inside the Process Automation module no longer stops showing in the UI.

W-14313721

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## October 12, 2023 ### What’s New - The **Cumulated Used Credits** column is now removed from the usage summary. - Global variable of type Alphanumeric is no longer limited to 200 characters. - You can now set time-limited debug logging for RPA Bots. ### Fixed Issues
Issue ResolutionID

The Description column of the evaluation criterion no longer disappears randomly.

W-14037661

Getting the status of an execution through the RPA API no longer throws an error when the executionId contains special characters.

W-14059317

The Japanese translation is now available for the deployment map.

W-14168737

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## October 5, 2023 Changes made in this release were reverted. ## September 25, 2023 ### What’s New - You can now open the Activity library in RPA Manager. - Process run results now show the execution ID of invocable and scheduled processes. - Error dialogs now include a request ID to improve troubleshooting. ### Fixed Issues
Issue ResolutionID

You can now link Global variables in test plans in the test phase.

W-13980494

Activity parameters now show properly in claimed User tasks when the User task is the first activity of a process.

W-13999038

Activity parameters in a test plan in the test phase no longer show an incorrect value.

W-14008168

Starting an automation from a process evaluation in the menu My Backlog no longer shows an error.

W-14013519

Deleted users and teams in Anypoint Access Management no longer show in RPA Manager.

W-13989445

Process run statistics in Bot Management now show data only for the logged in user.

W-14026825

Rejected process evaluations now show the correct state.

W-14048993

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## August 23, 2023 ### Fixed Issues
Issue ResolutionID

Editing a run configuration for a process in the test phase when the process is executing now shows a detailed warning.

W-13644464

Saving the configuration of an RPA Bot is now possible only after all data finishes loading.

W-13896999

The Benefits column in My Backlog now shows a correct column header.

W-13932862

The Session Queues of an RPA Bot now shows all priority queues.

W-12488822

Starting an automation from My Backlog no longer leads to an error.

W-13933409

Team list views now supports showing more than 100 teams.

W-13916936

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## August 4, 2023 ### Fixed Issues
Issue ResolutionID

Invocable processes no longer fail to execute when the Run in Secure Session > as this user configuration in the Execution tab links to a credential in the credential pool.

W-13871254

Long process names no longer span outside the window when you click on more in a process card to see the complete description of the process.

W-13843102

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## July 26, 2023 ### What’s New - RPA Manager is now integrated with Anypoint Platform. See [Anypoint Platform Integration Overview](https://docs.mulesoft.com/rpa-home/anypoint-migration-overview) for details about the new features and benefits for the new RPA customers and how the existing RPA customers can request migrating their organization to Anypoint Platform. ### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

A new Anypoint Platform user is not available in dropdown lists.

The new Anypoint Platform user must log in at least once to RPA Manager to appear in the lists of available users.

W-13833054

A user with recently added RPA Project Manager permissions is not available in the dropdown menu for project manager assignments.

The user with the RPA Project Manager permissions must log out from RPA Manager and then log in again to appear in the list of available project managers.

W-13833036

## July 25, 2023 ### What’s New - The Deployment Map now includes two different tabs to filter processes that are in the Production or Testing phases. - The Deployment Map now includes improved tooltip texts and color schema for better readability. ### Fixed Issues
Issue ResolutionID

The Send email notification to all related users when the task is ready for processing checkbox no longer shows enabled when a process does not have user tasks.

W-13664033

The validation process before starting a test or deploying a run configuration now shows Error or Warning messages. RPA Manager now blocks a test or deployment when an error occurs during validation.

W-13656062

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## July 18, 2023 ### Fixed Issues
Issue ResolutionID

Notification emails no longer show an incorrect username when a process changes phase.

W-13111442

Changing the session count within a scheduled run configuration now reflects properly on the RPA Bot.

W-13673157

The Process Execution Plans page no longer shows an error when loading.

W-13697922

Creating a process evaluation without specifying a category no longer throws an error.

W-13717288

You can now specify or modify Activity Parameter in run configurations that are in test or production phase.

W-13721840

RPA Manager no longer shows a Malformed URI error if the URL is valid.

W-13753194

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## July 5, 2023 ### Fixed Issues
Issue ResolutionID

Creating and modifying credentials in the Credential Pool now works correctly.

W-13704977

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## June 22, 2023 ### Fixed Issues
Issue ResolutionID

You can now select users in the Execution section of an invocable run configuration.

W-13490993

The category of a process evaluation now shows properly after renaming it.

W-13517620

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## June 12, 2023 ### What’s New - Process run results now show the messages of all activities that include **Write bot message** action steps. - User and bot API keys are no longer visible after their creation to improve security. API keys are available for copy only during creation. ### Fixed Issues
Issue ResolutionID

The descriptions of privileges now show correctly.

W-13477475

Users no longer receive an error when they try to delete a credential in the Credential Pool if they are referenced to that credential via a user group only.

W-13505515

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## May 23, 2023 ### Fixed Issues
Issue ResolutionID

The time zone Sao Tome Standard Time is now supported.

W-12658271

The time zone Samoa now displays correctly.

W-12173355

The link to Anypoint Platform in the top navigation bar now redirects correctly.

W-13220858

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## May 15, 2023 ### What’s New - RPA Manager now shows a top navigation bar. - Improved the **Execution** tab for Run Configuration: - The **Run in existing desktop session as logged in user** option is now **Run in existing Console or RDP session if specified user is signed in**. - Selecting **Run in existing Console or RDP session if specified user is signed in** now requires you to specify a user. - These settings work in RPA Bots running version 1.2.0 or later. Earlier versions of RPA Bot ignore these settings. - The **MuleSoft RPA Builder assignment** option from **User Management** is now the new privilege **Builder Usage**. - The **Project Manager** flag of a user is now replaced by the new privilege **Project Management**. ### Fixed Issues
Issue ResolutionID

Removing a user group from an unprocessed user Task no longer lead to an error.

W-13062881

Users can no longer download a process in RPA Builder after the Builder Usage permission is revoked.

W-13071216

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, ensure that you import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## April 20, 2023 ### Fixed Issues
Issue ResolutionID

RPA Bots no longer remain blocked after failing to create a Secure Session because RPA Manager now pauses a failing run configuration after five consecutive errors.

W-12718095

The list of users to assign to unprocessed user tasks no longer shows empty.

W-13027522

The run results for a process in Production and the process run statistics for an RPA Bot no longer show different results.

W-12974321

Paused run configurations are no longer shown in the list of run configurations that you can pause.

W-12774698

Process streaming is no longer unresponsive.

W-13011702

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, ensure that you import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## April 5, 2023 ### Fixed Issues
Issue ResolutionID

Bot tasks no longer show internal identifiers instead of text.

W-12767736

The content of the Process Streaming view now shows correctly if you quickly switch between views.

W-12723795

A dialog showing a "Gateway Timeout" error no longer appears when staying on a page for several minutes.

W-12535589

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, ensure that you import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## March 17, 2023 ### Fixed Issues
Issue ResolutionID

Using alphanumeric global variables containing #} in their value no longer causes an endless loading screen for table views.

W-12636515

The values of global variables used in a run configuration now show correctly.

W-12664566

Publishing a process containing an empty BPMN to the test phase no longer causes an internal server error.

W-12607151

Starting an invocable process by calling the PUT endpoint no longer returns a 404 - Not found error.

W-12701176

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, ensure that you import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## March 13, 2023 ### Fixed Issues
Issue ResolutionID

RPA Manager now automatically restarts process executions carried out by an RPA Bot when the bot restarts due to a failure, such as a crash or a system reboot.

W-12361095

The content of the table in Activity Parameter from the Create run configuration menu is now properly aligned.

W-12234671

The content of the table in Evaluation Criteria now loads without errors.

W-12544373

### Known Issues
Known IssueWorkaroundID

Editing a process while you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, ensure that you import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## February 24, 2023 ### What’s New - You can now assign credentials in the Credential Pool to users and user groups. RPA Manager automatically affiliates credentials that were created prior to this release with all users. You can edit credentials to change affiliated users. - The new **Copy to Clipboard** button in user tasks enables you to copy activity parameter values to the clipboard. - The color scheme of process boards now aligns with Salesforce style. ### Fixed Issues
Issue ResolutionID

You can no longer remove a process assigned to a user if that user is either the project owner or the project manager.

W-12193883

Users can no longer create multiple evaluation criteria with the same name.

W-12024864

Long activity parameter names are now truncated to enhance their visibility.

W-12244827

Users no longer see incorrect privileges assigned when logging in to RPA Manager after a different user logs out.

W-12421163

### Known Issues
Known IssueWorkaroundID

Editing a process after you copy it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, ensure that you import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## February 01, 2023 ### Fixed Issues
Issue ResolutionID

Deleting a test run configuration no longer causes a database error.

W-12463062

Deleting a production run configuration no longer causes a database error.

W-12463050

Uploading a workflow from RPA Builder no longer causes a database error.

W-12463075

### Known Issues
Known IssueWorkaroundID

Editing a process after you make a copy of it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, ensure that you import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## January 26, 2023 ### What’s New - The password reset email now shows information about appending the 2FA token for users that have 2FA enabled. - The initial mail sent to the first administrator user of an organization now contains more information about their role and responsibilities. ### Fixed Issues
Issue ResolutionID

Process Streaming now properly shows the process execution.

W-12421442

### Known Issues
Known IssueWorkaroundID

Editing a process after you make a copy of it causes RPA Builder to fail to import the copied process.

Before making any changes to the original process, ensure that you import the copy in RPA Builder and then upload the copy to RPA Manager. After uploading the copy to RPA Manager, you can modify the original process and the copy without experiencing any issues.

W-12472442 / W-11954705

## January 18, 2023 ### Fixed Issues
Issue ResolutionID

Two-Factor-Authentication (2FA) can now be deactivated for other users.

W-12367549

List views now load properly and show their containing entities.

W-12288330

## January 13, 2023 ### What’s New - Added a new Activity Parameter of type OAuth credentials. - Now, RPA Manager explicitly declares time zones if they differ from the logged user’s time zone. ### Fixed Issues
Issue ResolutionID

Published OpenAPI specifications to Anypoint Exchange no longer contain a wrong required specification.

W-12141693

Invocable run configurations are no longer configurable from the Deployment Map.

W-12148933

The team members of a process are now shown in the process' tile.

W-12186972

The user’s configurations are now properly saved in their workspace.

W-12194534

## December 16, 2022 ### Fixed Issues
Issue ResolutionID

RPA Manager no longer includes the userName and password fields for the AWS Credentials type in the OpenAPI Specification (OAS) when you publish an invocable run configuration to Anypoint Exchange.

W-12141693

The RPA Manager UI now shows a note when a date and time are not in the same time zone as the logged-in user.

W-12028146

## December 8, 2022 ### Fixed Issues
Issue ResolutionID

RPA Manager no longer causes a delay in the execution of MuleSoft Composer flows when you run two asynchronous flows that execute RPA processes.

W-12173987 / W-12175608

## December 5, 2022 ### Fixed Issues
Issue ResolutionID

RPA Manager no longer causes a delay in the execution of MuleSoft Composer flows when you run two asynchronous flows that execute RPA processes.

W-12150402 / W-12133450

The Secure Session Assignment Information button now shows correctly in run configurations regardless of the execution settings.

W-12121199

The default custom interval for Process Run Statistics now starts at the current time and ends 1 hour earlier.

W-12104577

## November 22, 2022 ### Fixed Issues
Issue ResolutionID

RPA Manager no longer causes a Timeout error in MuleSoft Composer when you use the Invoke RPA Process action to query large amounts of data.

W-12083939

## November 17, 2022 ### What’s New - Users are now able to reset their own password. - The color scheme, typography, and buttons changed to better align with MuleSoft’s style. - The **Home** menu item now shows a badge that informs users about new client releases. ### Fixed Issues
Issue ResolutionID

Users can now login using ZScaler. RPA Manager no longer fails the login attempt when ZScaler submits more than one IP address in an HTTP header.

W-12040207

## October 13, 2022 ### What’s New - The loading time of RPA Manager web pages is improved. - You no longer require the privilege **User Management Administration** to create an API key for yourself. ### Fixed Issues
Issue ResolutionID

RPA Manager no longer fails to upload a Workflow that has more than 10 revisions.

W-11808671

## September 29, 2022 ### What’s New - The **Download Applications** section on the landing page is now collapsible, which enables you to see the **Need More Help** section without scrolling. - The videos from the **Learning Center** now show their duration. - The usage summary now contains a month selector. Thus, the user no longer needs to specify a time range with start and end dates. - The image of an application is now limited to a maximum size of 5 MB. - A user’s profile image is now limited to a maximum size of 5 MB. ### Known Issues
Issue ResolutionID

A user cannot upload more than 10 revisions of a workflow.

W-11808671

## August 1, 2022 ### What’s New MuleSoft announces the release of RPA Manager, the cloud-based control plane that enables you to: - 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. ## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Overview > For the full documentation index, see: https://docs.mulesoft.com/llms.txt MuleSoft Robotic Process Automation (RPA) enables you to automate business processes and tasks by using bots, which helps save time and prevent introducing human errors. MuleSoft RPA can automate processes that require human input and can also interact with systems that do not have an API available for consumption. RPA bots can interact with applications, extract data, read images, and manipulate computer input faster and more accurately than humans. MuleSoft RPA integrates with Anypoint Platform, which enables sharing and reusing automation assets through Exchange, and with MuleSoft Composer to connect applications and data with you automation projects. - See [Create an Anypoint Platform Account](https://docs.mulesoft.com/access-management/managing-your-account#how-to-create-your-account) for instructions on creating your Anypoint Platform account. - See [MuleSoft Composer: Getting Started](https://docs.mulesoft.com/composer/ms_composer_prerequisites) for instructions to setup and configure your Composer account. ## Use Cases Your company can benefit in many ways by implementing RPA into their processes, either by saving time, reducing costs, or preventing errors caused by human input. The most common use cases for RPA include: - Data Extraction and Data Entry Extract data from PDF, CSV, and other file formats and send this data to other systems. - Payroll Processing Automate payroll data entry and validate the information across multiple systems. - Price Comparisons Automate the monitoring of input prices and competitor prices. - Processing Refunds Automate the processing of customer refund requests to make them quicker and provide the best experience for customers. - Customer Information Updates Update customer information automatically across different systems that do not have an API and that are accessible only through the UI. ## RPA Lifecycle MuleSoft provides a complete solution to manage the RPA development lifecycle, which includes the following phases: - Evaluation In this phase you use the Process Evaluation module in RPA Manager to determine if a business process qualifies to be automated by evaluating the costs savings and benefits of building the automation based on the process’s complexity, stability, and other key values. - Design If the evaluation is complete and the process qualifies for automation, you can start designing the workflow of the automation that specifies the actions to perform and the conditions under which to perform those actions. RPA Manager uses the Business Process Model and Notation (BPMN) to create the workflows. You can design the workflow manually by using the drag and drop tools in RPA Manager, or automatically by using the RPA Recorder. - Build In the build phase, you fill the previously-created process with specific instructions for humans and bots. With RPA Builder you can import a BPMN diagram generated in RPA Manager, and then drag and drop operations or record key inputs to specify the action steps. When you finish building the process, you upload it to RPA Manager. - Test During the test phase, you create different testing scenarios for your automation projects to confirm that they work as expected. This phase works as the quality assurance step of the development process. In this phase, you can create real-world test scenarios using different parameters and can troubleshoot failed steps when there are errors. - Deployment When the automation project successfully completes the testing phase, you are ready to deploy. In the deployment phase, you use RPA Manager to set up the production parameter values, configure the process execution schedule, and select the RPA bots to run the process. You can deploy one automation process to one or multiple RPA bots. - Monitor RPA Manager provides different management and monitoring options for your deployed automations. You can monitor the performance of the deployed automations, configure alerts and notifications when there are issues, and locate the source of these issues. ## RPA Applications MuleSoft RPA provides the following applications that enable you to manage the complete development lifecycle of your automation projects:
ApplicationDescriptionFeatures

RPA Manager

RPA Manager is the cloud-based control plane for the automations that is integrated into Anypoint Platform.

  • 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.

RPA Builder

RPA Builder is the on-premise application that enables you to build the automations by specifying the steps of the process.

  • Download and upload automation assets to RPA Manager.

  • Add the automation logic to the processes.

  • Run local tests for the automations.

RPA Recorder

RPA Recorder is an on-premise tool that assists during the building phase of a process by automatically recording action steps from your local environment.

  • Build a BPMN diagram based on user actions.

  • Capture keyboard input, mouse clicks, and used applications.

  • Add comments and variables during the recording.

  • Automatically take screenshots per each mouse click.

RPA Bot

RPA bots are software robots that run in an on-premise environment and execute the assigned automations. You can manage bots from RPA Manager.

  • Execute the automations.

  • Read text and images.

## See Also - [Hardware and Software Requirements](https://docs.mulesoft.com/rpa-home/hardware-software-requirements) - [Tutorial: Build an Automation from Start to Finish](https://docs.mulesoft.com/rpa-home/automation-tutorial-introduction) - [Use Case: Extracting Data from a Legacy System](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction) - [RPA Manager Overview](https://docs.mulesoft.com/rpa-manager/) - [RPA Builder Overview](https://docs.mulesoft.com/rpa-builder/latest/) - [RPA Recorder Overview](https://docs.mulesoft.com/rpa-recorder/latest/) - [RPA Bot Overview](https://docs.mulesoft.com/rpa-bot/latest/) - [Anypoint Exchange](https://docs.mulesoft.com/exchange/) --- product: RPA --- # RPA Recorder 6.5.0 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Recorder enables you to record a business process for automation. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## November 28, 2023 ## What’s New - The **Retake** option is now shown as a button in a dropdown. Using the **Retake** option, you can delay the screen freeze for capturing image-based mouse clicks. This assists with preparing collapsible menus and hidden elements before the screen capture freezes. User and mouse actions are not recorded during the delay. - You can now set the initial screen freeze delay directly from the image-based mouse clicks toolbar. - When recording a Web Task, the selected area now has a red border. - RPA Recorder now always generates an `RPARecorder` subfolder during installation. - RPA Recorder now uses TLSv1.3 by default, and HTTP is now disabled for all API requests. - When recording in Notepad++, long window titles and name attributes are now truncated in the Documentation section of the RPA Recording Editor. - The Settings UI and Log files panels are updated, as well as the Manual Activity and Comment dialogs. ## Other Important Changes - The attribute selection panel is no longer enabled and cannot be expanded or collapsed when recording image-based mouse clicks in a Web Task. After the image-based mouse clicks recording is finished, the panel can be opened. - Upon completion of recording image-based mouse clicks for a Web or Bot Task, a message now appears to indicate recording has been resumed. - When recording image-based mouse clicks in a Web Task, the browser window cannot be minimized, and the address bar and buttons are no longer enabled in the browser window. ## Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

## Fixed Issues
Issue ResolutionID

Restarting image-based mouse clicks after cancelling the Scaling Warning dialog no longer leads to multiple toolbars.

W-13941631

When selecting the capture area on a Web Task while capturing image-based mouse clicks, the Selected area cannot be null error no longer occurs.

W-13966122

The Screen capture is null error no longer occurs when closing the Display Settings Warning dialog.

W-13980627

When capturing image-based mouse clicks during Web Task recording, clicks on menu items in dropdowns are now recorded.

W-14043830

When capturing image-based mouse clicks during Web Task recording, the browser window now freezes properly when selecting a dropdown menu.

W-14036847

When capturing image-based mouse clicks, pressing Alt+F4 in the capture image step no longer leads to an error.

W-14025390

When capturing image-based mouse clicks, the elapsed time now matches the specified delay time.

W-14007202

Changing the scaling when capturing image-based mouse clicks is now recognized.

W-13778082

RPA Recorder no longer fails to load the BPMN from RPA Manager when the width or height values are not a whole number.

W-13957382

RPA Recorder no longer crashes when attempting to open a web page that has an invalid URL containing two periods. Instead, a Page is not available error message displays.

W-13990958

When recording a hover event for a Bot Task, the active window is now recorded.

W-12752823

When opening a recorded BPMN in Notepad++ in a Bot Task, HTML is now being escaped in documentation properly and only the events from the recording are documented.

W-14292760

An error message now appears when a BPMN fails to download.

W-14128004

Improved the content of the error message that displays when a BPMN fails to upload.

W-12708752

The BPMN is now positioned correctly when searching for an activity name in the main RPA Recorder window.

W-14160638

The BPMN now loads successfully after conducting a search of the BPMN in the main RPA Recorder window.

W-14283085

Clearing the cache while recording a Web Task now works properly.

W-14258875

The Page is not available error now displays when navigating back and forward in a browser while recording a Web Task.

W-12481508

## See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Recorder 6.5.2 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Recorder enables you to record a business process for automation. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## December 5, 2023 ### Compatibility
ApplicationVersion

RPA Builder

6.4.0 and later

### Fixed Issues
Issue ResolutionID

The Recording Toolbar no longer displays while adding manual screenshots. Once screenshots are confirmed, the toolbar displays again.

W-14573347, W-14572817

RPA Recorder no longer creates the RPARecorder subfolder in the RPARecorder folder when upgrading from version 6.4.4 to 6.5.2.

W-14600072

### See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Recorder 6.6.0 Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Recorder enables you to record a business process for automation. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## April 29, 2024 ## What’s New - You can now start RPA Recorder from RPA Builder via the Activity Workflow or by clicking the new **Record** option in the [Workbench Toolbar](https://docs.mulesoft.com/rpa-builder/latest/workbench-toolbar-overview). RPA Builder automatically generates the workflow or single App or Web session, and you no longer need to generate the workflow by uploading the recording to RPA Manager and then downloading it in RPA Builder. - The documentation in the Process Recording Editor is redesigned to improve the appearance and readability. - Layout and styling changes are made to the user interface of the Process Recording Editor. - When starting RPA Recorder from RPA Manager, you can now install the latest RPA Recorder version from the RPA Recorder home page. An **Update Available** button shows on the home page when a new version is available. - You can now use the ESC key on your keyboard to cancel or close dialogs and pop-up messages in RPA Recorder. ### Compatibility
ApplicationVersion

RPA Builder

6.6.0 and later

### Fixed Issues
Issue ResolutionID

Audio and video no longer continues to play after closing your browser when recording a Web Task.

W-14965350

RPA Recorder no longer crashes after navigating to youtube.com when recording a Web Task.

W-14996105

The correct error message now shows when loading a debug file into the Process Recording Editor, informing you that the jsonForBuilder file format is not supported in the current mode.

W-15211454

HTML escape characters are now encoded in your recording’s documentation and displayed in plain text format.

W-15099313

Text that you copy during a Bot or Web Task recording is now truncated in your recording’s documentation.

W-15038064

The text in the Name field in the Add Activity dialog for a User Task now shows in your recording’s documentation.

W-15038454

Pressing Alt+Tab to focus the Notepad app when recording a Bot Task now selects Notepad as expected when you release the Alt key.

W-14607692

Highlighting and recording events now works as expected when recording a Web Task on salesforce.com as well as on subsequent websites you go to after going to salesforce.com.

W-14666842

### See Also - [Salesforce Help](https://help.salesforce.com) - [MuleSoft Services](https://www.mulesoft.com/support-and-services) --- product: RPA --- # RPA Release Notes > For the full documentation index, see: https://docs.mulesoft.com/llms.txt RPA Manager instances automatically update to the latest version available; you don’t need to perform any tasks to move to the new version. The latest versions of RPA Builder, RPA Recorder, and RPA Bot become available for download in RPA Manager as soon as they are released and you must manually update them on your local environment. To take advantage of all new features, improvements, and bug fixes, ensure that you are using the latest version of each RPA application. ## RPA Manager - [RPA Manager Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-manager-release-notes) ## RPA Builder - [RPA Builder 6.7.26 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.26-release-notes) - [RPA Builder 6.7.25 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.25-release-notes) - [RPA Builder 6.7.24 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.24-release-notes) - [RPA Builder 6.7.23 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.23-release-notes) - [RPA Builder 6.7.22 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.22-release-notes) - [RPA Builder 6.7.21 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.21-release-notes) - [RPA Builder 6.7.20 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.20-release-notes) - [RPA Builder 6.7.19 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.19-release-notes) - [RPA Builder 6.7.18 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.18-release-notes) - [RPA Builder 6.7.17 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.17-release-notes) - [RPA Builder 6.7.16 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.16-release-notes) - [RPA Builder 6.7.15 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.15-release-notes) - [RPA Builder 6.7.14 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.14-release-notes) - [RPA Builder 6.7.13 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.13-release-notes) - [RPA Builder 6.7.12 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.12-release-notes) - [RPA Builder 6.7.11 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.11-release-notes) - [RPA Builder 6.7.10 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.10-release-notes) - [RPA Builder 6.7.9 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.9-release-notes) - [RPA Builder 6.7.8 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.8-release-notes) - [RPA Builder 6.7.7 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.7-release-notes) - [RPA Builder 6.7.6 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.6-release-notes) - [RPA Builder 6.7.5 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.5-release-notes) - [RPA Builder 6.7.4 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.4-release-notes) - [RPA Builder 6.7.3 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.3-release-notes) - [RPA Builder 6.7.2 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.2-release-notes) - [RPA Builder 6.7.1 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.1-release-notes) - [RPA Builder 6.7.0 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.7.0-release-notes) - [RPA Builder 6.6.8 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.6.8-release-notes) - [RPA Builder 6.6.7 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.6.7-release-notes) - [RPA Builder 6.6.6 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.6.6-release-notes) - [RPA Builder 6.6.5 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.6.5-release-notes) - [RPA Builder 6.6.4 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.6.4-release-notes) - [RPA Builder 6.6.3 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.6.3-release-notes) - [RPA Builder 6.6.2 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.6.2-release-notes) - [RPA Builder 6.6.1 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.6.1-release-notes) - [RPA Builder 6.6.0 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-builder-6.6.0-release-notes) ## RPA Recorder - [RPA Recorder 6.6.0 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-recorder-6.6.0-release-notes) - [RPA Recorder 6.5.2 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-recorder-6.5.2-release-notes) - [RPA Recorder 6.5.0 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-recorder-6.5.0-release-notes) ## RPA Bot - [RPA Bot 1.7.24 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.24-release-notes) - [RPA Bot 1.7.23 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.23-release-notes) - [RPA Bot 1.7.22 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.22-release-notes) - [RPA Bot 1.7.21 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.21-release-notes) - [RPA Bot 1.7.20 Release Notes (Deprecated)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.20-release-notes) - [RPA Bot 1.7.19 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.19-release-notes) - [RPA Bot 1.7.18 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.18-release-notes) - [RPA Bot 1.7.17 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.17-release-notes) - [RPA Bot 1.7.16 Release Notes (Deprecated)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.16-release-notes) - [RPA Bot 1.7.15 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.15-release-notes) - [RPA Bot 1.7.14 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.14-release-notes) - [RPA Bot 1.7.13 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.13-release-notes) - [RPA Bot 1.7.12 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.12-release-notes) - [RPA Bot 1.7.11 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.11-release-notes) - [RPA Bot 1.7.10 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.10-release-notes) - [RPA Bot 1.7.9 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.9-release-notes) - [RPA Bot 1.7.8 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.8-release-notes) - [RPA Bot 1.7.7 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.7-release-notes) - [RPA Bot 1.7.6 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.6-release-notes) - [RPA Bot 1.7.5 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.5-release-notes) - [RPA Bot 1.7.4 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.4-release-notes) - [RPA Bot 1.7.3 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.3-release-notes) - [RPA Bot 1.7.2 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.2-release-notes) - [RPA Bot 1.7.1 Release Notes (Internal)](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.1-release-notes) - [RPA Bot 1.7.0 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.7.0-release-notes) - [RPA Bot 1.6.2 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.6.2-release-notes) - [RPA Bot 1.6.0 Release Notes](https://docs.mulesoft.com/rpa-home/release-notes/rpa-bot-1.6.0-release-notes) --- product: RPA --- # Secure Sessions > For the full documentation index, see: https://docs.mulesoft.com/llms.txt In RPA automations, a bot simulates a human user. The bot logs in to a system, sees the screen, and can interact with the UI via keystrokes and mouse actions. The bot can even interact with legacy systems that do not provide an API. The bot logs in to the computer, where it is installed. But, of course, it does not sit on a chair in front of the desktop. Nevertheless, if you enter the room where the computer is, you can see what the bot is doing: The screen shows the open applications, the mouse moves around and typing appears in forms. In MuleSoft RPA, we call this a _Desktop Session_. To prevent unauthorized data access or manipulation, you must secure the physical room. Or you can use what MuleSoft RPA calls _Secure Sessions_. Secure Sessions are hidden Desktop sessions that run in the background and are accessible only to the bot. An additional advantage of using Secure Sessions is that the bot can multiply itself to run several process instances in parallel. To use Secure Sessions you must ensure that all prerequisites are met and all responsible persons are informed. ## General Considerations - A bot either can run in Desktop Session or Secure Session mode. You can change the mode while no configurations are deployed to the bot. - You can’t switch the session mode while configurations are deployed on the bot. - Run configurations specify a session mode, too. - You can only deploy configurations to a bot that is in the same session mode. - You can specify the login data for the bot and the maximum number of Secure Sessions that the bot can run in parallel in the RPA Bot Configurator or in the RPA Manager. Enabling this setting in the RPA Bot Configurator limits the number of Secure Sessions, but doesn’t overwrite the same setting in RPA Manager Bot Management. - Desktop Sessions: - 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. - Secure Sessions: - The higher the number of Secure Sessions the lower the performance of the bot. Too much load can cause process slowdown or disruptions. Check the system data and the system requirements documentation to determine the maximum number of sessions that the bot can safely execute in parallel. - 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. - Do not sign in as the specified user to a computer where a bot with one licensed Secure Session is running a process. ## Next Steps 1. In the documentation, check the System Requirements. 2. On the computer where you want to run automations, where the bot is installed, check the system data: - Operating system - RAM - Terminal Server software - Login data for the bot - RPA Bot Configurator settings 3. If you want to use default session settings for the run configuration, set the bot login data and the maximum number of parallel Secure Sessions in the Bot Configurator. 4. In RPA Manager, enter the relevant data or a contact person in the description of the bot in the Bots view of the Bot Management module. If the bot should use Secure Sessions and the RPA Bot Configurator does not contain this setting, set the maximum number of parallel Secure Sessions that the bot may use via the Secure Session Assignment view. 5. When creating a run configuration in the Process Automation module of RPA Manager, keep the [general considerations](#general-considerations)in mind. ## See Also - [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) - [RPA Manager - Edit a Bot](https://docs.mulesoft.com/rpa-manager/botmanagement-manage#edit-a-bot) - [RPA Manager - Assign Sessions to Bots](https://docs.mulesoft.com/rpa-manager/botmanagement-manage#assign-sessions-to-bots) - [RPA Manager - Create a Process Run Configuration](https://docs.mulesoft.com/rpa-manager/processautomation-deploy#production-configuration) --- product: RPA --- # Security > For the full documentation index, see: https://docs.mulesoft.com/llms.txt When you automate a process, bots handle sensitive data. To ensure data security, RPA supports the following features: - Encryption of all data - [Tailored RPA permissions](https://docs.mulesoft.com/rpa-home/automation-userrolesandpermissions) - [Secure Sessions](https://docs.mulesoft.com/rpa-home/automation-security-securesessions) --- product: RPA --- # Step 1. Prerequisites for Creating an Automation > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Before you begin your automation journey, verify that you have the required tools and access: - **User Accounts and Permissions** - A user account to access RPA Manager If you don’t have a RPA Manager user, ask an administrator from your organization to set up your credentials with: - Enough privileges to access the automation modules - Enough permissions to manage the different project phases - The **Project Management** privilege - The **Builder Usage** privilege The [User Management](https://docs.mulesoft.com/rpa-manager/usermanagement-overview) module enables configuration of user privileges. - A user account to access MuleSoft Composer If you don’t have a Composer user, ask an administrator from your organization to set up your credentials. - An RPA API Key to connect MuleSoft Composer and MuleSoft RPA See [Create an API Key for a User](https://docs.mulesoft.com/rpa-manager/usermanagement-connect#create-an-api-key-for-a-user) for instructions. - A Connected App configured in Access Management to use with MuleSoft RPA 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 and configuring the Connected App. - **RPA Applications installed in your system** - RPA Builder installed and configured in your environment See [Installing and Configuring RPA Builder](https://docs.mulesoft.com/rpa-builder/latest/install-and-configure) for installation and configuration instructions. - RPA Recorder installed and configured in your environment See [Installing and Starting RPA Recorder](https://docs.mulesoft.com/rpa-recorder/latest/getting-started) for installation and configuration instructions. - RPA Bot installed and configured in your environment See [Installing RPA Bot](https://docs.mulesoft.com/rpa-bot/latest/installation) and [Configuring RPA Bot](https://docs.mulesoft.com/rpa-bot/latest/configuration) for installation and configuration instructions. - Ensure you configure the [Secure Session](https://docs.mulesoft.com/rpa-bot/latest/configuration#secure-session) in the RPA Bot Configurator tool. > [!TIP] Use two browser windows: One to read instructions and one to perform the tasks. ## Next Steps After you set up your environment with the necessary applications and credentials, you are ready to start evaluating processes for automation. Continue with [Step 2: Evaluate a process for automation](https://docs.mulesoft.com/rpa-home/automation-tutorial-evaluate) ## See Also - [User Management](https://docs.mulesoft.com/rpa-manager/usermanagement-overview) - [Hardware and Software Requirements](https://docs.mulesoft.com/rpa-home/hardware-software-requirements) --- product: RPA --- # Step 2. Evaluate a Process for Automation > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Before you start designing a process for automation, think about the following questions: - What processes are there in your company? - Who is responsible for the processes? - Which criteria are necessary and suitable to evaluate 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 to automate the processes? After gathering this information, you can use the default evaluation template or create your own evaluation criteria and templates to assess the feasibility and benefits of automating a process. ## Step 2.1: Create an Evaluation Criterion Create a new evaluation criterion to use during the process evaluation: 1. Open RPA Manager. 2. In the navigation panel, click the **Process Evaluation** module. 3. Open the **Evaluation Criteria** view. 4. Click **Create Benefit**. - In the **Name** field, write: `Concurrency` - Click the **Exclude** checkbox - In the **Definition Gradation 1** field, write: `Yes, allows parallel executions` - In the **Definition Gradation 2** field, write: `No, only one execution at a time` 5. Click **Save**. ## Step 2.2: Create an Evaluation Template After you create new criteria for evaluation, create a new evaluation template that includes that criteria: 1. In the navigation panel, click the **Process Evaluation** module. 2. Open the **Evaluation Templates** view. 3. Click **Create**. - In the **Name** field, write: `My custom template` - Scroll down and verify that the **Exclude MuleSoft default evaluation criteria** checkbox is unselected - Inside the **Available qualifiers** section, click the **Move All** (→→) button - Inside the **Available benefits** section, click the **Move All** (→→) button Note that the **Concurrency** criterion created in the previous step appears in this section. 4. Click **Save**. ## Step 2.3: Create a Process Evaluation When creating a process evaluation, you can select the default evaluation template or a custom template you created. To create a new process evaluation using the custom template created in the previous step: 1. In the navigation panel, click the **Process Evaluation** module. 2. Open the **Process Evaluation** view. 3. Click **Create**. - In the **Name** field, write: `MuleSoft newsletter sign-up` - Click the **Template** dropdown and select **My custom template** 4. Click **OK**. After confirming these details, you are redirected to the evaluation view where you specify the **Costs**, **Qualifiers** and **Benefits** for this process: 1. Set the **Manual process execution time** field to `00:10:00`. 2. In the **Benefits** section, set the **Concurrency** slider to **No, only one execution at a time**. 3. Click **Save**. ## Step 2.4: Submit the Process to Start an Automation Project After you finish evaluating a process for automation and confirm that it is suitable, submit the process to the next step to start an automation project: 1. In the navigation panel, click the **Process Evaluation** module. 2. Open the **Process Evaluation** view. 3. Search for the **MuleSoft newsletter sign-up** project in the process list and click the **Approve** (![The approve icon](/mulesoft/current/en-us/rpa-home/_images/approve-icon.png)) button. 4. Select the **Project Manager** option. 5. In the **Project Manager** dropdown menu, select your username. If your username does not show in the dropdown menu, ensure your user has the **Project Management** privilege. 6. Click **OK**. ## Next Steps After the process evaluation finishes and the process is approved, the assigned Project Manager or Center of Excellence can start the automation project. Continue with [Step 3: Create the automation project](https://docs.mulesoft.com/rpa-home/automation-tutorial-create) ## 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) --- product: RPA --- # Step 3. Create the Automation Project > For the full documentation index, see: https://docs.mulesoft.com/llms.txt After evaluating and approving a process for automation, create an automation project from the approved process proposal and assign it a category. You can either use a category that exists in your organization or you can create a new one. ## Step 3.1: Create a Category To create a category, follow these steps: 1. In the navigation panel of RPA Manager, click the **Process Automation** module. 2. Open the **Process Management** view. 3. Click **Create**. 4. In the **Name** field, write `Web Automations`. 5. Click **OK**. ## Step 3.2: Create the Automation Project After you create a category, follow these steps to create your automation project: 1. In the navigation panel, click the **My RPA** module. 2. Open **My Backlog**. 3. Search for the **MuleSoft newsletter sign-up** project in the process list and click the **Start automation** (![The approve icon](/mulesoft/current/en-us/rpa-home/_images/start-automation-icon.png)) button. 4. Provide the necessary information for the project: - In **Process name**, write `MuleSoft newsletter sign-up`. - In **User**, select **Design**, **Build**, **Test**, and **Production** to ensure your user has access to all phases of this automation project. - In **Category**, select the **Web Automations** category, created in the previous step. - Deselect **Use Process Board**. 5. Click **Save** ## Next Steps Now that you’ve created an automation project, it’s time to move to the design phase, in which you create the BPMN diagram for the process. Continue with [Step 4: Design the BPMN diagram for the automation](https://docs.mulesoft.com/rpa-home/automation-tutorial-design) ## See Also - [Starting Automation of Approved Processes](https://docs.mulesoft.com/rpa-manager/myrpa-start) --- product: RPA --- # Step 4. Design the BPMN Diagram for the Automation > For the full documentation index, see: https://docs.mulesoft.com/llms.txt After creating a new automation project, you can start designing the BPMN diagram for the process to automate. You can create the diagram manually or by using the RPA Recorder, which records your actions, creates each corresponding step in the diagram, and generates the action steps based on your mouse and keyboard interactions. ## Step 4.1: Open the Project for Editing and Start RPA Recorder Follow these steps to edit your process BPMN diagram using RPA Recorder: 1. In the navigation panel of RPA Manager, click the **My RPA** module. 2. Click **My Backlog**. 3. Search for the **MuleSoft newsletter sign-up** project in the process list and click the **Open process** (![The open process icon](/mulesoft/current/en-us/rpa-home/_images/open-process.png)) button. 4. In the **Automation** panel, click the **Record BPMN** (![The record process icon](/mulesoft/current/en-us/rpa-home/_images/record-process.png)) button. ![The Record BPMN button inside the Automation Panel](/mulesoft/current/en-us/rpa-home/_images/automation-panel-recording.png) If you see a pop-up window asking for permission, select the checkbox to allow RPA Manager to open RPA Recorder and click **Open**. 5. Provide your RPA Manager user account password and click **Login**. ## Step 4.2: Record Activity Steps with RPA Recorder After you log in to RPA Recorder, you can start the activity recording process. In this process, you alternate between adding activity steps in RPA Recorder and performing the actual actions in your computer that you want to record and include in the BPMN diagram. This procedure continues until you perform the last action and finish the recording. ### Before you Begin Recording the Process To prevent issues during the tutorial, before you start with the recording steps: 1. Navigate to [https://blogs.mulesoft.com/signup-for-our-newsletter/](https://blogs.mulesoft.com/signup-for-our-newsletter/). 2. If a Cookie Consent pop-up shows, accept the cookies. Performing this action prevents the pop-up from showing during the next steps of the automation tutorial, which could prevent you from finishing the process successfully. ### Start the Recording To record actions with RPA Recorder and create the BPMN diagram, follow these steps: 1. In RPA Recorder, click the **Start Recording** (![The start recording icon](/mulesoft/current/en-us/rpa-home/_images/start-recording.png)) button and add the first activity step: 1. In the **activity name** field, write `Open newsletter sign-up page`. 2. In the drop down menu, select **Web task**. 3. Click **Add**. 4. In the browser session that opens, navigate to `https://blogs.mulesoft.com/signup-for-our-newsletter/`. 2. In the RPA Recorder panel, click the **Add activity** (![The add activity icon](/mulesoft/current/en-us/rpa-home/_images/add-activity.png)) button and add a new activity step: ![The recorder panel of RPA Recorder](/mulesoft/current/en-us/rpa-home/_images/rpa-recorder-panel.png) 1. Write `Sign-up for newsletter` in the activity name field. 2. In the drop down menu, select **Web task**. 3. Select the **Continue with already existing web session** checkbox. This option creates the `generatedWebSession1` Action Parameter, which enables you to continue using the same web session in subsequent Web tasks. You can also reference this parameter when you create new action steps during the build phase in RPA Builder. 4. Click **Add** 5. In the sign-up page, provide an email address of your choice and click **Sign up**. 3. In the RPA Recorder panel, click the **Stop recording** (![The stop recording icon](/mulesoft/current/en-us/rpa-home/_images/stop-recording.png)) button. 4. Confirm that RPA Recorder generates a BPMN diagram as follows: ![A BPMN diagram with two steps](/mulesoft/current/en-us/rpa-home/_images/newsletter-bpmn-diagram.png) After you finish the recording process, upload the newly-created BPMN diagram to RPA Manager to update the model of your current automation project. ## Step 4.3: Upload the BPMN Diagram to RPA Manager Follow these steps to upload the BPMN diagram created with RPA Recorder to RPA Manager: 1. In **RPA Recorder**, click the **Edit, Merge and Upload Recordings** (![The edit, merge and upload icon](/mulesoft/current/en-us/rpa-home/_images/edit.png)) button. 2. In the **Automation** panel, click the **Save** (![The save icon](/mulesoft/current/en-us/rpa-home/_images/save.png)) button. 3. Write `MuleSoft Newsletter` in the **Process name** field and click **Save**. 4. Click the **Upload to server** (![The upload to server icon](/mulesoft/current/en-us/rpa-home/_images/upload-to-server.png)) button. 5. In the confirmation window that shows after the upload finishes successfully, Click **OK**. ![The BPMN upload confirmation message](/mulesoft/current/en-us/rpa-home/_images/bpmn-upload-successful.png) 6. Close the **RPA Recording Editor** window. 7. Close the **RPA Recorder** window. 8. Return to RPA Manager and refresh the browser page. 9. Click **Publish**. ![The Publish button](/mulesoft/current/en-us/rpa-home/_images/publish-button.png) 10. Click the confirmation checkbox and then click **Release to Build**. ## Next Steps Now that you’ve created a BPMN diagram for your automation project and published it, it’s time to move to the build phase, in which you can edit the diagram and specify the actions to execute for each action step. Continue with [Step 5: Build the automation from the BPMN diagram](https://docs.mulesoft.com/rpa-home/automation-tutorial-build) ## See Also - [Installing and Starting RPA Recorder](https://docs.mulesoft.com/rpa-recorder/latest/getting-started) - [Process Recording Editor](https://docs.mulesoft.com/rpa-recorder/latest/process-rec-editor) - [Design a Process Model](https://docs.mulesoft.com/rpa-manager/processautomation-develop) --- product: RPA --- # Step 5: Build the Automation from the BPMN diagram > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Now that the BPMN diagram for the process to automate is ready, it’s time to use RPA Builder to specify each of the actions the RPA bot executes when it runs this process. Because you used RPA Recorder to create the diagram, each existing task already contains the action steps for the bot to execute. During this step, you add a new task to confirm that the sign-up process was successful by reading the confirmation text on the screen. Before you start defining the actions, configure RPA Builder to connect with your RPA Manager repository so you can import the designs and re-upload them after the build phase is finished. ## Step 5.1: Connect to the RPA Manager Repository To connect RPA Builder with your RPA Manager repository: 1. Open RPA Builder. 2. If it is your first time opening RPA Builder, the connection dialog shows automatically. If the dialog does not show: - In the top menu bar, go to **Options** > **Repository**. 3. Provide the required information: - **RPA Manager Address:** The URL of the RPA Manager instance you want to connect to For example: myorganization.rpa.mulesoft.com. - **User Name:** Your RPA Manager account user name - **Password:** Your RPA Manager account password 4. Click **Test Connection** - If the test fails, ensure the provided information is correct and try again - If the test succeeds, click **OK** to close the message 5. Click **OK**. ## Step 5.2: Import the Project From the RPA Manager Repository To import the project from the RPA Manager repository: 1. In RPA Builder, click the **Repository Explorer** panel. ![The Repository Explorer panel](/mulesoft/current/en-us/rpa-home/_images/repository-explorer-panel.png) If this panel is not visible, go to the top menu bar and click **View** > **Show Repository Explorer**. 2. Find your project under the **Process** column and double-click it. ## Step 5.3: Edit the Project and Add an Action Step To add a new action step into your automation project: 1. In RPA Builder, drag the **Create bot task** element (![The Create bot task icon](/mulesoft/current/en-us/rpa-home/_images/create-bot-task-icon.png)) from the BPMN editor into your process flow, after the **Sign-up to newsletter** task. ![A BPMN diagram with three steps](/mulesoft/current/en-us/rpa-home/_images/add-bot-task-to-process.png) If the diagram does not automatically connect the new task, re-arrange the arrows to ensure that the new task comes after the **Sign-up to newsletter** task and connects to the **End recording** element. 2. In the new task element, write `Confirm sign-up`. 3. Double-click the **Confirm sign-up** task to open the workflow in edit mode. This action opens the task for editing in the **Workbench** panel. 4. In the **Workflow Initialization** section, double-click **Activity Parameters**. ![The workflow Initialization section](/mulesoft/current/en-us/rpa-home/_images/activity-parameters.png) 5. Double-click the **generatedWebSession1** parameter to move it to the **Used in this Workflow** session. Alternatively, you can use the arrow buttons to move this parameter. > [!TIP] RPA Recorder generated this Action Parameter when you selected the **Continue with > already existing web session** option while creating Web tasks during step 4.2 of this > tutorial. 6. Click **OK**. 7. Click the **Toolbox** panel. If this panel is not visible, in the top menu bar, go to **View** > **Show Toolbox**. 8. From the **Web Automation** section, drag a **Web Session(Chrome)** element into the **Activity Workflow** section. ![The activity workflow with a Web Session element](/mulesoft/current/en-us/rpa-home/_images/drag-web-session.png) If you have a different web browser configured as the default, ensure that you use the corresponding **Web session** element that matches your default browser. 9. Double-click the **Web Session** element you just added in the **Activity Workflow**. 10. In **Reuse Web Session**, click the **Web Session id** drop-down menu and select **Activity Parameters** > **generatedWebSession1**. ![The Web Session Wizard showing the generatedWebSession1 parameter selected](/mulesoft/current/en-us/rpa-home/_images/web-session-configuration.png) 11. Click **OK**. 12. In the **Toolbox** panel, search for the **Text Recognition (OCR)** section and drag an **Intelligent OCR(2020)** element to the **Web Session** inside the **Activity Workflow**. ![The Activity Workflow section with an Intelligent OCR (2020) element](/mulesoft/current/en-us/rpa-home/_images/activity-workflow-ocr.png) 13. Double-click the **Intelligent OC (2020)** element. 14. In **Search Mode**, select **Text Comparison**. 15. In **Search Text**, write `"Thanks\s*for\s*signing\s*up"`. This regular expression matches the text even if it spans over multiple lines. 16. Click **OK**. 17. In the top menu bar, click **File** > **Save Project**. After you add the text recognition task and save the project, perform a local test of your process. ## Step 5.4: Perform a Local Test of the Process To perform a local test of the created process: 1. Ensure your project is open for edit. 2. In the BPMN editor, click the **Run Process** (![The Run process icon](/mulesoft/current/en-us/rpa-home/_images/run-process.png)) button. This action starts the execution of the process and shows the **Test run information** window: ![The test run information in RPA Builder](/mulesoft/current/en-us/rpa-home/_images/builder-test-run-information.png) As the tasks start executing, notice that new entries appear in this window and show a **Task execution succeeded** (![Task execution succeeded icon](/mulesoft/current/en-us/rpa-home/_images/task-execution-icon.png)) icon in the **Run state** column when they finish. > [!IMPORTANT] Because the RPA Bot conducts the test using your current Desktop session, do not > interact with any elements in the screen until the test finishes. Otherwise, the test could > fail. 3. Click **Close** to close the **Test run information** window and return to RPA Builder. After confirming that the test is successful, upload the project to RPA Manager. ## Step 5.5: Upload the Project to RPA Manager To upload the updated automation project to RPA Manager: 1. In RPA Builder, go to **File** > **Upload Project**. 2. Provide a description in the **Changes:** field and click **Upload**. 3. Confirm that the upload was successful and click **OK**. 4. Close RPA Builder. ## Next Steps You’ve modified the automation project, added a new task to the process, and verified that the automated process works as expected. Now, it is time to create a test plan in RPA Manager and execute the tests for this project. Continue with [Step 6: Test the automation](https://docs.mulesoft.com/rpa-home/automation-tutorial-test) ## See Also - [RPA Builder Overview](https://docs.mulesoft.com/rpa-builder/latest/) - [Installing and Configuring RPA Builder](https://docs.mulesoft.com/rpa-builder/latest/install-and-configure) - [Toolbox Reference](https://docs.mulesoft.com/rpa-builder/latest/toolbox) --- product: RPA --- # Step 6: Test the Automation > For the full documentation index, see: https://docs.mulesoft.com/llms.txt You finished the build phase and the automation project is ready to move to the testing phase, where you create a test plan to execute the necessary tests on your automation project. You can create multiple configurations to test your process using different activity parameters and to test for the completion of user tasks. For this tutorial, create a simple test that confirms the proper deployment and execution of the automated process. ## Step 6.1: Create a Test Plan To create a test plan, open RPA Manager and follow these steps: 1. In RPA Manager, go to **My RPA** > **My Processes**. 2. Click the **MuleSoft newsletter sign-up** project. 3. Click **Publish(Test)**. 4. Click the confirmation checkbox and then click **Release to Test**. 5. Inside **Test plans**, click the **Create new test plan** button. 6. In the **Test plan name** field, write **My Test** and click **Next**. 7. Click **Next** (this process has no activity parameters). 8. Click **Next** (this process has no user tasks). 9. Select **Run test in Secure Session**, check **Enable Taskbar (Start menu, taskbar buttons)**, and click **Next**. Ensure you followed the steps to configure the [Secure Session](https://docs.mulesoft.com/rpa-bot/latest/configuration#secure-session). Otherwise, the bot fails to run. 10. Select any of your configured bots and click **Finish** ## Step 6.2: Run the Test, Examine the Results, and Publish to Production To run the test plan and see the results, follow these steps: 1. In the **Test plans** panel, click **Start tests**. 2. In the **Select Configuration to deploy** window, select your test plan and click **Execute**. ![The Select Configuration to deploy window](/mulesoft/current/en-us/rpa-home/_images/test-config-deploy.png) 3. In the **Test Results** panel, click **Update**. If there are no results, wait a few minutes for the test to end and click **Update** again. 4. Verify that there is a new entry for the bot showing **1** in the **Success** column. ![The Test Results window showing a successful execution](/mulesoft/current/en-us/rpa-home/_images/bot-test-success.png) 5. After the test finishes, click **Publish (Production)**. 6. Click the confirmation checkbox and then click **Release to Production**. ## Next Steps You created a test plan that executes the automation to ensure that the process runs successfully. Then, you finished testing the process and released it to the production phase. Now, it is time to publish the process to Anypoint Exchange by creating an invocable run configuration for this process. Continue with [Step 7: Publish the Automation to Exchange](https://docs.mulesoft.com/rpa-home/automation-tutorial-deploy) ## See Also - [Installing RPA Bot](https://docs.mulesoft.com/rpa-bot/latest/installation) - [Configuring RPA Bot](https://docs.mulesoft.com/rpa-bot/latest/configuration) --- product: RPA --- # Step 7: Publish the Automation to Exchange > For the full documentation index, see: https://docs.mulesoft.com/llms.txt After finishing the testing phase, the process moves to the production phase. It is time to create an invocable run configuration, which publishes the process to Anypoint Exchange and enables MuleSoft Composer to trigger the execution of this process. Before you can create an invocable run configuration, ensure that you configured your Anypoint Platform settings in RPA Manager. See [Configure Anypoint Platform Credentials](https://docs.mulesoft.com/rpa-manager/organizationmanagement-settings#configure-anypoint-credentials) for instructions. ## Step 7.1: Create an Invocable Run Configuration To create an invocable run configuration for a process: 1. In RPA Manager, go to **My RPA** > **My Processes**. 2. Click the **MuleSoft newsletter sign-up** project. 3. In the **Production configurations** panel, click **Create invocable run configuration**. 4. Specify a **Configuration name**, for example, **Invocable RPA Process**, and click **Next**. 5. Click **Next** (this process has no activity parameters). 6. Click **Next** (this test has no user tasks). 7. Select **Run in Secure Session** and click **Next**. 8. Select the bot to carry out the execution and click **Save**. 9. In the **Production configurations** table, click **Publish** > **Publish to Anypoint**. ## Next Steps Now that you’ve published the process to Exchange, it is time to create a Composer flow that triggers the execution of this RPA process. Continue with [Step 8: Integrate the Automation with Composer Flows](https://docs.mulesoft.com/rpa-home/automation-tutorial-composer) ## See Also [Deploying Automations](https://docs.mulesoft.com/rpa-manager/processautomation-deploy) --- product: RPA --- # Step 8: Integrate the Automation with Composer Flows > For the full documentation index, see: https://docs.mulesoft.com/llms.txt After successfully publishing the process automation, you can connect your MuleSoft RPA account with MuleSoft Composer and start the automated process from a Composer flow. During this step, you create a new MuleSoft Composer flow, configure a trigger, connect your Composer account with your MuleSoft RPA account, and start the execution of an RPA Process. Different triggers can start a Composer flow, including interactions with Salesforce and other systems. This tutorial uses the Scheduler event because it is a simple way to start the execution of the flow without configuring connections to other systems. ## Step 8.1: Create a New Composer Flow To create a new Composer flow: 1. Open MuleSoft Composer. If you don’t know your organization’s MuleSoft Composer instance URL, contact your organization administrator. 2. In the menu bar, click **Composer Flows**. 3. Click **New Flow**. 4. Click the edit button next to **Untitled Flow** and provide a name for this flow, for example, **Trigger RPA Automation**. ## Step 8.2: Add a Start Event for the Flow Every Composer flow needs a start event to trigger the execution. To add a starting action: 1. In the **What Should Start This Flow?** window, click **Scheduler**. The **Scheduler** triggers the flow execution on a configured schedule, such as every 15 minutes. ![The action card showing options to configure the flow trigger in Composer](/mulesoft/current/en-us/rpa-home/_images/composer-trigger.png) 2. Leave the **Every** field set to the default value of 15 minutes. ## Step 8.3: Connect Composer with MuleSoft RPA Before you can call an RPA process from Composer, you must configure the connection between the two systems. To configure the connection between Composer and MuleSoft RPA: 1. Click **Add** (![The Add Event button](/mulesoft/current/en-us/rpa-home/_images/add-icon.png)) next to the Scheduler event you previously created. 2. Select **System Action**. 3. Select **MuleSoft RPA**. Because this is the first time you are interacting with a new system (MuleSoft RPA), Composer opens the connection panel. 4. Provide the following details to connect with your MuleSoft RPA account: - **Connection Display Name**: A name for the connection, for example, **My RPA Account**. - **RPA API URL**: The RPA API URL of your RPA Manager instance. Construct this URL by appending `/rpa/api/v1` to the URL of RPA Manager, for example: `[https://.rpa.mulesoft.com/rpa/api/v1](https://\.rpa.mulesoft.com/rpa/api/v1)`. - **User API Key**: An API key to connect MuleSoft RPA with Composer. Use the same API key you created as part of the tutorial prerequisites. You can create a new user API key by following the steps in [Create an API Key for a User](https://docs.mulesoft.com/rpa-manager/usermanagement-connect#create-an-api-key-for-a-user). 5. Click **Connect**. If you see an error message while creating the connection, verify the configuration details and try again. ## Step 8.4: Add an Action to Invoke the RPA Process After successfully configuring the connection to MuleSoft RPA, follow these steps to invoke the RPA process: 1. In the MuleSoft RPA action card, select **Action** > **Invoke RPA Process**. 2. In **RPA Process**, select the invocable run configuration that you created in [Step 7.1: Create an Invocable Run Configuration](https://docs.mulesoft.com/rpa-home/automation-tutorial-deploy#Step-7-1). 3. In **Output**, select **Use response in this flow**. 4. Click **Save**. 5. Click **Test** to test the Composer flow, including the call to the RPA process. After the test finishes successfully, you see additional details in the RPA process card, such as **RPA Execution ID** and **RPA Execution Status**, which shows `SUCCEED` to confirm the proper execution of the RPA process. ## Next Steps Now that you created a Composer flow that triggers the execution of an RPA process, it’s time to monitor the deployment. Continue with [Step 9: Monitor the Automation](https://docs.mulesoft.com/rpa-home/automation-tutorial-monitor) ## See Also - [Building Process Automation with MuleSoft Composer](https://docs.mulesoft.com/composer/ms_composer_overview) - [RPA Overview](https://docs.mulesoft.com/rpa-home/) --- product: RPA --- # Step 9: Monitor the Automation > For the full documentation index, see: https://docs.mulesoft.com/llms.txt After publishing the process to Exchange and executing it from Composer, use the Process Monitoring module to see a summary of the deployed bots and the process executions. ## Step 9.1: See a Live Stream of the Deployed Process To see a live stream of the deployed process: 1. In Composer, open the flow you created in [Step 8.1: Create a New Composer Flow](https://docs.mulesoft.com/rpa-home/automation-tutorial-composer#step-8-1) for editing and click **Test**. 2. Switch to RPA Manager and open the **Process Monitoring** module. 3. Click on **Process Streaming**. 4. Refresh the page and click **Show process streams**. If the button is disabled and shows **No sessions running**, it means the process has not started yet. In that case, refresh the page and try again. 5. Click **On** to enable showing screen captures of this process. ![The process streaming window showing a process running](/mulesoft/current/en-us/rpa-home/_images/process-streaming.png) The **Process Streaming** section shows a window for each run configuration that is currently executing. The stream consists of a sequence of images that the RPA bot records during process execution. > [!TIP] If this section shows empty, it is possible that the execution of the process has already > finished, meaning that it is not running now and it cannot provide a stream of the process. ## Step 9.2: Monitor the Deployed Process To see the active bots and the deployed processes: 1. In RPA Manager, open the **Process Monitoring** module. 2. Click on **Bot State and Operation**. The **Bot State and Operation** section shows a list of your configured bots and the current process executions. ![The Bot state and operation window showing process execution results](/mulesoft/current/en-us/rpa-home/_images/process-monitor.png) Note that the **Work done** column shows **1**, which confirms that the execution of the process finished one time. ## Next Steps At this point you finished creating a Composer Flow that calls an automated process that you previously created and published to Exchange using MuleSoft RPA. You can use this project as a template or starting point to develop further automation projects and integrations between MuleSoft Composer and RPA. ## See Also - [Process Monitoring](https://docs.mulesoft.com/rpa-manager/processmonitoring-overview) --- product: RPA --- # Tutorial: Create an Automation from Start to Finish > For the full documentation index, see: https://docs.mulesoft.com/llms.txt MuleSoft Robotic Process Automation (RPA) enables you to automate workflows that contain time-consuming manual tasks and integrate them with your MuleSoft Composer flows. During this tutorial, you create a simple automation project that accesses the MuleSoft website, subscribes to the newsletter, uses optical character recognition (OCR) to confirm that the process finishes successfully, and then you configure a Composer flow to execute the automated process. Follow these steps to complete the end-to-end automation journey: - [Step 1. Prerequisites for Creating an Automation](https://docs.mulesoft.com/rpa-home/automation-tutorial-prerequisites) - [Step 2. Evaluate a Process for Automation](https://docs.mulesoft.com/rpa-home/automation-tutorial-evaluate) - [Step 3. Create the Automation Project](https://docs.mulesoft.com/rpa-home/automation-tutorial-create) - [Step 4. Design the BPMN Diagram for the Automation](https://docs.mulesoft.com/rpa-home/automation-tutorial-design) - [Step 5: Build the Automation from the BPMN diagram](https://docs.mulesoft.com/rpa-home/automation-tutorial-build) - [Step 6: Test the Automation](https://docs.mulesoft.com/rpa-home/automation-tutorial-test) - [Step 7: Publish the Automation to Exchange](https://docs.mulesoft.com/rpa-home/automation-tutorial-deploy) - [Step 8: Integrate the Automation with Composer Flows](https://docs.mulesoft.com/rpa-home/automation-tutorial-composer) - [Step 9: Monitor the Automation](https://docs.mulesoft.com/rpa-home/automation-tutorial-monitor) After you’ve experienced the end-to-end journey, use the model you created to plan your next automation projects. ## See Also - [RPA Overview](https://docs.mulesoft.com/rpa-home/) --- product: RPA --- # Use Case: Extracting Data from a Legacy System > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Extracting data from legacy systems is a common use case for RPA. Companies use legacy applications because they still work, they contain data crucial for daily work, and it’s complicated and expensive to replace them. Companies also work with newer applications that use the same data. If the legacy application offers no way to transfer the data automatically, employees must copy and paste data sets manually. This takes up a lot of time and is error-prone and tedious. Robots can extract the data faster and more securely and don’t get bored. Examples of data extraction use cases are: - Retrieve an order ID from a legacy system to get a tracking number from an order tracking application. - Retrieve data from a legacy AMS to create a CRM report in Salesforce. (Check out this [Accelerator](https://anypoint.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-financial-services/minor/1.10/pages/604-0mq/Use%20case%207%20-%20Unlock%20AMS%20through%20hyperautomation%20for%20insurance%20brokers/)!) - Migrate all of the data of a legacy application to a state-of-the-art application. This example illustrates the following tasks: - Copy the contents from a PDF file to a text file. - Compare strings. - Copy a substring from a text file. - Find text on a screen using optical character recognition (OCR). - Interact with a screen using mouse actions and keystrokes. - Use activity parameters to transfer data and to determine which path to follow in the model. ## Example Scenario Mythical University orders a travel package for a field excursion. As an accountant, you receive an email and save the attached order confirmation to your computer. An order confirmation from your travel agency Wonderlust Travel typically looks like this: ![Letter containing a logo, headers, text, and tables. The order ID is contained in a table in a header in the middle of the page. The label says 'Order ID'.](/mulesoft/current/en-us/rpa-home/_images/usecase-1-wonderlusttravels-orderconfirmation-pdf.png) You need to refer the corresponding tracking number in your payment, so you search for the order ID in the order tracking system. Unfortunately, your order tracking system is old and can only be accessed by typing in and reading from a terminal screen: ![Legacy order tracking system showing green glowing text in a terminal. Above a list of orders, there is an entry field for the order ID labeled 'Order-ID' and a button labeled 'Search' next to it.](/mulesoft/current/en-us/rpa-home/_images/as400ordertrackingscreen.png) You click the search field, enter the order ID, and click 'Search'. ![Legacy order tracking system shows no search results.](/mulesoft/current/en-us/rpa-home/_images/as400ordertrackingscreen-searchresult-ordernotfound.png) The list of orders is now empty, which means that either the order isn’t there or you mistyped the number. Let’s assume that the latter is the case. You try again and the list shows the corresponding entry: ![Legacy order tracking system shows one search result.](/mulesoft/current/en-us/rpa-home/_images/as400ordertrackingscreen-searchresult-orderfound.png) Now you can copy the tracking number and reference it in your payment. Because the scientists at Mythical University travel frequently, you repeat this tedious, error-prone, and risky process many times a day. You decide to get a bot to do this work. This example shows how to get the order ID and tracking number from the legacy system automatically. You can use a PDF and MuleSoft RPA as an invocable automation step to do this. The example doesn’t include downloading the attachment and any steps afterward. ## Design a Model of the Process in RPA Manager In RPA Manager, you open a new project and design a model of the process using the [Business Process Model and Notation (BPMN) standard](https://www.omg.org/spec/BPMN/2.0/). The model contains the following activities: 1. Extract the order ID from the order confirmation. 2. Extract the corresponding tracking number from the legacy system. 3. Return either the tracking number or information that it couldn’t be found. ![In the model flow, activities one and two are sequential. Depending on whether the order id is found, an exclusive gateway branches the flow to the third activity.](/mulesoft/current/en-us/rpa-home/_images/extractrackingnumber-bpmn.png) You include the user tasks in the third activity for illustration and testing purposes and can later replace them with steps to prepare the returned data for processing in another automation step. After you finish the first draft of the model, you move the project to the build phase. Then, you open the project in RPA Builder to implement the workflows for the bot activities. ## Create Activity Parameters in RPA Builder The process uses variables to store and route data. You define these _Activity Parameters_ in RPA Builder. For your process, you need three Activity Parameters: - order\_id - is an alphanumeric variable - stores the order ID found in the order confirmation - is returned at the end of the process - tracking\_no - is an alphanumeric variable - stores the corresponding tracking number found in the order tracker application - is returned at the end of the process if it is found - is\_order\_id\_found - is a boolean variable - is set to true if the order id is found in the order tracking system - routes the process flow through the gateway accordingly ![The Activity Parameter tab in the Business Process Initialization window on the modelling workbench in RPA Builder shows the three parameters of the process.](/mulesoft/current/en-us/rpa-home/_images/activityparameters.png) To use Activity Parameters in a Workflow, move them from **Available Parameters** to **Used in this Workflow** in the **Activity Parameters** action step of the **Workflow Initialization** section. The parameters retain the values set in previous workflows throughout the process. ![](/mulesoft/current/en-us/rpa-home/_images/usecase-legacysystem-useactivityparameters.png) ## Implement the Activities The next topics about implementing activities as _Workflows_ on the next pages follow the model flow: 1. [Finding Information in a PDF](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction-extractfrompdf) 2. [Interacting with a Screen of a Legacy Application](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction-extractfromscreen) 3. [Reacting to Different Outcomes](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction-reacttodifferentoutcomes) 4. [Returning Values](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction-returnvalues) ## See Also - [Tutorial: Create an Automation from Start to Finish](https://docs.mulesoft.com/rpa-home/automation-tutorial-introduction) - [Create an RPA Project](https://docs.mulesoft.com/rpa-home/create-rpa-project) - [RPA Manager: Developing Automations](https://docs.mulesoft.com/rpa-manager/processautomation-develop) - [RPA Builder: Activity Parameters](https://docs.mulesoft.com/rpa-builder/latest/toolbox-variable-handling-activity-parameters) [Finding Information in a PDF](https://docs.mulesoft.com/rpa-home/automation-usecase-legacysystemdataextraction-extractfrompdf) --- product: RPA --- # User Roles and Permissions > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Automating a process takes an interdisciplinary team. Knowledge, skills, and responsibilities are distributed over several different persons. Not everyone can do anything or should know anything for security reasons. These restrictions are implemented as user roles and permissions in RPA Manager. ## User Permission Scopes Permissions determine what users of the RPA products can see and do: - See and open - a module - a view - an object and its data - Perform an action in a view - Create objects - Edit data - Transition objects - Take decisions - Use products - Analyze data - Monitor - usage - performance - Report results ## User Permissions Types Permissions have different scopes and purposes. They can be combined.
Permission TypeScopeExample

Privileges / RPA (Deprecated) Permissions

  • Predefined fine-granular permissions to view and process data.

  • Can be compiled to individual roles.

  • For some tasks users need individual permissions or assignments additional to privileges.

  • Are deprecated after the migration of RPA Manager to Anypoint Access Management

You can guess the purpose of these example privileges from their name:

  • Process Automation Open

  • Project Management

  • Process Evaluation Approval to a Project Manager

  • Open Evaluation Templates

  • Builder Usage

  • Create Global Variables

  • Edit Evaluation Templates

  • Change Project Manager

  • Upcoming Process Changes Administration

RPA Permissions

  • Role-like permissions

  • For some tasks users need individual permissions or assignments additional to permissions.

You can guess the purpose of these example privileges from their name:

  • RPA Automations Designer

  • RPA Performance Analyzer

Roles

  • Combination of privileges.

  • Users can have more than one role.

  • Are deprecated after the migration of RPA Manager to Anypoint Access Management

The role Business User could include the privileges Activity Library Administration, Activity Library Open, Dashboard Open, Process Automation Open, and Process Recording.

Assignments

  • Permissions valid for a phase in the lifecycle of a project.

  • Enable a user to assume responsibility for a project.

  • Assignments are combined with privileges.

  • A user who is part of a user group marked as Center of Excellence also needs the privilege Process Create to start the automation of a process.

  • RPA developers need the privilege Process Automation Open to see which newly designed processes they can build. They need the privilege Builder Usage and the permission for the build phase as a team member to work on the implementation of the process in RPA Builder. If senior RPA developers need to check the build first before running tests in RPA Manager, the project manager can assign them the advanced permission Release to Test.

Individual Permission

  • Permissions for security relevant process elements.

  • Granted only to selected users on element creation.

Credentials can only be used by users selected on creation.

Transferred Permission

  • API Keys are assigned to users whose identity and permission set is used to complete tasks via REST API.

  • API Keys have an expiration date.

API Keys are needed when an RPA Manager Invocable Configuration is included into a Composer Flow.

## See Also - [RPA Manager Overview](https://docs.mulesoft.com/rpa-manager/) - [Assign Privileges to a User](https://docs.mulesoft.com/rpa-manager/usermanagement-manage#assign-privileges-to-a-user) - [List of Privileges by Module](https://docs.mulesoft.com/rpa-home/automation-userrolesandpermissions-privilegesbymodule) - [Designate User Groups As Centers of Excellence](https://docs.mulesoft.com/rpa-manager/usermanagement-assemble#designate-user-groups-as-centers-of-excellence) - [Assign Permissions to a Process Team Member](https://docs.mulesoft.com/rpa-manager/processautomation-manage#projectdata-processteam) - [Manage Credentials](https://docs.mulesoft.com/rpa-manager/processautomation-prepare-deployment-credential) - [Create an API key for a User](https://docs.mulesoft.com/rpa-manager/usermanagement-connect#create-an-api-key-for-a-user). - [Anypoint Access Management](https://docs.mulesoft.com/access-management/)