Release date: 3 August 2022
Bug fixes
Fixed a bug that caused Action Center to fail loading, after upgrading to newer versions, using the
Load Balancer URL
, only if the following steps are made before the upgrade process:
Important
Manually add the correct value of the
Action_Center_URL
key in the registry at PathComputer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\UiPath\UiPath Action Center
.To find the correct value of the
Action_Center_URL
from theenv.json
file:
- Navigate to the Installation Folder.
- Go to the
ActionCenter/Actions/environments/env.json
file path.- From the
PostLogoutRedirectUri
key, retrieve the correct Action_Center_URL.The format for the
PostLogoutRedirectUri
is"Action Center URL"/actions
. For example, if thePostLogoutRedirectUri
ishttps://action-center.loadbalancer.uipath.com:447/actions
, then the corresponding Action Center URL ishttps://action-center.loadbalancer.uipath.com:447
.If the correct value of the
Action_Center_URL
is not provided before starting the upgrade process, then the initial bug reappears and you will need to manually update theenv.json
file. For step-by-step instructions on how to update theenv.json
file, check the last row from Action Center installation issues.
Â
What do the labels mean?
Click to learn more...
This version of Action Center is available in two deployment models:
- standalone Action Center
- Action Center service which is part of Automation Suite.
The product is similar enough across deployment types to share the same documentation.
But differences do exist. When certain information applies to only one of the deployments, we use the following labels:
- only applies for standalone Action Center and does not apply for Automation Suite Action Center.
- only applies for Automation Suite Action Center and does not apply for standalone Action Center.
Whenever there is no label, the information applies for both deployment types.
Updated 7 months ago