1. Overview

Overview

What is a Flow In Stubber

In Stubber, a "flow" refers to the mapping, outline, or step-by-step representation of a process, which can be broken down into the following key concepts and components:

Start and End of a Flow

  • Every flow in Stubber has a clear beginning and end.
  • The start is a bit fuzzy and abstract, resembling the initial steps of planning a process.
  • The end is concrete and specific, representing the accomplishment of a well-defined goal.

Actions and States

What Makes Up a Flow:

  • A flow in Stubber is essentially the mapping, outline, or step-by-step representation of a process.
  • States: These serve as resting points in your process, where things pause, awaiting the next step or decision.
  • Actions: Imagine them as specific moments in time when something happens. They can be decisions or updates provided by users.

Understanding Actions and States:

  • States: Think of them as periods in time where everyone involved is engaged in different actions.

  • In the Stubber interface, a state is represented by the following symbol: State

  • Actions: Some actions update information within a state, while others lead to moving on to the next steps.

  • In the Stubber interface, an action is represented by the following symbol: Action

For more information on states and actions, using the following links:

Stubs in Stubber

What is a Stub:

  • In Stubber, each run-through of a process is referred to as a "stub."
  • Picture it as a smart little robot following the mapped-out steps you've laid out in your process definition.

Important Things about Stubs:

  • A stub can only be in one state at a time.
  • It can only be in a state that you've specifically defined for the process.
  • Transitions between states guide everyone involved, showing them the path to completion.
  • In Stubber, we use the term "stub" to refer to an instance of the process being run.
  • Stubs are Finite State Machines (FSMs)
  • A stub can only be in one state at any point in time
  • A stub can only be in a state that is defined on the template or inherited templates (advanced topic)
  • Stubs transition state and thus guide people and AIs along a path to completion

For more information on stubs, using the follow this link.

Special Note

What a Stubber Flow Is Not:

  • A Stubber flow is not a traditional workflow. It's not just about tasks in order.
  • It operates at a higher conceptual level, allowing you to define and structure processes in a flexible and adaptable manner.
Next Setup ->