Skip to main content

Workflows

Learn how Glossa discovers, maps, and helps you edit the business workflows behind your project's requirements.

Written by Ali

Overview

Workflows let Glossa discover the business processes implied by your project's requirements — who's involved, what triggers the process, what the outcome is — and represent each one as an editable diagram. Instead of requirements sitting as a flat list, Workflows groups related requirements into the end-to-end processes they support, so you can review and validate process-level understanding with your client, not just requirement-by-requirement.

Accessing Workflows

  1. Navigate to your project

  2. Click Workflows in the left navigation

Discovering Workflows

Glossa can scan your project's requirements and propose candidate workflows automatically.

Find Workflows — discovers new workflow candidates from requirements that aren't yet part of a workflow

Update Workflows — re-scans to refine existing workflows as requirements change

Only one discovery run can be active for a project at a time. If you start a run while another is already in progress, Glossa tells you a run is already active rather than starting a second one.

The Workflow Diagram

Each workflow is represented as a process-map diagram showing:

  • The trigger that starts the process

  • The people, departments, and systems involved (its actors)

  • The branching steps between trigger and outcome

  • The outcome the process ends in

You can edit a workflow's diagram directly — describe the change you want and Glossa applies it with AI and updates the diagram in place.

Creating and Editing Workflows Manually

Besides automatic discovery, you can:

Add a workflow manually — provide a name, trigger, outcome, description, and the departments/people/systems involved, and optionally link existing requirements to it

Edit a workflow — update its details or which requirements it's linked to

Merge workflows — combine two workflows that describe the same process into one; relationships and requirement links transfer to the surviving workflow

Requirement Writeback

Workflows can propose new or updated requirements based on gaps found while mapping a process — for example, a step with no requirement backing it yet. Review each proposal and accept it to add it to your project's requirements, or dismiss it.

Related Articles

Requirements Management

Conflict Detection

Did this answer your question?