See the whole process
Employees see the current stage in relation to the next steps. Information stays on the CRM record.
Make sales and service processes visible on the record. Interactive stage bars combine progress, transition rules and warnings about excessive time in a stage.
Check the decision-maker and budget before the next stage begins.
◷ Example: five days in this stage · Review follow-up
Schematic illustration with example data
A stage bar puts the status field in context: where is the transaction, what is missing and what comes next?
Employees see the current stage in relation to the next steps. Information stays on the CRM record.
Time in stage and stage-specific thresholds make unusual delays visible. A concrete prompt supports follow-up.
Before a stage change, rules show which information is needed. Missing details are addressed at the right moment.
Chevrons emphasise sequence, timelines show progression, milestones highlight steps and Classic offers a compact overview. Colours and stage icons complement the display.
Choose a style, then click “Quotation”.
This example uses one condition. The product can require several conditions together.
Confirm the budget before moving to “Proposal”.
Define thresholds for each stage. Initial qualification may need a different timeframe from quotation review.
Time since recorded entry into the current stage makes delays traceable. Analysis depends on the available stage history.
When a threshold is exceeded, show a warning and a call to action, such as “Please follow up by phone”. Text and an icon complement the warning colour.
Completed transactions are no longer monitored as active stages according to configuration, keeping attention on open tasks.
A rule can combine several conditions with AND. The configured transition is allowed only when all conditions are met.
For example, require a contact, a budget value or a completed qualification field. Available conditions depend on the supported data model.
A blocked transition identifies the unmet criteria. Employees can see what to add rather than receiving a generic error message.
The configuration preview supports testing blocked and permitted transitions before a stage bar is deployed.
Rules and supported editing paths are checked during setup. A visible block in the bar alone does not establish enforcement for API calls, imports or other editing routes.
Successful, cancelled and neutral end states should be clearly recognisable.
Examples of configurable end states. Hidden dropdown values must remain consistently mapped; changing their display does not delete existing values.
The bar is configured for a suitable module and dropdown field. Existing status values are the starting point.
| Area of use | Example process |
|---|---|
| Leads | New · Assigned · In progress · Converted or disqualified |
| Opportunities | Initial contact · Qualification · Quotation · Negotiation · Won or lost |
| Quotations | Draft · Under review · Sent · Accepted |
| Customer service | New · Under analysis · Waiting for a response · Resolved |
| Projects | Planning · Implementation · Review · Acceptance |
| Custom modules | Suitable dropdown fields and statuses after reviewing the module structure |
These workflows are examples, not prescribed defaults. Supported modules, fields and views are checked for your SuiteCRM version.
Process owners handle setup. Employees then use the bar directly on the record.
Under Processes & Interface → Stage & Process Guidance, select the supported module and status field.
Define order, visibility, end states, style, colours and icons to suit the process.
Configure transition conditions, thresholds and clear warning messages.
Test the display and blocked transitions. Coordinate display conditions for multiple bars before deploying the configuration.
Answers about setup and everyday use.
Configuration builds on suitable existing dropdown fields. Status values, order and hidden values are mapped and reviewed before use.
Click-to-change is intended for supported views and authorised users. The conditions configured for the transition must be met.
The stage stays unchanged. A message identifies the missing prerequisite. Try this in the website demo using the missing budget range.
Multiple configurations for one module can be assigned using suitable display conditions. Which bar applies in each context must be unambiguous.
Stage guidance supports orientation and status changes on the record. The Workflow Engine models broader automation, such as tasks, messages and scheduled follow-up actions.
No; a universal promise would be too broad. The module, field type, view, permissions and alternative editing paths must be reviewed for the installed version.
The right addition to your workflow.
Help & documentation
Progress bars, transition rules and time in stage — in the QOON Knowledge Base.
In about 20 minutes we discuss your pipeline and show stages, transition rules and time-in-stage in SuiteCRM 8.