Skip to content

Manual Guide: Logic Flow

The Logic Flow module is the visual orchestration engine of mdlwr.web.id. It enables developers and system integrators to build, schedule, and monitor end-to-end data integration pipelines using an interactive graph canvas (powered by AntV X6), reactive data tables, and multi-mode execution handlers (Webhooks, Cron Schedules, SQL/File/Stream Monitors).

1. Overview & Module Architecture

Multi-Tab Interface Layout

  1. Canvas / Visual Builder (Tab 1): Interactive drag-and-drop workspace. Nodes (Actions) are grouped by category in a left-hand palette and connected to build sequential or branching workflows.
  2. Logic Flow List (Tab 2): A server-side processed DataTables view listing all configured flows. Double-clicking or selecting Edit on any row dynamically loads the graph workspace in Tab 1.
  3. Execution Logs (Tab 3): Tracks runtime health, latency, payload inputs, execution success status, and error traces.
  4. Deleted History (Tab 4): Captures historical audit logs of removed logic flows with snapshot details and rollback capabilities.

2. Logic Flow Configuration Form Reference

When configuring a Logic Flow via the management form, the settings are categorized into general metadata, execution triggers, scheduling rules, and advanced system options.

General Configuration

  • Category: Organizes the logic flow into custom catalog categories. Defaults to Uncategorize.
  • Sites: Associates the workflow with a specific infrastructure location or node group. Defaults to Central.
  • Name: Human-readable title of the logic flow.
  • Path: Unique routing endpoint or identifier path for incoming requests.
  • Description: Detailed notes outlining the purpose of the pipeline.
  • Technical Doc: File upload field for supplemental PDF/markdown specifications.

Execution & Trigger Parameters

  • HTTP Method: REST verb accepted by the flow endpoint (GET, POST, PUT, DELETE). Defaults to POST.
  • Retry Count: Number of automatic retries permitted on task failure.

  • Processing Mode:

    • sync: Processes requests synchronously and returns responses immediately.
    • async: Offloads execution to background worker queues.

  • Execution Mode: Determines how the flow is triggered:

    • webhook: Exposes an HTTP endpoint to accept external webhooks.

    • scheduled: Runs automatically based on time/interval rules.

    • sql_monitor: Polls database changes via custom SQL queries.

    • file_monitor: Scans directory paths for incoming file drops.

    • stream_monitor: Listens to continuous socket/stream feeds.

  • Target URL: Destination endpoint utilized when the flow acts as a proxy or forwarder.

  • Credentials & Security: Reference keys linked to secure vault configurations for authenticated outbound calls.

Monitoring & Scheduling Rules

  • SQL Monitor Query: Code mirror text editor block used to write polling queries when execution_mode is set to sql_monitor.

  • Schedule Selector: Configurable interval or time-based cron builder supporting:

  • Interval Mode: Hours, minutes, and seconds spacing.

  • Time Mode: Days of the month, days of the week, and exact hours/minutes.

  • Business Calendar & Exception Policy: Governs holiday behavior and business day shifts (STRICT, PREVIOUS_B_DAY, NEXT_B_DAY, SKIP).

  • Timeout: Maximum execution runtime limit before cancellation.

Advanced System Flags

  • Track Reference:

    When enabled, incoming requests must include an External ID. The system remembers previous requests and reuses the same MdlWr ID when the same External ID is sent again, preventing duplicate records and maintaining data consistency.

  • Active: Toggles the operational availability of the logic flow.

3. Visual Workflow Builder (Canvas Integration)

The canvas workspace operates on a component-based node architecture:

  • Palette: Located on the left panel, displaying available Actions grouped dynamically by category. Users can drag actions directly onto the canvas grid.
  • Node Linking: Connect ports between action nodes to establish sequential execution order or conditional branching.
  • Template Injector: Quick-load selectors embedded in the action code drawer allow instant bootstrapping with standard templates (e.g., Standard Webhook).
  • View Controls: Toolbar features include sun/dark theme toggles for the code editor and a fullscreen mode expansion button.
  • Cancel: Closes the current form drawer.
  • Preview: Evaluates and tests cron rule outputs or schedule timings before saving.
  • Clone: Duplicates the current logic flow configuration for rapid template replication.
  • Submit: Commits all form parameters, script configurations, and canvas connections to the database.