Decisions Component

Overview

The Decisions component is an event component for logic-based if/then scenarios. For example, if your end-user selects radio button A, then show field B. Or, if your end-user types value X, then display pop-up Y.

Three inputs drive the Decisions component:

Input component: What drives the action. Any component works here, including Buttons, Radio Buttons, or Text Fields. The Decisions references the Property ID A Property ID is the unique field ID used by Unqork to track and link components in your module. of the input component.
Output component: What reacts to the action. Again, any component works, including Panels and Field-Groups containing multiple components. The Decisions references the Property ID of the output component.
Decisions component: The Decision itself. You can configure the interaction between the inputs and outputs using Micro Decisions. You can set the input and output behavior by selecting the Type for each. The Micro Decisions table is where you'll set if/then rules using your defined inputs and outputs. Inputs display in the left columns of the Micro Decisions table. The column headers match the Input components' Property IDs. Outputs display in the right columns and are named using a concatenation of their ID and Type.

You can find the Decisions component in the Data & Events Processing group to the left of the Module Builder.

What You'll Learn

After completing this article, you’ll know when to use a Decisions component, how to configure its settings, and how to use it in a module.

About the Configuration Window

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	A component’s 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 Module Builder. 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. For Decisions, it's best practice to use the same value for Canvas Label Text as your Property ID: ruleXxx.

Setting

Description

Canvas Label Text

A component’s 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 Module Builder.

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.

For Decisions, it's best practice to use the same value for Canvas Label Text as your Property ID: ruleXxx.

Actions Panel

Triggers

Setting	Description
Trigger Type	This setting provides the following options: Manual: The component fires when triggered by another component. For example, when using a Button or Initializer component to trigger a Plug-In component. By default, this Trigger Type is selected. Watch: The component fires when there's any action taken on the input listed in the Inputs table. Actions include entering a new value, editing, or overwriting a saved value. If there are multiple inputs, use the Required setting to specify what inputs must be present before firing.
Execution Type	When executing a rule, the Decisions component runs through each Conditional (top to bottom) to set the output. For clarity, assume that you have six configured Conditionals. The third and fifth Conditionals fulfill the Decision conditions to determine a match. The following Execution Types set the Decision's behavior: First: This is the default Execution Type. When you choose First, the Decision runs through the Micro Decisions only acting on the first Micro Decision that matches. Based on the earlier example, the match is on the third Micro Decision. Last: When you choose Last, the Decision runs through the Micro Decisions only acting on the last Micro Decision that matches. Based on the earlier example, the match is on the fifth Micro Decision. Merge: When you choose Merge, the Decision runs through the Micro Decisions and concatenates new values as a comma-separated list. This behavior only works with multiple Micro Decisions with Output types of value.

Setting

Description

Trigger Type

This setting provides the following options:

Manual: The component fires when triggered by another component. For example, when using a Button or Initializer component to trigger a Plug-In component.

By default, this Trigger Type is selected.

Watch: The component fires when there's any action taken on the input listed in the Inputs table. Actions include entering a new value, editing, or overwriting a saved value. If there are multiple inputs, use the Required setting to specify what inputs must be present before firing.

Execution Type

When executing a rule, the Decisions component runs through each Conditional (top to bottom) to set the output. For clarity, assume that you have six configured Conditionals. The third and fifth Conditionals fulfill the Decision conditions to determine a match.

The following Execution Types set the Decision's behavior:

Inline image displaying a selected radio button. First: This is the default Execution Type. When you choose First, the Decision runs through the Micro Decisions only acting on the first Micro Decision that matches. Based on the earlier example, the match is on the third Micro Decision.

Inline image displaying a selected radio button. Last: When you choose Last, the Decision runs through the Micro Decisions only acting on the last Micro Decision that matches. Based on the earlier example, the match is on the fifth Micro Decision.

