You can create and save agents, which are collections of up to five Anvi Chat prompts that you can run manually or on a schedule. You can also automate the steps (prompts) within an agent so that they do not require your direct intervention to run.
NOTE
Agents were called Workflows in earlier versions.
For scheduled agents, you can also send or receive emailed reports on the chat history, the last message sent, or errors.
You can also create an agent by using a predefined agent in the Anvi Chat template library. See Planview Anvi Prompt and Agent Library for more information.
To create an agent:
>
Manage favorites.
TIPS
in a Step cell to rearrange steps.
next to a prompt to remove that step from the agent.
You can set up an agent to run automatically once at a specific date and time or to run repeatedly based on a schedule. You can also configure Anvi to email reports about the scheduled agent runs.
To run an agent automatically on a schedule and enable reporting:
>
Manage favorites.
To view the history of agent runs:
>
Manage favorites.
for that run.
Follow these best practices, tips, and tricks to maximize your experience when using Anvi Chat agents.
| Best practice | Explanation |
|---|---|
|
Ask Anvi to return counts instead of lists |
Scheduled agents run automatically and unattended. However, large sets of returned results, such as those in lists, can cut off silently. To avoid this, use prompts that ask for counts and aggregations instead of lists; counts and aggregations are reliably returned with small or large results. |
|
Chain simpler prompts together instead of overcomplicating prompts |
Use a series of simple prompts, as in the following example, instead of overcomplicating a single prompt with multiple tasks:
|
|
Specify the dates and times; avoid words like "today" |
Agents don't inherently know concepts such as "today." Instead, start an agent with a date prompt. Then reference that date explicitly in subsequent prompts; never assume that the time context will carry over to future prompts. |
|
Match the data model's terms and vocabulary |
Use the exact field names, entity types, and hierarchy terms from the product you are asking about. Mismatched terminology can cause unpredictable results. |
|
Avoid ambiguous terms and conditions |
The more specific the conditions in a prompt are, the more repeatable the results will be, as in the following examples:
|
|
Test the agent before scheduling it |
Run the agent manually two or three times, testing all prompts in the agent, before scheduling the agent for automatic runs. If the results vary among the manual tests, refine the prompts until the results are stable. Inconsistent prompts become inconsistent agents. |