AI Agent Studio FAQs

Refer to this FAQ for general queries on the behavior and functionality of creating Model connections, Prompt Templates, running automations using the Generative AI Prompt Template package, and tracking and monitoring model interaction data within automations for security and governance.

General FAQs

What are the supported foundational models?
Currently, AI Tools supports foundational models from hyperscaler vendors such as Amazon Bedrock, Google Vertex AI, Azure OpenAI, OpenAI and others. These are supported models for each vendor:
  • Amazon Bedrock: anthropic.claude-v2:1, amazon.titan-text-express-v1, amazon.titan-text-lite-v1.
  • Google Vertex AI: text-unicorn, text-bison, text-bison-32k, gemini-1.0-pro.
  • Azure OpenAI: gpt-4, gpt-4-32k, gpt-35-turbo, gpt-35-turbo-16k.
  • OpenAI: gpt-4, gpt-4-turbo-preview, gpt-3.5-turbo, gpt-3.5-turbo-16k.
Does Automation Anywhere provide foundational models for use within AI Agent Studio?
No, AI Agent Studio offers customers the ability to connect to their own foundational models from vendors such as Azure OpenAI, OpenAI, Amazon Bedrock, and Google Vertex AI by providing the connection details to customer instances of these models within Model connections. See Manage Model connections (Automation Admin).
What is the license requirement for AI Tools?
AI Tools is included in the AI Agent Studio product suite and can be made available with the purchase of the Enterprise Platform license. For details about the Enterprise Platform license, see Enterprise Platform.
What is the general availability for AI Agent Studio?
This product is available on Automation 360 Cloud only.
What type of data is stored and for how long when I enable data logging?
When data logging is enabled, all model interactions, including prompts, model responses, and parameters, are stored during automation or prompt executions. This data is stored within your environment and is used to offer detailed insights into AI usage in automations.
What is the data retention policy for stored data?
We adhere to a consistent data retention policy for audit logs. You can review the policies here: Automation 360 のよくある質問 (FAQ).
Can I use SIEM integrations to forward the stored logs?
Yes, stored data can be forwarded to an integrated SIEM system configured in the Control Room.
What security measures are implemented to protect stored prompts?
All logged data is stored within the customer's production environment, never leaving the protected boundaries. This data is used solely for analytics to provide insights into AI usage within automations. Prompts and model responses are encrypted using industry-standard algorithms, and log data is securely transmitted via TLS. Access to view the prompts and responses is controlled through role-based access control.
Can the text prompts and model responses be exported or printed?
To safeguard privacy, prompts and model responses cannot be exported or printed from the Control Room. However, they can be forwarded to a SIEM through a SIEM integration.
Do I need additional licenses for data logging?
Data logging and AI governance is part of the Enterprise Platform license, available through AI Agent Studio.

For details about the Enterprise Platform license, see Enterprise Platform.

Known product behavior

  • After creating a Prompt Template, the name and description of that template cannot be changed.
  • Currently, use of Prompt Templates is available only from within a Task Bot.
  • If you delete a Model connection that is connected to a Prompt Template, you will get an error while executing the Task Bot that has been configured to use that Prompt Template.
  • If you delete a Model connection and create a new one with the same name, the Prompt Template will reference the new version. However, if the underlying LLM models are different the outcome could be different.
  • For Microsoft Azure connections:
    • The Model connection configuration requires a user to provide a Deployment ID which is the name of the deployment within the Microsoft Azure portal. As this deployment is mapped to a specific foundational model, users should ensure that they select the correct Model connection model that maps to the Microsoft Azure deployment model.
      注: You would see a warning message if these values do not match.
    • Users should be aware that altering the connection details of an existing Model connection would save incorrect input details and will not automatically trigger the Test connection functionality. This could result in Prompt Templates or Task Bots, using the Model connection, to break during execution. If you make any changes to a Model connection, ensure you test the updated connection so the Bots using this Model connection do not fail during automation execution.
  • If you encounter a run-time error during an automation execution, based on the system-displayed error message, 'Unable to publish AI governance audit logs. Please make sure that the Bot Agent version is at least 22.60.10. Error: <java.lang.NoSuchMethodError error message>' we recommend updating to the latest available Bot Agent version.
  • If you are unable to see any Audit log data, we first recommend checking for relevant custom role permissions. If you have the required permissions, then we suggest making sure you are using the latest available Bot Agent version.
  • For Audit log and Bot execution features to work smoothly, we recommend using compatible Control Room and Bot Agent versions. See Assign roles and permissions to enable AI governance to view the version compatibility matrix.