Inline image displaying a selected radio button. Merge: When you choose Merge, the Decision runs through the Micro Decisions and concatenates new values as a comma-separated list. This behavior only works with multiple Micro Decisions with Output types of value.

Inputs

Setting	Description
Source	The Source 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. When using a Trigger Type of Watch, enter all inputs the component must watch for in the Property ID column. 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.
Type	The following input types are available for your selection: Exact: With this input type, your logic component watches for an exact value. Use this option when you have a finite number of responses. Typical components used with this input type include Radio Buttons, Dropdowns, or Text Field components. Range: Used when the input includes a range of numeric values, like 1 to 15 or 3% to 40%. Typical examples include ages, coverage amounts, and so on. To learn more about Input Type best practices, view our Best Practices: Component Configuration article. Contains: Used when the value contains a phrase and is ideal for strings. An example is a button click that carries dynamic prefixes or suffixes.
Required	Set an input to Required when it must have a value before triggering the Decision.
Silent	"Silent" stands for "Silent Watcher". If Silent is selected and the Trigger Type is set to Watch, the Decisions component won't trigger if that input's value changes. This setting lets you use the input data as a Micro Decision without triggering the component if that data changes. Silent only functions when the Trigger Type is set to Watch. It won't function if the Trigger Type is set to Manual.

Outputs

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	Set the type of Output process to run. Discover available Output types in our Logic Components: Input & Output Types article.

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

Set the type of Output process to run. Discover available Output types in our Logic Components: Input & Output Types article.

Conditionals

The Conditionals table in UDesigner replaces the Micro Decisions table from Classic Designer. They are functionally the same.

The Conditionals table is where you set if/then rules using your defined inputs and outputs. Inputs display in the left columns of the Conditionals table. The column headers match the Input components' Property IDs. Outputs display in the right columns and are named using a concatenation of their ID and Type.

The Conditionals table begins in an empty state until Inputs and Outputs are implemented.

Setting	Description
Input Values (Left Columns)	Shows a column for each input component. The component's Property ID serves as the header for the column. Using the firstrow, enter the trigger value the logic component uses when triggering the output. By default, Date Input components store dates in ISO 8601 format with a timestamp of midnight UTC. For example, 2020-11-13T00:00:00Z. When referencing input values from a Date Input component, you must also use ISO 8601 format. The exception is when the Date Input component has Store Date Only enabled, in which case the date stores without a timestamp. A blank value/nothing in the Input column acts as a catch-all for any Input values not otherwise defined.
Output Values (Right Columns)	Shows a column for each output component. A concatenation of the component's Property ID and the Type serves as the header for each column. Using first row onward, define the behavior based on the Type. For example, _visible: yes/no.

Setting

Description

Input Values
(Left Columns)

Shows a column for each input component. The component's Property ID serves as the header for the column. Using the firstrow, enter the trigger value the logic component uses when triggering the output.

By default, Date Input components store dates in ISO 8601 format with a timestamp of midnight UTC. For example, 2020-11-13T00:00:00Z. When referencing input values from a Date Input component, you must also use ISO 8601 format. The exception is when the Date Input component has Store Date Only enabled, in which case the date stores without a timestamp.

A blank value/nothing in the Input column acts as a catch-all for any Input values not otherwise defined.

Output Values
(Right Columns)

Shows a column for each output component. A concatenation of the component's Property ID and the Type serves as the header for each column. Using first row onward, define the behavior based on the Type. For example, _visible: yes/no.

Advanced Panel

Set Execution

Setting	Description
Set Execution	Select if and what is executed when this component triggers.
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).
Execute All Child Decisions	When set to (ON), triggers all child Decisions associated with this Decisions component. By default, Execute All Child Decisions is set to (OFF).
Execute Decisions From Last To First	Reverses the trigger order of child decisions. When set to (ON), child decisions trigger from last to first.
Set Debounce	The number of milliseconds that pass before the form loads this component. For larger modules, increasing the debounce value prevents the Decisions component from triggering before all components load in.

