Installation

Action Center is available for on-premises installation, allowing you to manage actions from a dedicated user interface, other than the Actions tab in the corresponding Orchestrator instance.

Although Action Center relies on an existing Orchestrator instance, it can be installed on a separate server or the same server as Orchestrator.

The authentication and authorization aspects are managed through a corresponding Identity Server instance and Orchestrator instance, as provided during the Action Center installation procedure.

Compatibility

Orchestrator

Customers using Actions Center within Orchestrator do not have to perform any additional steps other than pointing the Action Center instance to an existing Orchestrator 2021.10 instance. All the existing actions will be reflected to end-users in the new Action Center portal as per the access control defined in a corresponding Orchestrator tenant.

Learn more about the Backward and Forward Compatibility between Action Center and Orchestrator.

Supported Topologies

Single Node Scenarios

• Action Center running on the same server as Orchestrator (different port).
• Action Center running on a single node server pointing to a separate single node Orchestrator instance.

Multi-Node Scenarios

• Multi-node Orchestrator behind a load balancer:

  • A single Action Center instance installed on a different server pointing to the Orchestrator load balancer URL.
  • Action Center installed on all Orchestrator nodes, each pointing to the Orchestrator load balancer URL.
  • Business users exposed to a load-balanced Action Center URL.

Orchestrator Settings to Accept Storage Bucket Requests From Action Center

Features within Action Center that rely on Orchestrator storage buckets (Images & PDF rendering on Form actions, Document Classification & Document Validation actions) require the following configuration changes in Orchestrator to function as expected:

1. Accept Action Center requests to Orchestrator
   1. Go to the Orchestrator installation folder.
   2. Open the UiPath.Orchestrator.dll.config file with administrative permissions.
   3. Under the <appSettings> tag, locate the following key: <add key="AcceptedRootUrls" value="http://{your_localhost_name}:{port_number}" />. If you can't locate the key inside the file, manually add the key yourself.
   4. Append the Action Center URL to the previously located or manually added key (e.g., "https://{Action_Center_host}:{port_number}"). Replace the values in the brackets with your own. For example: <add key="AcceptedRootUrls" value="http://localhost:1234,https://laptop-batman:555" />.
      Important:

      • Make sure the value of the AcceptedRootUrls key does not include space characters.
      • Only add the port value if it is different than 80 or 443 (default ports).
2. Check if the OPTIONS verb is allowed in IIS for the Orchestrator website:
   1. Navigate to IIS.
   2. Select UiPath Orchestrator from the Sites list.
   3. Double click Request Filtering to open the Request Filtering window.

   4. Navigate to the HTTP Verbs tab and search for the OPTIONS verb in the displayed list.

      In case the OPTIONS verb is not present in the list:

      1. Right-click in the window and select Allow Verb.
         
         

         

         
         
      2. Enter OPTIONS and click OK.
         
         

         

         
         
3. Reset IIS for the changes to take effect.

   For other storage buckets like Amazon S3 and Azure, see CORS/CSP Configuration for details on how to configure CORS and CSP settings.