A Workflow is a set of instructions, or the master blueprint of a process, which outlines exactly how a specific process should be completed.

A Perform, on the other hand, is an individual instance of that Workflow. Think of it as a parent/child relationship.

Each time a member starts working on a workflow a new perform gets created.

Performs in a Customer Request workflow

For example, if you have an Purchase Request Workflow, your team would run the workflow each time they had a new request to purchase anything. Each one of those purchase requests are called Perform in GoodFlow.

At a time may be you got 10 new purchase requests, and having separate Performs allows you to know exactly what progress has been made for each request, or what still needs to be done.

For each workflow you can also rename the word Perform to suit your need.

Here are a few examples of what performs represent in different workflows:

  1. In a sales pipeline workflow, each perform represents a lead moving through all the stages of your sales process. From prospecting to closing the sale, all the information you gather throughout the process is stored within the perform.

  2. In a candidate tracking workflow, each perform represents a candidate.

  3. In request management workflow, for each request logged via introduction form, a new perform gets created.

All the performs have same structure to help you understand the current situation of the work properly and understand full journey of the perform appropriately.

A Perform in GoodFlow

Did this answer your question?