Heisenware Docs
Go to websiteGet a demo
  • 👋Welcome
  • Getting started
  • Release Notes
    • v84 - Get in the flow
    • v83 - Beauty treatment
    • v82 — Fully distributed
    • v81 — Removing old cruft
    • v80 — Chicks on fire
    • v79 — Nothing is forever
    • v78 — Keep moving
    • v77 — More intelligence
    • v76 — Well cooked
  • Build & Deploy Apps
    • Overview
    • Flow Builder
      • Nodes (Functions)
        • Inputs
        • Trigger
        • Output
      • Flows
      • Function Extensions
        • Modifier
        • Filter
        • Error handler
        • Memorizer
      • Objects & Instances
      • Utilities
        • Basic Functions
        • PDF functions
        • Circular buffer
        • Timer
        • Counter
    • Integrations
      • Protocol Connectors
        • GraphQL
        • HTTP/REST
        • MQTT
        • OPC UA
          • Heidenhain PLCs with OPC UA
        • RS-232/485
        • Siemens S7
      • Data Connectors
        • File
        • Relational Database
        • Time Series Database (WIP)
      • API Connectors
        • OGC SensorThings API
        • Operating System
        • Zebra RFID IoT Connector
      • Agent / (Edge Connector)
      • Calling Custom Code
    • UI Builder
      • Input Widgets
        • Form
        • File Upload
        • Photo
        • Signature
        • Barcode / QR-Code (WIP)
        • Document Scan (WIP)
      • Display Widgets
        • Chart
        • Chat
        • Circular Gauge
        • Data Grid
        • Linear Gauge
        • Map
        • Media View
        • Progress Bar
        • Sparkline
        • Status Lamp
        • Toast
        • Value Box
        • Kanban Board
        • Data Tiles
        • Pie Chart
        • Sankey
      • Buttons
      • Text Box
      • Images
      • Icons
    • Communication Interfaces
      • Email Notifications
      • OPC UA Server
    • Data & File Storage
      • Internal InfluxDB
      • Internal PostgreSQL
      • File Server
    • App Appearance
      • Pages
      • In-App Navigation
      • Screens & Devices
      • Theming
    • Simulation & Testing
      • Simulating Events
      • Simulating Data
    • PDF Templates
    • RAG-based Chatbot
    • Deployment
  • Manage Apps
    • Overview
    • Manage Apps
      • General Settings
      • Users and Access
      • Distribution & Versioning
    • Manage Integrations
    • Manage Account
      • Account Structure
      • Members
      • Workspaces
  • TUTORIALS
    • Build Your First Heisenware App
  • Connect Heidenhain CNC with OPC UA Support
  • Related links
    • Website
    • Privacy policy
    • Imprint
Powered by GitBook
On this page
  • Trigger events
  • Configuration
  • Sequential processing
  • Explainer video
  1. Build & Deploy Apps
  2. Flow Builder
  3. Nodes (Functions)

Trigger

Last updated 6 months ago

The trigger initiates a function to execute its action. To do this, the trigger listens for events. Events can be captured by users or programmatically.

Jump to .

Trigger events

The following events can serve as triggers:

  • Application logic events

    • change, update, or becoming true of an input argument

    • change, update, or becoming true of an output

    • change, update, or becoming true of a modifier

  • UI events

    • Click of a button

    • Loading of a page

    • Start of an app

      • once

      • periodic (every 0.1 seconds to once a day)

    • Stop of an app

  • App Builder: Click on the trigger icon of the function

A single function can be associated with more than one trigger event. For instance, a function might be triggered when its input argument is updated or when a page is loaded. It can also be triggered periodically after app start.

Configuration

A trigger can be configured in different ways:

  • Via context menu: Right-click on the trigger box

    • App start

    • App stop

  • Drag and drop of other items on a trigger

    • on page load

    • on input change, update, true

    • on output change, update, true

    • on modifier change, update, true

  • Drag and drop of a trigger on a button

To unlink an event from a trigger, click the x next to the trigger event.

Sequential processing

To sequentially process an array of data, the trigger can be configured to execute the function for each value within the array individually, one by one. This type of function execution corresponds to a so-called loop in classic programming.

To configure sequential processing of arrays:

  1. Right-click on the trigger to open the context menu.

  2. Hover above Process One By One.

  3. Select the input argument of the function that contains the array.

To switch back to regular processing:

  1. Right-click on the trigger to open the context menu.

  2. Select Process Regularly.

Example: One prevalent use case for sequential processing is merging objects or arrays, where a singular element should be merged into all sub-arrays of an array of elements. The following image illustrates a function where the trigger of the combine function is configured to Process One By One on argument one (On arg 1). As a result, both sub-arrays in the output contain the singular element.

Explainer video

explainer video
Three trigger events
Sequential processing of functions