Workflows Admin

The Workflows screen lists all existing workflows, shows the default workflow, and allows you to create/edit/delete your workflows.

Workflows pass submitted quotes through a process that correspond to your business requirements. Workflows facilitate the following:

  • Allows managers to approve or review quotes before they proceed to the next state.
  • Performs builds on configurators included within the quote, as well as quote outputs.
  • Restricts access to the quote and its properties depending on the state they are in.
  • Performs other routines, such as sending emails or making API calls to external sources.

The workflow mechanism is implemented as a state machine. This means after a quote is submitted, it will be assigned a specific state, which dictates its behavior. For instance, in one state, a quote may be visible only to management, who can perform certain actions on the quote. Performing these actions may deliver the quote to another state, which then makes it visible to other users, such as engineers or the customer.

Advanced logic may also drive how a quote is taken through a workflow. A common example is if a quote exceeds a certain price. If the quote's price exceeds a certain threshold, it may first need to go through a special approval state before it goes to the "Completed" state. Or, perhaps you need special approval from an engineer if the quote contains a specific configured product within.

Because Workflows use Snap, this logic can be specified in a maintainable way.

Workflow States

As a quote goes through a workflow, it will be assigned to a specific workflow state based on that workflow's logic. Think of a state as a stopping point in the workflow, where an automated process can build documents, or a user can approve, reject, or edit the quote and advance it to other states.

Workflow Actions

Workflow actions let your users contribute to the workflow beyond the basics of "approve" and "reject".

Common Workflow Scenarios

Building a workflow to match your business requirements requires some understanding of Snap and the specific Snap blocks which are used within workflow rules. These workflow scenarios represent some of the more common business requirements, which can inspire workflows for your specific needs.

 

An example workflow, built with Snap blocks.

Was this article helpful?