> ## Documentation Index > Fetch the complete documentation index at: https://developers.argosidentity.com/llms.txt > Use this file to discover all available pages before exploring further. # March 2026 update > ARGOS Omni product update for March 2026 Hello from ARGOS Omni. We are introducing ARGOS Omni. *** ## ARGOS Omni launches New Feature Omni is a document verification platform that **runs your verification policy exactly as you wrote it**, in plain language. The work people used to do by hand is written once as policy sentences, and every case after that is processed automatically. No code required. *** ## Workflow creation wizard New Feature Build a verification workflow in four steps. | Step | What it does | | -------------------- | --------------------------------------------------------------------------- | | 1. Basic information | Name and description | | 2. Policy definition | Write, in plain language, what you verify and against which criteria | | 3. AI model | The model that performs the analysis. Without a choice, the default is used | | 4. Output schema | Define the JSON structure you want back | Workflow creation step 2, policy definition Saving generates a **playbook** — the execution plan — from the policy text. *** ## Automatic engine assignment New Feature **You never pick which engine a check needs.** Engines are attached from the content of your policy, and the execution order is decided for you. A clause such as "screen the managing member's name against AML lists" becomes an action with an AML engine attached, while a clause that needs no external lookup produces an action with no engine — [AI model and engines](/en/omni/dashboard/workflow-setup/engine-selection). *** ## Define your own output schema New Feature Define the JSON structure you receive. Build it row by row in the **Field Builder**, or paste a whole schema into **JSON Schema Input** — the two convert to each other. Output schema Field Builder Results come back in exactly the shape your system expects, so no post-processing conversion is needed. *** ## Copy a workflow New Feature The **Actions** menu in the workflow list can copy a workflow, creating a new one with the policy, schema, and playbook intact. Leaving the name blank sets it to `[Copy] original name`. Handy for trying a different policy version without rewriting the output schema. *** ## The analysis results screen New Feature Review a result through sub-tabs. | Tab | Contents | | ------------- | ------------------------------------------------------------- | | Summary | Decision variables and a per-step summary of what was decided | | Report | Output-schema fields and the extracted values | | Audit | The steps the agent ran and the tools it called | | Output Schema | The raw JSON of the extracted data | | Info | Processing information and the items used | *** ## API v1 New Feature Automate profiles, folders, items, and analyses through the API. Creating and editing workflows stays in the dashboard — [API overview](/en/omni/api-reference/overview). *** ## Related pages * [Introducing Omni](/en/omni/getting-started/introduction) · [Quickstart](/en/omni/getting-started/quickstart) * [Creating a workflow](/en/omni/guides/creating-a-workflow)