- Getting started
- Best practices
- Autopilot for developers
- Autopilot for testers
- Autopilot for testers
- Quality-check requirements
- Generate tests for requirement
- Import manual test cases
- Generate tests for SAP transactions
- Generate coded automations
- Generate coded API automation
- Refactor coded automations
- Generate low-code automations
- Generate synthetic test data
- Generate test insights reports
- Search Test Manager project
- Autopilot for Everyone
- Autopilot plug-ins
- Data privacy
Autopilot overview
Prompt-to-response flow
There is a predefined interaction flow that Autopilot follows to answer each query:
Once Autopilot receives the prompt, it analyzes its intent, along with any images or files, and determines which (if any) actions it should perform to answer your query.
A pre-response action is an automation or a data source query that Autopilot runs in the background before responding to the query. This helps collect any information or context needed to provide a relevant answer.
If Autopilot decides it should use pre-response actions to help answer your request, it can perform up to six pre-response actions automatically.
A non-pre-response action is an automation which is not configured as a pre-response. If Autopilot decides to use a non-pre-response action, it recommends and sets up the automation to the user by inferring argument values from the conversation context. You can then validate the argument values and execute the automation. Only one non-pre-response action can be recommended at a time.
Once all actions are complete, Autopilot generates a response. It may use information from pre-response actions, non-pre-response actions, and its LLM-trained knowledge. When the response includes a table, the Clipboard AI paste menu is displayed at the bottom of the table.
Any relevant citations, such as those sourced from actions, appear under the previously generated response.