Skip to content
Agentivity
Star on GitHub Start free

What a Solution is, and how to mark one

A Solution is the central idea of Agentivity. It is not a feature of the portal: the whole workspace knows which of your agents, teams and workflows are Solutions, and the Studio itself makes them stand out. This page says what a Solution is, what to mark as one, and how to mark it in the Studio.

A solution is something a person launches to get a need handled from start to finish. The person makes a request and receives finished work. Underneath, a solution is an agent, a team or a workflow. The person who uses it does not need to know which one.

What makes something a Solution is a tag: the tag solution, on an agent, a team or a workflow. There is no other way to make a Solution. Marking one only adds the tag, and unmarking one only removes it. Nothing else changes: it is not published, not shared, and it does not run differently.

Tags are always kept in lower case. If you type Solution in the Studio, Agentivity keeps solution.

Mark what a person launches. What it calls stays behind it. The Studio says it in one sentence:

Mark the agent, team or workflow that people launch; what it calls stays behind it.

In our example, the team Payment Reminders has two agents. A person launches the team, so the team is the Solution. The two agents are its members: they are not marked.

It is the same for a workflow. Mark the workflow that people start. Do not mark the workflows that it calls to do a part of the job.

An agent can be a Solution too, when a person launches it directly and no team stands in front of it.

You can do it from a library or from an editor.

The list of agents: Reminder Writer carries the mark Solution beside its name, and the menu of its row offers Open, No longer a solution, Create Template, Use my default model and Delete

  1. Open Studio > Agents for an agent or a team, or Studio > Workflows for a workflow.
  2. On the row of the agent, the team or the workflow, select the three dots.
  3. Select Mark as solution.

When it is already a Solution, the same entry reads No longer a solution. Select it to remove the mark.

This changes only the tags. You do not need to publish.

The panel Info of a workflow: Name, Role, then the box Solution with its switch, then Tags

  1. Open the agent, the team or the workflow in its editor.
  2. In the panel Info, on the right, find the box Solution. It is above Tags.
  3. Turn the switch on, or off.
  4. Select Publish.

The change is saved with the rest of the editor. The box says what a Solution is, with the same sentence as above.

You can also type the tag solution by hand in Tags. It is the same thing: the switch only adds or removes that tag. See Show a team in the portal.

In Agents and in Workflows, a Solution is told apart from the rest:

  • a small mark Solution stands beside its name;
  • its icon takes the accent colour.

If you rest the pointer on the mark, it tells what a Solution is.

WhereWhat happens
The librariesThe mark beside the name, as above.
The portal, and the apps you buildThe portal is a white-label application: people can use it as it is, or adapt it. It finds the Solutions of your workspace by this tag, and nothing more. An app of your own can do the same. See Show a team in the portal and List solutions and start an execution from your app.
A TemplateA Template always has a Solution at its heart. When the Template is created, its main agent, team or workflow carries the tag. So what you import from a Template shows up as a Solution in your library. See Share your work as a Template.
What the Assistant buildsThe Assistant saves its work with the main agent, team or workflow marked as a Solution. See Build your first team with the Assistant.

In the library, the row of the agent, the team or the workflow shows the mark Solution beside its name, and its menu now offers No longer a solution.

In an editor, the switch of the box Solution is on, and the tag solution is under Tags.

A portal or an app lists it after you load its page again.

  • Marking a Solution does not publish it, share it or change how it runs. It adds a tag.
  • A team is one Solution, whatever the number of its members. Mark the team, not each member.
  • To stop listing something in a portal, unmark it.

What you can do with Agentivity.