Before Creating a Functional Flow

Veritran Docs

Before Creating a Functional Flow

Who defines the functional flows in an app?

The manager and the leader in charge of the technical aspects of the project, together with the implementer, define functional flows in an app.

Where do you work?

You must use the architecture documentation prepared for your project, that must include the features of the app and, therefore, the functional flows.

This article contains how-to guides that you must read before you start working with functional flows. It includes the following cases:

If the functionalities of the app and the functional flows have been specified and you need to determine if you must create a flow. To learn more about flows and their use, read Modules.
If a new functionality was added to the app and you must determine whether it is necessary to create a functional flow from scratch or reuse an already created one.

To create a functional flow, one or more of the following circumstances must occur. This means that you must easily identify the characteristics of the flow and its importance as reusable set of screens:

It implies separate use cases: each flow has a clear and specific purpose, while avoiding applying the same logic to different functionalities and ensuring an organized structure.
It facilitates independence and low coupling: flows must interact with each other in a controlled manner, while minimizing dependencies to facilitate their maintenance and improvement.
It is reusable: you should be able to reuse flows in multiple cases in the same app or in other projects.
It is of high importance or frequently used in the app (or other apps): flows must involve a key feature or a feature that is highly used in the app.
It is easy to identify the life cycle and the users involved: flows must be created considering the expected improvement of functionalities and such functionalities must be grouped considering the different types of users.

To build a functional flow and understand its configuration, you must document the parameters of its interface and specify their behavior. This documentation serves two purposes:

Specify the interface settings, the type of data involved, and the impact of each parameter when the flow is invoked.
Provide clear understanding of the flow configuration, both for members in charge of the building process in Studio and for any other members reusing that flow in other projects.

To do so, follow these steps.

Duplicate the Functional Flow Technical Data in your project's repository.
Change the name of the document with the functional flow name, which must identify the functionality it includes.
Complete the document according to the flow defined.

Important

Documenting the configuration of the functional flow allows you and your team to be aware of the technical specifications of such flow and makes it possible to reuse the following with deep understanding on the feature involved.

In this section:

Was this helpful?

Would you like to provide feedback? Just click here to suggest edits.

Veritran Docs

Before Creating a Functional Flow

Who defines the functional flows in an app?

Where do you work?

Important

Search results