A software company can use the Blueprint feature to track and manage the software development lifecycle.
A blueprint consists of two parts:
transitions. Zoho Creator allows you to update the status of a
for important events, such as
when a feature request is received, when development starts, when issues are found, and so on. The relevant team then moves the blueprint to the next stage using
once they complete their work items. This way, the entire development cycle is efficiently tracked and fully automated using workflow actions that are triggered at each blueprint transition.
The following is an illustration of
would work in Blueprint.
Setting up a
Step 1: Navigation to
In your application, navigate to
Create blueprint by:
Associating a form -
Blueprints are associated with a form. Stages and transitions in a blueprint are displayed for the records of a selected form. For example, when employees apply for
they submit a record using a form. The record will contain blueprint transitions like
Reject Leave, and stages like
Select a form from the
Defining a condition -
Blueprints can be triggered based on conditions.
For example, let's say a blueprint should be enabled only when the received request is of type "New Feature Request", so that the development process of the feature can be tracked.
Define a condition as displayed below:
Note: Setting a condition is not mandatory, and can be skipped when blueprint
be enabled for all records.
Add Stages - These are the different milestones in the process.
For a software development lifecycle process,
Feature Developed, and
Testing Complete might
be some of the stages.
and drag-and-drop the newly created
Stages can be renamed or deleted by clicking on them.
Add transitions -
These are the intermediate phase
between two stages,
acting as their link.
Transitions are clickable button
are used to move the blueprint to the next stage.
Using the same example,
Development Started, and
be some of the transitions. When the
transition is performed, the blueprint stage is moved to
the Request Approved
Click on the
icon to a
dd a transition between the stages:
Transitions contain two parts,
Before Actions are to configure who can view the transition,
criteria to display the transition,
tooltips, and confirmation messages. After Actions consist
of actions to be executed after the transition is triggered. The actions available are
Set the following
actions are used to configure
that are triggered when the transition button is clicked.
For example, we can use the
send mail task
to send an automated email notification to customers when their requests are approved.
Add New Action
gives options to configure various workflow actions:
The following image shows the various
that can be configured:
to check out a complete hands-on tutorial on Blueprint.
Using the tutorial,
you will be able to build a functioning app tha
t manages the software development lifecycle.