Automation Anywhere Connected System

• Updates key name and Updates to Jackson databind library and added license file

Even today we are facing the same issue reported earlier.

Any resolution for above mentioned prblem

• Updates to Jackson databind library and added license file

• Security Updates

Further to this, this is the value that is being used for the Input parameters property:

a!toJson(
  a!map(
    input_username: if(
      a!isNullOrEmpty(ri!username),
      null,
      joinarray(ri!username, "|")
    ),
    input_groupName: ri!groupName
  )
)

I am getting the following error when attempting to use the Deploy Bot integration for the connected system:

I am wondering if there is anything else that needs to be provided to the Deploy Bot integration to get it to work?

• Security Updates

• New Features and Functionalities curtsey of Tricor Global!
• Now choose between AA V11 and A360 as your Control Room.
• Loads of new integrations like Get Queues, Get Pools, Put Work Item, Delete Work Item, and much more!

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.