Introduction to the Operations Builder

Overview

The Operations Builder tool enables Creators Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. to configure and execute logic behavior in Unqork applications. Creators use the Operations Builder to configure logic for their applications in the form of events and operations. Events are facts about what has happened in the runtime, and operations are the action that executes when the event fires To execute or perform a a task. In the Operations builder, Events fire (execute) one, or multiple Operations.. For example, you could have a Button component configured with an On Click event that executes the Add a Row operation in a Vega Table component. When the end-user End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product. clicks the button, the button's On Click event occurs and the assigned operation executes, adding a new row to the table.

The Operations Builder supports advanced configurations, including components emitting multiple events, and events causing multiple operations to execute. The Operations Builder uses the Vega 2.0 Runtime and Vega-compatible components to produce a guided, easy-to-read experience that isn't possible in the Centauri runtime.

To learn how to use the Operations Builder tool in an application, view our Operations Builder article.

When to Use the Operations Builder

Use the Vega Operations Builder when you want to utilize DOM The Document Object Model (DOM) is the data representation of objects that form the structure and content of a document on the web. The DOM represents the page. events, or new Vega features like the Vega Table Operations. DOM events provide Creators granular control when logic executes. The Operations Builder is only available in the Vega 2.0 runtime.

Lets explore scenarios when you'd use the Operations Builder in Vega versus configuring logic in Centauri.

When to Use the Operations Builder Tool

The Operations Builder enables the following features:

• Granular control over logic using DOM The Document Object Model (DOM) is the data representation of objects that form the structure and content of a document on the web. The DOM represents the page. events, like On Click, On Scroll, On Error, and so on.

• Executing operations like Scroll To or Focus Element.

• Executing Vega Table Operations, like Add Row, Add Column, Clear, and so on.

• Using a Boolean value to change the status of a component using an event. For example, setting a hidden   HTML Element component to visible if they move their mouse over a Button component.

• Using an event occurrence to execute a logic component.

When to Use Centauri Logic Components:

While you can execute logic components using the Execute event operation, consider using Centauri logic components for the following reasons:

• Manipulating data using Data Workflow operators.

• Triggering a Centauri-only component.

• When the existing configuration does not need to be configured with events and operations.

Understanding Events

In Unqork applications, events occur that cause operations to execute. Events can occur from actions in the runtime, in the DOM The Document Object Model (DOM) is the data representation of objects that form the structure and content of a document on the web. The DOM represents the page., or by the end-user End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.. For example, when an end-user clicks an element on the page, the element emits the onClick event. Using the Operations Builder in a Vega-compatible component, Creators Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. can assign one or more operations to execute after an event occurs.

Think of events as the IF portion of a conditional statement A conditional statement, also known as an if-then statement, is a logical formula consisting of a hypothesis (if), followed by a conclusion (then). The conclusion is the result of the hypothesis.. IF this event occurs, THEN perform that operation.

While Unqork supports dozens of events for Creators to configure, common events include:

• On Click: The end-user clicks an HTML HTML (Hyper Text Markup Language) is the standard markup language for for achieving font, color, graphic, and hyperlink effects when creating web pages. element, like a button.

• On Hover: The end-user hovers their mouse over an HTML element.

• On Change: An HTML element changes.

• On Load: The browser finishes loading the page.

• New Submission: An  Initializer component fires at the start of a new module submission.

To get a full list of events, view our Operations Builder Events Reference List.

Once Creators have decided on an event, they can begin building operations that execute when the event fires.

Understanding Operations

Operations are the logic that fires when an event occurs. In Unqork, operations can  change a Boolean value, scroll to a specific element, focus on an element, add new rows in a Vega Table, toggle a component from hidden to visible, and so on.

Think of operations as the THEN portion in a conditional statement A conditional statement, also known as an if-then statement, is a logical formula consisting of a hypothesis (if), followed by a conclusion (then). The conclusion is the result of the hypothesis.: IF this event occurs, THEN perform this operation.

Here are some examples of operations you can build with the Operations Builder:

• Use the Execute operation to trigger a Data Workflow component.

• Use the Add a Row operation to create an additional row in a Vega Table component.

• Use the Boolean operation to display a hidden Button component.

• Download a PDF file.

Combining Events and Operations

After selecting an event and operation(s), you'll configure them in the Operations Builder tool. There are over one thousand possible combinations of events and operations for a component. How you use them depends on your configuration needs.

Here are some examples of event and operation combinations:

• A Button component with an On Click event to execute the Table Add Row operation in a Vega Table.

• An  Initializer component with a New Submission event that executes the Execute operation against a Data Workflow.

• A Button component with an On Click event to execute an Add a Row operation in a Vega Table.

• A Vega Table component with an On Add Row event that disables a Button component using the Boolean operation.

• A Menu component with an On Click event that executes a Scroll To operation targeting HTML headers.

To learn more about using the Operations Builder tool in an application, view our Operations Builder article.

Vega Components Compatible With the Operations Builder

The following Vega-compatible components support the Operations Builder:

Primary Components	Secondary Components	Display & Layout Components	Data & Event Processing Components	Charts & Graphs Components
Checkboxes Date Input Dropdown Menu  Number Radio Buttons Single Checkbox  Text Area  Text Field Simple Select Search Select	Button Hidden Intl Phone Number Phone Number	Columns Field Group   HTML Element Iframe Image Iterator Panel Panel - Dynamic Refresh Vega Table	Initializer Plug-In  Timer	Charts & Graphs components are not supported.

Resources

• Use the Operations Builder Tool.

• Introduction to the Vega Runtime.

• Vega Table Operations.

• Operations Builder Events Reference List