---
schema_version: "1"
id: 9c3d64c5f0b9638f5486b9859b0908a19bc5b0f96449860e661a44037cf9ec45
title: Manage Applications
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/rpa-manager/processautomation-prepare-project-application.md
canonical_url: https://docs.mulesoft.com/rpa-manager/processautomation-prepare-project-application
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 930ad93bf91ac36e5e3cc58521775d64f682e2642ffdf8b3364752f4a23f6719
description: MuleSoft Documentation Site
latest: true
---
---
product: RPA Manager
---

# Manage Applications

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Process applications are third-party application installations that business experts use to execute
a process.

Manage a list of all applications and their downtimes.

Create a new entry for each instance of an application, for example
`FinWiz - Mythical University - Computer 1 - Tokyo` and
`FinWiz - Mythical University - Computer 42 - San Francisco`.

Applications are not available during downtimes or while deactivated.

To avoid confusion, append the name of the time zone to the name of the application or the downtime.
For example, name an application `Words - Tokyo` and a downtime `Electrical Power Outage Tokyo`.

In the **Process Management** view, a member of the project team
[assigns required applications to a process](https://docs.mulesoft.com/rpa-manager/myrpa-start#required-process-applications) at process
automation creation or phase transition.

In the **Bot Management** module, an administrator
[assigns required applications to bots](https://docs.mulesoft.com/rpa-manager/botmanagement-manage#bot-assign-servicetimes-applications)
that can access them.

A member of the process team can deploy a process on a bot that has assigned the required
applications. If an application becomes unavailable, the bot completes running processes using that
application and restarts the processes when the downtime or deactivation period has ended.

## Before You Begin

- Ask an organization administrator in Access Management to assign you the required permissions:

  <table><colgroup><col> <col> <col></colgroup><thead><tr><th>Action</th><th>RPA Permission</th><th>Deprecated RPA Permission</th></tr></thead><tbody><tr><td><p>Open the <strong>Process Automation</strong> module.</p></td><td><p>RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Administrator</p></td><td><p>Process Automation Open</p></td></tr><tr><td><p>Create and change process applications.</p></td><td><p>RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Bots Manager, RPA Administrator</p></td><td><p>Application Create, Application Edit</p></td></tr><tr><td><p>Delete process applications.</p></td><td><p>RPA Automations Manager, RPA Bots Manager, RPA Administrator</p></td><td><p>Application Delete</p></td></tr></tbody></table>

- Note the timezone of the computer that each application is installed on.

## View All Applications

To view all existing applications for automation projects, open the **Process Applications** view of
the **Process Automation** module.

## Create a Process Application

Create one entry for each application instance required for the execution of processes.

To create a process application:

1.  Open the **Process Applications** view of the **Process Automation** module.

2.  Click **Create**.

3.  Complete the **Create a new application** form:

    - **Time Zone**:

      Time zone for defining downtimes.

      Specify a downtime in the time zone in which it occurs. If the bot that you assign the
      downtime to is installed on a computer that uses a different time zone, the downtime interval
      is converted to the bot’s time zone. If you assign the application to multiple bots in
      different time zones, all bots pause executing processes that use that application
      simultaneously. The time intervals might change, depending on daylight saving time.

      For example, if you specify a downtime that starts at 1:30 AM and ends at 5:30 AM in Tokyo
      time (JST (UTC +9)) and the bot is installed on a computer in San Francisco (PST (UTC -8)),
      the bot does not execute processes between 8:30 AM and 12:30 PM in San Francisco time.

      To avoid confusion, append the name of the time zone to the name of the downtime. For example,
      name your downtime `Electrical Power Outage Tokyo`.

    - **Downtimes**

      Click **Create** to add a downtime to the application.

4.  Click **Save**.

## Edit an Application

Edit an application to change its data or downtimes:

1.  Open the **Process Applications** view of the **Process Automation** module.

2.  Click **Create**.

3.  Edit the **Edit the application** form.

    For an explanation of the properties, see
    [**Create an Application**](#form-create-process-applications).

4.  Click **Save**.

## Deactivate or Activate a Process Application

Deactivate an application if it is temporarily unavailable and you don’t know when it will be
available again.

Use downtimes to schedule maintenance and planned downtimes. Deactivation periods are not added to
the list of downtimes.

Applications are not available during downtimes or while deactivated. A member of the process team
can deploy a process on a bot that has assigned the required processes. If an application becomes
unavailable, the bot completes running processes using that application and restarts them when the
downtime or deactivation period has ended.

If an application is not available, deactivate it:

1.  Open the **Process Applications** view of the **Process Automation** module.

2.  Click **Deactivate** (![toggle-on symbol](/mulesoft/current/en-us/rpa-manager/_images/deactivate-icon.png)) on the panel of the
    application to deactivate.

RPA Manager displays an **Inactive** label on the panel of the application.

If a deactivated application becomes available again, activate it:

1.  Open the **Process Applications** view of the **Process Automation** module.

2.  Click **Activate** (![toggle-off symbol](/mulesoft/current/en-us/rpa-manager/_images/activate-icon.png)) on the panel of the
    application to activate.

RPA Manager displays an **Active** label beneath the logo of the application.

## Remove a Process Application

Remove an application if it is no longer available:

1.  Open the **Process Applications** view of the **Process Automation** module.

2.  Click **Remove** (![trash symbol](/mulesoft/current/en-us/rpa-manager/_images/delete-icon.png)) on the panel of the application to
    remove.

3.  Confirm the removal.

RPA Manager removes the application from all processes and bots to which it was assigned.

## See Also

- [Assign Process Applications to an Automation Project](https://docs.mulesoft.com/rpa-manager/processautomation-manage#projectdata-processapplications)

- [Assign Process Applications to a Bot](https://docs.mulesoft.com/rpa-manager/botmanagement-manage#bot-assign-servicetimes-applications)
