---
title: "Initializer Component"
slug: "initializer-component"
updated: 2025-12-04T19:35:20Z
published: 2025-12-04T19:35:20Z
canonical: "docs.unqork.io/initializer-component"
---

> ## 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.

# Initializer Component

UDesignerClassic Designer

The **Initializer component** is one of Unqork's core [logic components](/v1/docs/data-event-processing-components). Initializers trigger operations based on an end-user's interaction with [components](/v1/docs/module-builder-component-library) and [modules](/v1/docs/introduction-to-the-module-builder). Initializer component can be set up to trigger an operation with each new module [submission](/v1/docs/submission-data).

While similar, Initializers and [Decisions](/v1/docs/decisions-component) differ in how they handle inputs. A Decisions component relies on specific input values (if an end-user responds **yes** to a question, the Decision triggers). Initializers, on the other hand, trigger on actions (such as a button-click or a new submission on a page).

To trigger an operation based on an action instead of a value, use the Initializer component.

The Initializer component is in the [Data & Event Processing](/v1/docs/data-event-processing) group to the left of the [Module Builder](/v1/docs/introduction-to-the-module-builder).

## What You'll Learn

After completing this article, you’ll know when to use an Initializer component, how to configure its settings, and how to use it in an Unqork application.

## About the Configuration Window

> [!TIP]
> To learn more about general component settings and those that display when a component is associated with Data Models, view our [General Component Settings](/v1/docs/general-component-settings) article.

### Display Panel

#### Field Text

| Setting | Description |
| --- | --- |
| **Canvas Label Text** | Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field. User-friendly labels make your module more accessible. Keep labels short and descriptive (a word or two) using title case. For longer entries, use sentence case. |

### [![A static displaying the Initalizer Component's Display settings.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer_Component_Display_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer%20Component%20Display.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) Actions Panel

#### Triggers

| Setting | Description |
| --- | --- |
| **Trigger Type** | A drop-down menu showing the following options: - Manual: The component fires when triggered by another component (for example, a Button or Plug-In component). - Watch: The component fires when there's any action taken on the input component(s) listed in the Inputs table. Actions include entering a new value or editing or overwriting a saved value. If there are multiple inputs, use the Required setting to specify what inputs must be present before firing. - New Submission: 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. - Edit Submission: The component fires when the page loads with a submission ID. - Browser Event: The component fires when the end-user closes or refreshes their page. When this happens, the end-user sees a pop-up. Try to keep your operations simple. Long API (application programming interface) calls, for example, might not complete before the page closes. > [!TIP] > You can trigger Initializers set to New Submission or Edit Submission with a Post Trigger in another component. > [!NOTE] > When using New Submission or Edit Submission **Trigger Types** in a workflow, submissions carry through the workflow. The New Submission **Trigger Type** only works for the first module of a workflow. For subsequent modules, use Edit Submission. |

#### [![A static image displaying the Initalizer component's Actions settings.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer_Component_Actions_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer%20Component%20Actions.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) Inputs Table

The Inputs table is for inputting components that trigger the Initializer component.

