Functional flows
Previous steps
To reach the functional flows stage, the project team must have defined the design system and the configurable components to be used in the app.
In Veritran, a functional flow is a visual an logical sequence of steps that represent a feature solving a specific and reusable business requirement. It consists of a set of related screens that contain logic and represent the steps executed by an app user. These steps usually share similar characteristics and require to be grouped in a flow that is created through the use of modules. Some examples include a transfers flow, payments flow or investments flow in a banking app. To learn more about functional flows and how to build them using modules, read Modules.
There are three main reasons why you must use functional flows in your project:
To ensure quality of the app: decoupling allows you to lower the risk of causing issues or errors by modifying configurations and affecting the app performance. It also allows you to reduce regressions when deploying new versions to the production environment.
To facilitate deployment to the production environment and accelerate the update of existing functionalities: an app that uses modules correctly has a lower risk and makes the features evolution run faster, since it allows you to deploy updates to functionalities on a case-by-case basis.
To ensure reuse of flows in one or more apps.
What you'll find here
This documentation contains a collection of how-to guides that you must use at key moments in the module development and configuration process—before creation, during creation, and after a module is built. Each how-to provides step-by-step instructions or practical guidance to help you set up, build, and use modules in Studio while following best practices and patterns.
Important
The how-to guides in this section are mandatory and must always be used through the functional flows phase.