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.

timh85 over 4 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
sam.merrill over 4 years ago in reply to Ankit Shree

Ankit Shree hey Ankit, can you try the Get Devices integration?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Ankit Shree over 4 years ago in reply to dannyt2

Hi, can you tell from where we can get the task and Device ID to put in the integration for Run Bot
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
sam.merrill over 5 years ago in reply to dannyt2

Hey Danny,

The API requires the Admin user type
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
dannyt2 over 5 years ago in reply to sam.merrill

Thanks Sam. A new message:

IntegrationError title: "Http Error 403" message: "Forbidden" detail: "message: Insufficient Privileges "

What access does the account need on AA?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
sam.merrill over 5 years ago in reply to dannyt2

Hey Danny that means the username/password on the CS may be incorrect. If you try the GetAccessToken integration, it may give you more information.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
dannyt2 over 5 years ago in reply to sam.merrill

Hi Sam,

Sean spotted my mistake and got the connection working. I have tried to run a bot and I'm getting the following error:

IntegrationError title: "Http Error 400" message: "Bad Request" detail: "message: JWT String argument cannot be null or empty. "

Any ideas what this means? I think we have put in the correct task ID and Device ID
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
dannyt2 over 5 years ago in reply to sam.merrill

Hi Sam,

I have tried removing https and it comes back on with the same error.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
sam.merrill over 5 years ago in reply to dannyt2

Hey Danny, are you trying to connect through SSL with HTTPS? If so could you try removing 'HTTPS' from the domain and see if that works
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
dannyt2 over 5 years ago

Anyone else seen the error "org.apache.http.client.ClientProtocolException" when testing the connected system?
- Cancel
- Up 0 Down
- Reply
- More
- Cancel