[![A static image dispaying the Initializer component's Inputs Table](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer_Component_InputsTable_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer%20Component%20InputsTable.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)

| Setting | Description |
| --- | --- |
| **Source** | The Source (Enter Property ID) column is where you enter inputs that your logic component references. Examples of supported inputs include: - The Property ID of another component in the module. For example, a component that acts as a trigger, as an input for a Micro Decision, or referenced in a formula. > [!NOTE] > When using a Trigger Type of Watch, enter all inputs the component must watch for in the Property ID column. > [!TIP] > You can use to reference values nested under a Property ID in the submission data. - Values that aren't the Property ID of a component in the module, but are still present in the submission object. For example, the currentUser object contains information about the end-user. Native values generated by the Unqork Designer Platform. For example, buttonClick, which Unqork creates following button-click events. |
| **Alias** | To simplify the configuration, give each component an alias. An easy approach is to assign each component a different letter of the alphabet. For example, A, B, C. |
| **Required** | If ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(43).png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)(**checked**), the end-user must enter a value in the field of this input component before the logic component executes. By default, this setting is ☐ (**unchecked**). |
| **Delete Input** | Deletes the row from the Inputs table. This action is not reversible. |

#### Outputs Table

The Outputs table is for outputting components and actions you want the Initializer component to perform.

[![A static image dispaying the Initializer component's Outputs Table](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer_Component_OutputsTable_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer%20Component%20OutputsTable.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)

| Setting | Description |
| --- | --- |
| **Source** | For your logic component to recognize an output, you must enter the destination component's Property ID(s). The Property ID entered must match the Property ID of the component that acts as the output. Remember, use camel case without spaces or punctuation. |
| **Type** | The Outputs Type drop-down contains a list of possible actions. When the Initializer triggers, the output type actions against the **Source**. For example, if your Source is a **T****ext Field** and the output type is set to **Clear**, then the Text Field's value clears when the Initializer triggers. > [!TIP] > To learn more about output types, view our [Logic Components: Input & Output Type](/v1/docs/logic-components-input-output-types)s article. > [!NOTE] > The following output Types are not supported: Steps, Focus, Pattern, Content, SelectValues, Editable, Hidden, and Clicked. |
| **Value** | Supporting text or values that work in conjunction with the Output Type selected. If the Type requires custom text (PopMessage or PopError, for example), enter the text here. Otherwise, if the Type needs a yes, no, or GO Value (for example, **Required** or **Trigger**), enter that here. |
| **Delete Output** | Deletes the row from the Outputs table. This action is not reversible. |

### Advanced Panel

#### Set Execution

| Setting | Description |
| --- | --- |
| **Disable Execution** | If Disable Execution is set to ![A toggle switch indicating an on/off state for a user interface element.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 1.png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) **(ON)**, the logic tied to this component does not execute. Use this to keep the component's settings, but disable the operations it performs. By default, this setting is set to ![A toggle switch in the 'on' position, indicating an active setting or feature.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 2(1).png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) **(OFF)**. |
| **Set Debounce** | The number of milliseconds that pass before the module loads this component. This is useful if you have a large module and you load several components at the same time. > [!NOTE] > 1,000 milliseconds = 1 second. > [!NOTE] > For an Initializer component, this is how much time passes before triggering. |

## [![A static image displaying the Initializer component's Advanced settings.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer_Component_Advanced_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer%20Component%20Advanced.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) Adding an Initializer Component

In this example, you'll learn how to set up an Initializer component without configuring the Input table. Instead of referencing the Input table, your Initializer watches for new submissions. With each new submission, your Initializer fires the value **yes** to a series of Radio Buttons.

> [!NOTE]
> These instructions assume that you have an open module saved and with a title.

### What You Need

For this configuration, you need the following components:

- 2 [Radio Buttons](/v1/docs/radio-buttons-component) components
- 1 **Initializer** component

### Configure the Radio Buttons Components

Start your configuration by adding two Radio Buttons components. These Radio Buttons serve as the output location for the Initializer component.

The first Radio Buttons component asks the end-user if they completed an application. The second Radio Buttons component asks the end-user if the application was completed less than a month ago.

1. In the Module Builder, drag and drop two **![Radio Buttons icon](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/radioButtonsComponent_Teal_Icon(1).png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) Radio Buttons** components onto your canvas.
2. In the Property ID and Label Text fields, enter the following:

| Property ID | Label Text |
| --- | --- |
| **fillOut** | Did you fill out this application yourself? |
| **startDate** | Was this application started less than one month ago? |
3. For each Radio Buttons component, complete the **Values** table as follows:

| Property ID | Label Text |
| --- | --- |
| **fillOut** | Did you fill out this application yourself? |
| **startDate** | Was this application started less than one month ago? |
4. Click **Save Component** for each Radio Buttons component as you complete it.

### Configure the Initializer Component

The Initializer component, once triggered, pushes the value **yes** to each Radio Buttons component. The Initializer component triggers as soon as the module loads. This trigger action occurs based on the selection of the New Submission Trigger Type.

1. In the Module Builder, drag and drop an **I****nitializer** component onto your canvas, placing it above your **R****adio Buttons** components.
2. In the Property ID field, enter **initNewSubmission**.
3. In the Canvas Label Text field, enter `Yes to All`.
4. Set the Trigger Type as New Submission.
5. In the Outputs table, set the following: a

| # | Source | Type | Value |
| --- | --- | --- | --- |
| 1 | fillOut | value | yes |
| 2 | startDate | value | yes |

[![A static image displaying the Initalizer component Actions settings, the Trigger Type is set to New Submission and the Outputs table includes the fillOut and startDate Property IDs.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer_Component_Example_Init_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer%20Component%20Example%20Init.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)
6. Click **Save Component**.
7. Save your module.

Once configured, click Preview to open your module in Express View. Here's how your module displays:

[![A static image displaying an Express View with two radio button components. The Initalizer component has automatically selected two of the radio buttons on submission load.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer_06_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer%2006.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)

The **Initializer component** is one of Unqork's core [logic components](/v1/docs/data-event-processing-components). Initializers trigger operations based on an end-user's interaction with [components](/v1/docs/module-builder-component-library) and [modules](/v1/docs/introduction-to-the-module-builder). Initializer component can be set up to trigger an operation with each new module [submission](/v1/docs/submission-data).

Here are some real-world examples of when to use an Initializer component:

- Auto-completing fields when an end-user opens a page or clicks a button.
- Triggering a [Plug-In](/v1/docs/plug-in-component) component in a remote execute module.
- Triggering the creation of a time-stamp on a module submission.

While similar, Initializers and [Decisions](/v1/docs/decisions-component) differ in how they handle inputs. A Decisions component relies on specific input values (if an end-user responds **yes** to a question, the Decision triggers). Initializers, on the other hand, trigger on actions (such as a button-click or a new submission on a page).

To trigger an operation based on an action instead of a value, use the Initializer component.

The Initializer component is in the [Data & Event Processing](/v1/docs/data-event-processing-components) group to the left of the [Module Builder](/v1/docs/introduction-to-the-module-builder).

[Video](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer_Gif.webm?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)

## What You'll Learn

After completing this article, you’ll know when to use an Initializer component, how to configure its settings, and how to use it in an Unqork application.

## About the Configuration Window

> [!TIP]
> To learn more about general component settings and those that display when a component is associated with Data Models, view our [General Component Settings](/v1/docs/general-component-settings) article.

### Display Panel

[![A static image dispaying the Initializer component's Display settings.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer_02_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer%2002.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)

| Setting | Description |
| --- | --- |
| **Canvas Label Text** | Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field. User-friendly labels make your module more accessible. Keep labels short and descriptive (a word or two) using title case. For longer entries, use sentence case. |

### Actions Panel

[![A static image dispaying the Initializer component's Actions settings.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer_03_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer%2003.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)

#### Triggers

| Setting | Description |
| --- | --- |
| **Trigger Type** | A drop-down menu showing the following options: - Manual: The component fires when triggered by another component (for example, a Button or Plug-In component). - Watch: The component fires when there's any action taken on the input component(s) listed in the Inputs table. Actions include entering a new value or editing or overwriting a saved value. If there are multiple inputs, use the Required setting to specify what inputs must be present before firing. - New Submission: 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. - Edit Submission: The component fires when the page loads with a submission ID. - Browser Event: The component fires when the end-user closes or refreshes their page. When this happens, the end-user sees a pop-up. Try to keep your operations simple. Long API (application programming interface) calls, for example, might not complete before the page closes. > [!TIP] > You can trigger Initializers set to New Submission or Edit Submission with a Post Trigger in another component. > [!NOTE] > When using New Submission or Edit Submission **Trigger Types** in a workflow, submissions carry through the workflow. The New Submission **Trigger Type** only works for the first module of a workflow. For subsequent modules, use Edit Submission. |

#### Inputs Table

The Inputs table is for inputting components that trigger the Initializer component.

| Setting | Description |
| --- | --- |
| **Property ID** | The Source column is where you enter inputs for your logic component to reference. Examples of supported inputs include: - The Property ID of another component in the module. Examples include a component that acts as a trigger, an input for a Micro Decision, or a referenced formula. > [!NOTE] > When using a Watch Trigger Type, enter all inputs the component must watch for in the Property ID column. > [!TIP] > You can use to reference values nested under a Property ID in the submission data. - Values that are not the Property ID of a component in the module, but are still present in the submission object. For example, the currentUser object contains information about the end-user. - Native values generated by the Unqork Designer Platform. For example, buttonClick. This Unqork value is created following button-click events. |
| **Alias** | To simplify the configuration, give each component an alias. An easy approach is to assign each component a different letter of the alphabet. For example, A, B, C. |
| **Required** | If ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(43).png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) (**checked**), the end-user must enter a value in the field of this input component before the logic component executes. By default, this setting is ☐ (**unchecked**). |

#### Outputs Table

The Outputs table is for outputting components, and actions you want the Initializer component to perform.

| Setting | Description |
| --- | --- |
| **Property ID** | For your logic component to recognize an output, you must enter the destination component's Property ID(s). The Property ID entered must match the Property ID of the component that acts as the output. Remember, use camel case without spaces or punctuation. |
| **Type** | The Outputs Type drop-down contains a list of possible actions. When the Initializer triggers, the output type actions against the **Property ID**. For example, if your Property ID references a **T****ext Field** and the output type is set to **Clear**, then the Text Field's value clears when the Initializer triggers. > [!TIP] > To learn more about Output Types, view our [Logic Components: Input & Output Types](/v1/docs/logic-components-input-output-types) article > [!NOTE] > The following output Types are not supported or referenced above: Steps, Focus, Pattern, Content, SelectValues, Editable, Hidden, and Clicked. |
| **Value** | Supporting text or values that work in conjunction with the Output Type selected. If the Type requires custom text (PopMessage or PopError, for example), enter the text here. Otherwise, if the Type needs a yes, no, or GO Value (for example, **Required** or **Trigger**), enter that here. |

### Advanced Panel

[![A static image dispaying the Initializer component's Advanced settings.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer_04_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer%2004.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)

#### Set Execution

| Setting | Description |
| --- | --- |
| **Disable Execution** | If Disable Execution is set to ![A toggle switch indicating an on/off state for a user interface element.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 1.png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) **(ON)**, the logic tied to this component does not execute. Use this to keep the component's settings, but disable the operations it performs. By default, this setting is set to ![A toggle switch in the 'on' position, indicating an active setting or feature.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Group 2(1).png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) **(OFF)**. |
| **Set Debounce** | The number of milliseconds that pass before the module loads this component. This is useful if you have a large module and you load several components at the same time. > [!NOTE] > 1,000 milliseconds = 1 second. > [!NOTE] > For an Initializer component, this is how much time passes before triggering. |

## Adding an Initializer Component

In this example, you'll learn how to set up an Initializer component without configuring the Input table. Instead of referencing the Input table, your Initializer watches for new submissions. With each new submission, your Initializer fires the value **yes** to a series of Radio Buttons.

> [!NOTE]
> These instructions assume that you have an open module saved and with a title.

### What You Need

For this configuration, you need the following components:

- 2 [Radio Buttons](/v1/docs/radio-buttons-component) components
- 1 **Initializer** component

### Configure the Radio Buttons Components

Start your configuration by adding two Radio Buttons components. These Radio Buttons serve as the output location for the Initializer component.

The first Radio Buttons component asks the end-user if they completed an application. The second Radio Buttons component asks the end-user if the application was completed less than a month ago.

1. In the Module Builder, drag and drop two **![Radio Buttons icon](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/radioButtonsComponent_Teal_Icon(1).png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) Radio Buttons** components onto your canvas.
2. In the Property ID and Label Text fields, enter the following:

| Property ID | Label Text |
| --- | --- |
| **fillOut** | Did you fill out this application yourself? |
| **startDate** | Was this application started less than one month ago? |
3. For each Radio Buttons component, complete the **Values** table as follows:

| Option Label | Value to Store in the Submission Data |
| --- | --- |
| Yes | yes |
| No | no |
4. **Save & Close** each Radio Buttons component as you complete it.

### Configure the Initializer Component

The Initializer component, once triggered, pushes the value **yes** to each Radio Buttons component. The Initializer component triggers as soon as the module loads. This trigger action occurs based on the selection of the New Submission Trigger Type.

1. In the Module Builder, drag and drop an **I****nitializer** component onto your canvas, placing it above your **![Radio Buttons icon](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/radioButtonsComponent_Teal_Icon(1).png?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D) Radio Buttons** components.
2. In the Property ID field, enter **initNewSubmission**.
3. In the Canvas Label Text field, enter Yes to All.
4. Set the Trigger Type as New Submission.
5. In the Outputs table, set the following:

|  | Property ID | Type | Value |
| --- | --- | --- | --- |
| 1 | fillOut | value | yes |
| 2 | startDate | value | yes |

[![A static image displaying the Initalizer component Actions settings, the Trigger Type is set to New Submission and the Outputs table includes the fillOut and startDate Property IDs.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer_05_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer%2005.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)
6. Click **Save & Close**.
7. **Save** your module.

Once configured, click Preview to open your module in Express View. Here's how your module displays:

[![A static image displaying an Express View with two radio button components. The Initalizer component has automatically selected two of the radio buttons on submission load.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer_06_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Initializer%2006.jpg?sv=2026-02-06&spr=https&st=2026-11-09T16%3A59%3A07Z&se=2026-11-09T17%3A59%3A07Z&sr=c&sp=r&sig=i6fxdFROuymyogwoi8z6iYU1AQZABZoLnQNN98by96M%3D)

## Resources

- [Modify the Initializer component using the toolbar settings](/v1/docs/component-toolbar-settings).
- [How-to: Triggering Initializers with Buttons.](/v1/docs/use-case-triggering-initializers-with-buttons)
- [The difference between chaining Plug-In components and post triggers versus adding them to an Initializer](https://community.unqork.com/platform-q-a-10/what-is-the-difference-between-chaining-plugins-together-via-post-triggers-vs-putting-them-all-into-an-initializer-3413).
- [Initializer components outputs async or sync](https://community.unqork.com/platform-q-a-10/initializer-ouputs-async-or-sync-2717).
- [Set up Checkbox Options to be "true" using an Initializer component](https://community.unqork.com/platform-q-a-10/checkbox-with-initializer-6549).
- [Validate fields in a Panel component with an Initializer component](https://community.unqork.com/platform-q-a-10/how-can-i-validate-fields-in-a-panel-from-a-rule-or-initializer-150).

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.

Triggers activate another component when certain requirements are met. Trigger types include Concurrent, Post, and Error. Some components do not have the ability to trigger others.

The Post Trigger value fires after a component has completed its action. For example, post triggering a component to display the data received from a Plug-In component's API call.

Also known as Record Data. Submission data consists of information saved by Unqork components. View submission data by using the angular command, or in Record Collections.

A naming convention for computer programming. Use camelCase for Property IDs, for example: newUser, lastName, & rdoButton.

A Property ID is the unique field ID used by Unqork to track and link components in your module.

Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field.

Canvas Label Text indicates the purpose of the corresponding field or component. For non-input components, the Canvas Label Text isn't end-user facing, and only appears in the .

Deteremines how the component triggers.

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 outputs components and actions you want the component to perform.

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.

Enter outputs components and actions you want the component to perform.