The Operations Builder displays in the component settings panel when a component is placed in a Vega module or a Vega-enabled Panel component. Not every component supports every event. See Event Compatibility below.
An event is an action or condition that triggers the Operations Builder to run. When the event occurs, the operations assigned to it execute in order.
At least one scope is required. The available scopes vary by signal type. Some signals are self-only and do not offer the Child option.
Operations and events display a stability badge when they are not yet fully stable. No badge means the operation is stable and production-ready. Stability badges are synced from the runtime manifest and reflect the current stability state of each operation in the active runtime.
Stable operations display no badge.
An operation is an action that executes when an event fires. Each event handler can contain multiple operations that run in order. The following categories summarize the available operations.
DOM (Document Object Model) events are signals or notifications that something has occurred or is occurring within a web page, often triggered by user interactions or by the browser itself. These events allow JavaScript to react to changes and interactions on a web page, making it dynamic and interactive.
Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform.
APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services.
The Vega (v 2.0.0) runtime is the next-generation engine of the UDesigner platform. Vega uses cutting-edge technologies to improve the Creator and end-user experience.
The component fires when the page or called module loads without an existing submission ID. Dashboards and remote execute modules are great uses for this trigger.
Enter the Property ID of the component that you want to trigger on each button-click.
DOM (Document Object Model) events are signals or notifications that something has occurred or is occurring within a web page, often triggered by user interactions or by the browser itself. These events allow JavaScript to react to changes and interactions on a web page, making it dynamic and interactive.
The Number data type accepts integer or floating point values. The number data type does not use quotes around numerical values.
HTML (Hyper Text Markup Language) is the standard markup language for for achieving font, color, graphic, and hyperlink effects when creating web pages.
Scope is a tool that limits an application's access to a user's account. An application can request one or more scopes, this information is then presented to the user in the consent screen, and the access token issued to the application will be limited to the scopes granted.
The Boolean data type accepts one of two values: true, or, false.
A key-value pair is a fundamental data structure where a unique "key" is associated with a specific "value," used for organizing and retrieving data efficiently, like in dictionaries or databases.
Cascading Style Sheets (CSS) is a style sheet language used for presenting how a HTML or XML document looks to end-users.
A URL (uniform resource locator) is a unique identifier used to locate a resource on the internet. Also known as a web address.
HTTP (Hypertext Transfer Protocol) is an application-layer protocol used to transmit hypermedia documents like HTML.
A Module Builder component that executes a configurable pipeline of data operations in sequence, like API calls, transformations, filtering, and sorting. Creators build the pipeline visually using operators on the Data Workflow canvas. In Unqork, Data Workflow is a component, not the same as a workflow built in Workflow Builder.
A branch is a copy of modules in an Unqork application that helps Creators work in parallel. Branching an application can seperate in-progress changes from release-ready modules.
A branch is a copy of modules in an Unqork application that helps Creators work in parallel. Branching an application can seperate in-progress changes from release-ready modules.