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
      • 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
  • Input sources
  • Documentation
  • Configuration
  • Callbacks
  1. Build & Deploy Apps
  2. Flow Builder
  3. Nodes (Functions)

Inputs

Last updated 7 months ago

Inputs, also known as input arguments, are the parameters that a function uses to execute its action. The default format for input is YAML, providing a straightforward structure for defining input parameters. If necessary, this format can be switched to HTML.

Depending on the function, inputs can be:

  • Data (string, number, integer, boolean, array, object)

  • Files

  • Images

  • Filters

  • Options

  • Functions (for only)

Input sources

Sources for input arguments are varied:

  • Static input: Input arguments can be filled statically in the application logic.

Some special characters may require you to specify the input as text by either:

  1. Adding >- at the start of the document field and moving the input to the next line with two spaces in front.

  2. Placing a ' at both the beginning and end of your input, which will automatically convert to the first method.

Documentation

Configuration

Input boxes provide a context menu accessible through right-click. In this context menu, you can:

  • Switch between YAML and HTML input formats.

  • Set the input as secret, which is useful for passwords.

  • Clear the content of the input box.

  • Delete the input box.

Callbacks

Names of functions supporting callbacks often begin with on.

Certain functions provide the option to include extra inputs, allowing for the incorporation of additional arguments. To add another input box, click the + icon located behind an existing input box.

Dynamic input: They can be filled dynamically with of another function by linking the output to the input.

User input in user interface: Alternatively, input arguments can be dynamically filled by by linking the input widget to the input.

Hover over the right arrow icon of the input box to see its documentation.

In classical programming, a callback is designed to execute code in response to an event. In Heisenware, callbacks can be employed whenever the with an external system or the code integrated through the supports them.

A function that supports callbacks listens for certain events defined in the function. These functions feature a special, dashed input box that contains an output box. Within this box, you can observe the return value (output) of the function executed in response to an event, to which the original function is subscribed. From there, you can work with the data as with any other .

output
capturing user input
integration protocol
code adapter
output
callbacks
Function with input in YAML format
Documentation for input box
A function with a dashed input box listening for incoming MQTT messages in binary format