Inistate Documentation
  • Welcome
  • Workspace
  • Module
  • User
    • Role
    • Profile
    • Management
  • Configuration
    • Builder
    • Studio
  • Features
    • Basic
    • Information
    • Listing
    • Activity
    • Form
    • State
    • Flow
  • Advanced
    • Formula
    • Authorization
    • Automation
      • Automation Block
      • Scripting
    • Notification
    • Template
      • Report Starter Kit
      • Code
    • Logic
    • Integration
      • Accounting 1
        • Invoice
        • Cash Sale
        • Delivery Order
        • Stock Transfer
        • Sales Order
        • Creditor
        • Credit Note
        • Debit Note
        • A/P Invoice
        • A/P Credit Note
        • A/P Debit Note
        • Customer
      • Accounting 2
        • Debtor
        • Purchase Order
        • Good Receive
        • Payment Voucher
        • Customer Invoice
        • Customer Payment
      • Jobs json
      • Error Handling
      • Call Back
    • Scripting (Beta)
Powered by GitBook
On this page
  • Usage
  • Flow Configuration
  • Conditional Transitions
  • Best Practices
  1. Features

Flow

Flow in Inistate is a set of defined transitions between States that represent the lifecycle of an entity, dictating how it can move from one State to another.

PreviousStateNextFormula

Last updated 5 months ago

Usage

  • Flow Configuration: Each Flow defines valid transitions, ensuring entities follow an expected path.

  • Conditional Transitions: Some Flows allow conditional steps where specific criteria must be met for transitions to occur.

Flow Configuration

Flow Configuration plays an important role in guiding entities through well-defined paths. It comprises three core components, ensuring that processes progress logically and predictably:

  • From State: This is the initial phase from which an entity begins its transition. It sets the context for all subsequent activities and transitions.

  • Activity: The action or event triggered by a user, serving as the catalyst that propels the transition forward. Activities dictate the conditions required for moving between states.

  • To State: The resulting phase following the completion of an Activity. It reflects the new status or condition that an entity has achieved post-transition.

By specifying these elements, Flow Configurations provide a clear structure that aids teams in executing processes effectively, enabling smooth transitions and incorporating fallback paths for unexpected scenarios.

Conditional Transitions

Conditional

The Conditional functions as a toggle switch within the Flow Configuration, allowing users to change "To State" to "Conditional States".

Conditional States

Conditional States is an evaluative condition that is checked after an "Activity" is performed. This condition determines if the process should advance to the next stage. Below it has a formula condition and description of the condition flow.

Best Practices

  • Sequential: Ensure Flows progress logically, allowing smooth transitions.

  • Fallback Paths: Where applicable, include fallback paths to handle unexpected scenarios.

  • Documentation: Document each Flow to ensure all team members understand the process.

The area within the red frame highlights the Flow panel.