Initializer Component

Estimated Reading Time: 7 minutes

Overview

The Initializer component is one of Unqork's core logic components. Initializers trigger operations based on an 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.'s interaction with components and modules. Initializer component can be set up to trigger an operation with each new module submission.

While similar, Initializers and Decisions 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 group to the left of 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 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.

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

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 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. Initializers set to New Submission or Edit Submission with a Post Trigger 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. in another component. NOTE When using New and 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.

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 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. Initializers set to New Submission or Edit Submission with a Post Trigger 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. in another component.

NOTE When using New and 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
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 dot notation In Unqork, Dot Notation accesses the properties of an object. The object's name comes before the period, and the property comes after. For example, to reference just the City from an Address Search component, you would enter "address.city". to reference values nested under a Property ID in the submission data 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.. 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 (checked), the end-user must enter a value in the field of this input component before the logic component fires. 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.

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 A naming convention for computer programming. Use camelCase for Property IDs, for example: newUser, lastName, & rdoButton. 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 Text 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 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 (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 (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.

Setting

Description

Disable Execution

If Disable Execution is set to (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 (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 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.

In the Module Builder, drag and drop two Radio Buttons icon

Radio Buttons components onto your canvas.

In the Property ID A Property ID is the unique field ID used by Unqork to track and link components in your module. and Label Text Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field. 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?

For each Radio Buttons component, complete the Values table as follows:

Option Label	Value to Store in the Submission Data
Yes	yes
No	no

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.

In the Module Builder, drag and drop an Radio Button component icon