---
title: "Console Operator"
slug: "console-operator"
updated: 2025-09-26T00:36:40Z
published: 2025-09-26T00:36:40Z
canonical: "docs.unqork.io/console-operator"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unqork.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Console Operator

UDesignerClassic Designer

The **Console operator** is a testing tool that logs data passed through the other [Data Workflow operators](/v1/docs/data-workflow-operators) in the DevTools Console. It lets you confirm that your Data Workflow is working correctly.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/consoleOperator_thumb_0_0.png?sv=2026-02-06&spr=https&st=2026-11-06T22%3A54%3A30Z&se=2026-11-06T23%3A54%3A30Z&sr=c&sp=r&sig=Kay2%2BVccbCAlROklnIMumFWiFBjhZxdFBVNiXyKuEvo%3D)

Without the Console operator, you can only view data at the beginning and end of your [Data Workflow](/v1/docs/introduction-to-data-workflow). Adding a Console operator after each step of the workflow lets you inspect the effects of the other operators. Watching your Data Workflow is helpful when you need to troubleshoot.

You'll find the Console operator under the [I/O](/v1/docs/iooperators) group to the left of the [Data Workflow](/v1/docs/data-workflow-component) canvas.

## About the Info Window

And here's a breakdown of each setting in the Info window:

| Setting | Description |
| --- | --- |
| Category | Grayed out and non-adjustable setting indicating the operation type. |
| Label | Sets the label for your operator, displaying below the operator on your Data Workflow canvas. This field is optional, but set a label if you use more than one of the same operator type. A label helps you identify your operators without opening any Info windows. Labels are especially helpful with Console operators. This is because you'll see these labels logged in DevTools Console. |

## Adding a Console Operator

Configure a simple Data Workflow that populates two fields with Not Applicable. Then, configure a Console operator to view the results in the DevTools Console.

### Configure the Text Field Components

First, add two Text Field components to serve as the output components.

1. In the Module Builder, drag and drop two **T****ext Field** components onto your canvas.
2. Enter the following **Property ID** and **Label Text** fields for each **T****ext Field** component:

| # | Property ID | Label Text |
| --- | --- | --- |
| 1 | **jobTitle** | Job Title |
| 2 | **salary** | Salary |
3. Click **Save Component** as you add them.

### Configure the Data Workflow Component

Next, set up the Data Workflow to pass data to the output fields.

1. Drag and drop a **D****ata Workflow** component onto your canvas, placing it below the **salary** **T****ext Field** component.
2. In the **Property ID** and **Canvas Label Text** fields, enter `dwfValue`.
3. From the **Trigger Type** drop-down, select **Manual**.

#### Configure the Create Value Operator

1. Drag and drop a **C****reate Value** operator onto your **D****ata Workflow** canvas.
2. Configure the operator's **Info** window as follows:

| Info |
| --- |
| Category | Create Value |
| Label | Create GO Value |
| Preserve Argument Type | ☐ (**unchecked**) |
| Expression/Value | "yes" |

#### Configure the Set Outputs Operator

1. Drag and drop a **S****et Outputs** operator onto your **D****ata Workflow** canvas.
2. Configure the operator's **Info** window as follows:

| Info |
| --- |
| Category | Set Outputs |
| Component | jobTitle |
| Component 1 | salary |
| Action | value |
3. Connect the output port (right) of the **C****reate Value** operator to the input port (left) of the **S****et Outputs** operator.

#### Configure the Console Operator

1. Drag and drop a **C****onsole** operator onto the **D****ata Workflow** canvas.
2. Configure the operator's **Info** window as follows:

| Info |
| --- |
| Category | Console |
| Label | Not Applicable |
3. Connect the output port (right) of the **C****reate Value** operator to the input port (left) of the **C****onsole** operator.
4. Click **Save Component**.

Here's how the completed Data Workflow looks:

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/DatworkflowConsole_thumb_0_0.png?sv=2026-02-06&spr=https&st=2026-11-06T22%3A54%3A30Z&se=2026-11-06T23%3A54%3A30Z&sr=c&sp=r&sig=Kay2%2BVccbCAlROklnIMumFWiFBjhZxdFBVNiXyKuEvo%3D)

### Configure the Button Component

Lastly, configure a Button component to trigger the Data Workflow.

1. Drag and drop a **Button** component onto your canvas, placing it above your **dwfValue** **D****ata Workflow** component.
2. In the **Property ID** field, enter `btnValue`.
3. In the **Label Text** field, enter `Not Applicable`.
4. From the **Action Type** drop-down, select **Event**.
5. In the **On Click** field, enter or select `dwfValue`.
6. Click **Save Component**.
7. **Save** your module.

Here's how the completed example looks in the Module Builder:

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/finalconsole_thumb_0_0.png?sv=2026-02-06&spr=https&st=2026-11-06T22%3A54%3A30Z&se=2026-11-06T23%3A54%3A30Z&sr=c&sp=r&sig=Kay2%2BVccbCAlROklnIMumFWiFBjhZxdFBVNiXyKuEvo%3D)

Preview your module in Express View and open the DevTools Console. Click **Not Applicable** to view the logged operator data.

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Console_Operator_Buttonclick.webm?sv=2026-02-06&spr=https&st=2026-11-06T22%3A54%3A30Z&se=2026-11-06T23%3A54%3A30Z&sr=c&sp=r&sig=Kay2%2BVccbCAlROklnIMumFWiFBjhZxdFBVNiXyKuEvo%3D)

