Skip to content
Orvanta Docs

Outputs

Overview

Section titled “Overview”

The outputs feature in Orvanta’s low-code app editor displays the states and results of applications. Located on the left-hand side of the editor, outputs are organized into three categories: context and state, component outputs, and background runnables outputs.

Context and state

Section titled “Context and state”

App context

Section titled “App context”

The app context provides access to several key outputs:

  • summary: Current app summary
  • email: Current user’s email address
  • groups: Groups the user belongs to
  • hash: URL hash parameters
  • mode: Current app mode (editor or viewer)
  • query: URL query parameters as JSON object
  • username: Current user’s username
  • workspace: Current app’s workspace

State

Section titled “State”

The app state is a client-side store that can be used to store data. The app state can be manipulated by frontend scripts.

Component outputs

Section titled “Component outputs”

Each component generates its own outputs displayed in a collapsible tree structure. For example, the Table component offers outputs including selectedRow, loading, result, search, and selectedRowIndex.

Containers

Section titled “Containers”

Container components can hold other components, with nested component outputs displayed within the container’s output structure.

Background runnables

Section titled “Background runnables”

Background runnables are scripts or flows executing in the background to perform non-UI-related actions.

Connecting inputs to outputs

Section titled “Connecting inputs to outputs”

You can connect component inputs to outputs through the connection menu by clicking the plug icon and selecting outputs. Alternatively, components can be referenced directly using eval syntax (e.g., a.result).

Setting component values

Section titled “Setting component values”

The setValue helper function allows manual component value assignment: setValue(id: string, value: any). Note that mixing dynamic default values with setValue is inadvisable.

Resource connections

Section titled “Resource connections”

Apps are executed on behalf of publishers and by default cannot access viewers’ resources. Non-static resource references require enabling “Resources from users allowed” in runnable inputs.

Component ID editing

Section titled “Component ID editing”

Component IDs can be modified by clicking the ID field. IDs are restricted to letters and numbers only.