Skip to main content

Microflow Typologies

A microflow typology is a standardized pattern of a microflow that is designed for a specific purpose.

The microflow typologies in the Menditect Testability Framework define two aspects:

  • What is the purpose of the microflow, and what is the pattern of this microflow.
  • Which microflow typology is allowed to call another microflow typology (see the ‘Call hierarchy paragraph’ below).

Microflow typologies are divided in three main categories:

  • Unit microflow typology: A unit microflow is the smallest executable functionality that result in a measurable output
  • Orchestration microflow typology: An orchestration microflow can be seen as process logic which calls other orchestration microflows and unit microflows. 
  • Touchpoint microflow typology: A touchpoint microflow 'catches an interface trigger' and calls one or more orchestration microflows to handle this. After handling the trigger, the touchpoint microflow is responsible for the navigational logic and refreshing the Client Cache (Browser).

image-20251118-160112.png

1. Naming of microflow typologies​

Each microflow typology is identified by a capital letter prefix. For example: ACT_order_edit_save refers to a touchpoint microflow triggered by the save button on the Order_Edit page. See the Naming conventions page for more details about how microflow typologies are getting their names.

2. Call Hierarchy​

For each microflow type in the hierarchy, the allowed call relationships are defined—this is referred to as the Call Hierarchy. It differs from microflow layering, which describes the overall structure of a Mendix app’s architecture (see Testable App Architecture). For a complete overview of all permitted calls, refer to the Microflow call hierarchy overview page.

3. Advantages of the use of typologies​

  • Clear rules: Typologies define the do's and don’ts around allowed actions inside a microflow of that type.
  • Improved structure: Typologies introduce clear criteria for dividing large microflows in sub microflows.
  • Visual Patterns: A typology often evolve into a 'pattern' that can be visually evaluated
  • Enhanced Naming and Coverage: A typology comply to a strict naming convention which helps in defining coverage goals.
  • Promotes reusability: Typologies stimulates the re-use of logic which saves coding efforts and enhance changeability.