Adding a Decisions Component

In this scenario, you'll show a follow-up question when an end-user answers No to "Are you a citizen of the United States?" These instructions assume that you have an open module saved with a title.

Configure the Radio Buttons Component

This component asks the end-user if they're a citizen of the United States. If the end-user answers Yes, this is the end of the process. If the end-user answers No, the process continues. This Radio Button is the input for your Decisions component's if/then rule.

Drag and drop a Radio Buttons icon

Radio Buttons component 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. field, enter citizenCheck.

In the Label Text field, enter Are you a citizen of the United States?.

Click

Data.

Complete the Values table as follows:

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

From the component's configuration window, click Actions Icon

Actions.

In the Trigger field, enter ruleCitizen. You'll set up this component in a later step.

Click Save Component.

Configure the Text Field Component

This component stays hidden until the end-user answers No to the question. After selecting No, the Text Field displays, and the end-user can add their country of citizenship. This Text Field is the output for your Decisions component's if/then rule.

Drag and drop a

Text Field component onto your canvas, placing it below the citizenCheck Radio Buttons icon

Radio Buttons component.

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

In the Label Text field, enter If no, what country?.

Under Default State Options, set Hide Field to (ON).

Click Save Component.

Configure the Decisions Component

Your Decisions component holds the logic behind your if/then rule. In this example, if the end-user selects No in the Radio Buttons component, then the Text Field component displays.

Drag and drop a Decisions Component icon

Decisions component onto your canvas, placing it below the whatCountry

Text Field component.

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

In the Canvas Label Text 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 . field, enter ruleCitizen.

Navigate to the Decisions Component icon

Decisions component's Actions settings.

Next to Inputs & Outputs, click Edit.

Complete the Inputs table as follows:

	Property ID	Alias	Type
1	areYouACitizen		exact

Setting an output Type of exact lets you use exact values in the Micro Decisions table. Exact is a good option because there are only two possible values from the Radio Buttons component: yes and no.

Complete the Outputs table as follows:

	Property ID	Type
1	whatCountry	visible

Setting an output Type of visible lets you hide or display the field referenced in the Property ID column. So, your Text Field displays or hides based on the end-user's Radio Buttons selection. You'll set this up in the Micro Decisions table.

Under Conditionals, click the Add New Row button two times. This creates a two row table using the Inputs and Outputs values as headers.

Complete the Conditionals table as follows:

	citizenCheck	whatCountry_visible
1	no	yes
2		no

10.

Click Save Component.

11.

Save your module.

Preview your module in Express View Express View is how your end-user views you 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., and test it out:

Resources

Overview

Three inputs drive the Decisions component:

Input component: What drives the action. Any component works here, including Buttons, Radio Buttons, or Text Fields. The Decisions references the Property ID A Property ID is the unique field ID used by Unqork to track and link components in your module. of the input component.
Output component: What reacts to the action. Again, any component works, including Panels and Field-Groups containing multiple components. The Decisions references the Property ID of the output component.
Decisions component: The Decision itself. You can configure the interaction between the inputs and outputs using Micro Decisions. You can set the input and output behavior by selecting the Type for each. The Micro Decisions table is where you'll set if/then rules using your defined inputs and outputs. Inputs display in the left columns of the Micro Decisions table. The column headers match the Input components' Property IDs. Outputs display in the right columns and are named using a concatenation of their ID and Type.

Here are some real-world examples of when to use a Decisions component:

Displaying a Country of Citizenship field after your end-user answers that they're not a U.S. citizen.
Showing state-specific question labels, based on your end-user's selected state of residence.
Adjusting a maximum loan amount based on your end-user's calculated credit score.
Displaying a field with the click of a button.

You can find the Decisions component in the Data & Events Processing group to the left of the Module Builder.

What You'll Learn

After completing this article, you’ll know when to use a Decisions component, how to configure its settings, and how to use it in a module.

About the Configuration Window

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.