Automation Anywhere Connected System

Overview

Manage an Automation Anywhere Control Room and deploy Bots directly from Appian! Users can connect to their AA Control Room and perform multiple operations against it. See which devices are connected and what tasks are available to run. The Automation Anywhere Connected System Plug-in uses the AA Control Room API for each operation listed below.

Key Features & Functionality

Run Bot
- The Run Bot operation allows users to run a bot directly from Appian. The run bot operation requires the id of the task to be run and the id of the device to run it on.
Get Devices
- The Get Devices Operation will return all devices associated with a Control Room. This is a useful operation to run if you want to know which devices are currently connected to the Control Room. Only connected devices can be used as a bot to run a task.
Get Tasks
- The Get Task operation returns all available script tasks uploaded to the Control Room. Use the id of a script task in combination with a device id to run a bot.
Get Bot Activity
- The Get Bot Activity operation returns the status of all deployed bots on the Control Room. The operation provides the ability to query bot activity by status, automationId, deviceId, etc.
Get Authentication Token
- Use this operation to get an authentication token form Automation Anywhere. Useful if you want to store Auth Token in a local variable and reuse the same token for multiple operation calls. * Note if no Auth Token is provided the AA CSP will retrieve a new one for you each time an operation is executed. *If the token is expired, then the AA CSP will automatically renew the Auth Token for you.

Parents

timh85 over 3 years ago
Two questions on this plugin
1. Does it support A2019? I believe a number of the APIs have changed.
2. Can it be updated to allow sending of messages to queues in Appian, this is a much better way of starting bots.
In addition, we ran into a large problem in high volume environments. The AA Control Room only allows a user to log in once. However, in a process, you're likely to use the "Get Authentication Token", and then another function. However, there's a race condition that the "Get Authentication Token" invalidates the previous token. You can get the authentication token and save it somewhere, however, there's no way to know the token expiry. Then if the token is expired, the connected system throws an exception which can't be caught, freezing the process. All in, we found limitations in this plugin and so had to use the basic get authentication token, and use a standard HTTP connected system to talk to the APIs.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel

Comment

timh85 over 3 years ago
Two questions on this plugin
1. Does it support A2019? I believe a number of the APIs have changed.
2. Can it be updated to allow sending of messages to queues in Appian, this is a much better way of starting bots.
In addition, we ran into a large problem in high volume environments. The AA Control Room only allows a user to log in once. However, in a process, you're likely to use the "Get Authentication Token", and then another function. However, there's a race condition that the "Get Authentication Token" invalidates the previous token. You can get the authentication token and save it somewhere, however, there's no way to know the token expiry. Then if the token is expired, the connected system throws an exception which can't be caught, freezing the process. All in, we found limitations in this plugin and so had to use the basic get authentication token, and use a standard HTTP connected system to talk to the APIs.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel

Children

No Data