The **Console operator** is a testing tool that logs data passed through the other [Data Workflow operators](/v1/docs/data-workflow-operators) in the DevTools Console. It lets you confirm that your Data Workflow is working correctly.

Without the Console operator, you can only view data at the beginning and end of your [Data Workflow](/v1/docs/introduction-to-data-workflow). Adding a Console operator after each step of the workflow lets you inspect the effects of the other operators. Watching your Data Workflow is helpful when you need to troubleshoot.

You'll find the Console operator under the [I/O](/v1/docs/iooperators) group to the left of the [Data Workflow](/v1/docs/data-workflow-component) canvas.

## About the Info Window

And here's a breakdown of each setting in the Info window:

| Setting | Description |
| --- | --- |
| Category | Grayed out and non-adjustable setting indicating the operation type. |
| Label | Sets the label for your operator, displaying below the operator on your Data Workflow canvas. This field is optional, but set a label if you use more than one of the same operator type. A label helps you identify your operators without opening any Info windows. Labels are especially helpful with Console operators. This is because you'll see these labels logged in DevTools Console. |

## Adding a Console Operator

Configure a simple Data Workflow that populates two fields with Not Applicable. Then, configure a Console operator to view the results in the DevTools Console.

### Configure the Text Field Components

First, add two Text Field components to serve as the output components.

1. Drag and drop two **T****ext Field** components onto your canvas.
2. Enter the following **Property ID** and **Label Text** fields:

| Property ID | Label Text |
| --- | --- |
| jobTitle | Job Title |
| salary | Salary |
3. Click **Save & Close** as you add them.

### Configure the Data Workflow Component

Next, set up the Data Workflow to pass data to the output fields.

1. Drag and drop a **D****ata Workflow** component onto your canvas, placing it below the **salary** **T****ext Field** component.
2. In the **Canvas Label Text** and **Property Name** fields, enter `dwfValue`.

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/DW_Console16_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-06T22%3A54%3A30Z&se=2026-11-06T23%3A54%3A30Z&sr=c&sp=r&sig=Kay2%2BVccbCAlROklnIMumFWiFBjhZxdFBVNiXyKuEvo%3D)

#### Configure the Create Value Operator

1. Drag and drop a **C****reate Value** operator onto your **D****ata Workflow** canvas.
2. Configure the operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Create Value |
| Label | Create GO Value |
| Expression/Value | "yes" |

#### Configure the Set Outputs Operator

1. Drag and drop a **S****et Outputs** operator onto your **D****ata Workflow** canvas.
2. Configure the operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Set Outputs |
| Component | jobTitle |
| Component 1 | salary |
| Action | Value |
| setValue | Not Applicable |
3. Connect the output port (right) of the **C****reate Value** operator to the input port (left) of the **S****et Outputs** operator.

#### Configure the Console Operator

1. Drag and drop a **C****onsole** operator onto the **D****ata Workflow** canvas.
2. Configure the operator's **Info** window as follows:

| Setting | Value |
| --- | --- |
| Category | Console |
| Label | Not Applicable |
3. Connect the output port (right) of the **C****reate Value** operator to the input port (left) of the **C****onsole** operator.
4. Click **Save**.

Here's how the completed Data Workflow looks:

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/DW_Console_15_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-06T22%3A54%3A30Z&se=2026-11-06T23%3A54%3A30Z&sr=c&sp=r&sig=Kay2%2BVccbCAlROklnIMumFWiFBjhZxdFBVNiXyKuEvo%3D)

### Configure the Button Component

Lastly, configure a Button component to trigger the Data Workflow.

1. Drag and drop a **Button** component onto your canvas, placing it above your **dwfValue** **D****ata Workflow** component.
2. In the **Property ID** field, enter `btnValue`.
3. In the **Label Text** field, enter `Not Applicable`.
4. Set the **Action Type** to **Event**.
5. In the **On Click** field, enter `dwfValue`.
6. Click **Save & Close**.
7. **Save** your module.

Here's how the completed example looks in the Module Builder:

![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/DW_Console02_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-06T22%3A54%3A30Z&se=2026-11-06T23%3A54%3A30Z&sr=c&sp=r&sig=Kay2%2BVccbCAlROklnIMumFWiFBjhZxdFBVNiXyKuEvo%3D)

**Preview** your module in Express View and open the DevTools Console. Click **Not Applicable** to view the logged operator data.

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Console_Operator_Buttonclick.webm?sv=2026-02-06&spr=https&st=2026-11-06T22%3A54%3A30Z&se=2026-11-06T23%3A54%3A30Z&sr=c&sp=r&sig=Kay2%2BVccbCAlROklnIMumFWiFBjhZxdFBVNiXyKuEvo%3D)

## Resources

- [Modify the Console operator](/v1/docs/modifying-data-workflow-operators).
- [Console Operator Use Case: Finding an Issue in a Multi-step Data Workflow](/v1/docs/console-operator-finding-issues-in-a-multi-step-data-workflow)
- [Common Troubleshooting Strategies](/v1/docs/common-troubleshooting-strategies)

The DevTools Console helps you securely store, build, test, and deploy your software.

Express View is how your end-user views your application. Express View also lets you preview your applications to test your configuration and view the styling. This is also the view your end-users will see when interacting with your application. After configuring a module, click Preview in the Module Builder to interact with the module in Express View.