Overview
A Picklist is a UI element that provides users with a predefined list of options from which they can select values. It simplifies data entry by limiting choices to a set list.
Attributes of Picklist Field
Basic:
Attribute Name | Description |
---|---|
Component Size |
For example, |
Display as | Display As allows you to select data type options to define how the field will be display. For example, if you have a text field and choose to display it as a picklist, the data will be stored as text but displayed as a picklist. |
Label | Here user can set the label name for picklist. It can be come from various sources. Reference: Label Source Type |
Place holder | This is a hint or example text displayed in an input field before the user enters their own data. |
Type | Here you can choose different field types. Reference: Field Type. |
Dest Types | This attribute specifies whether the user wants to store a value in a variable or a model. Model: Here, the user can select the model and specify the field where the value will be stored. |
Dest Var | Here you can choose the variable option from variable list. Note: This appears when you select "Variable" in the Dest Type. |
Dest Model | Here you can choose the model from list. or it provide option for new model creation. Note: This appears when you select "Model" in the Dest Type. Reference: How to Create a Record Type Model |
Layout | Field Layout allows you to arrange fields on the form. |
Config:
Attribute Name | Description |
---|---|
Help Text | Provides additional guidance or information about a field or element to assist users in understanding how to complete it or what data is expected. |
Picklist Type | Here user can select the type for picklist as Value or none. |
Picklist Values | Here, users can add new picklist values by adding Key and values. |
Is Page Size Options | Enabling this checkbox displays the page size options. |
Hide Search | Enabling this checkbox allows the user to hide the search bar of picklist field. |
Is Dependent | Enabling this checkbox sets the picklist as a dependent picklist. |
Show Drop Down Up | Enabling the checkbox displays the drop-down menu above the picklist. |
Hide Select Icon | Enabling this checkbox hides the select icon. |
Option Limit | Users can set the picklist display limit to 5, 7, or 10 items. |
Base UI:
Attribute Name | Description |
---|---|
Margin Location | "Margin Location" refers to the spacing around the outside edge of an element |
Margin Size | "Margin Size" refers to the amount of space around the outside edges of an element, |
Style |
|
Classes |
|
Hide Space Checkbox | After marking this checkbox as true, it will crop the extra corners of the fields. |
Validations:
Attribute Name | Description |
---|---|
Required Type | You can make the field required by setting the required type.
|
Required Error | Users can add a custom error message for the required field. |
UI State:
Attribute Name | Description |
---|---|
Visibility Type | It determines whether a component is visible on the layout. It offers the following visibility types:
Reference: Conditional Visibility |
Read Only:
Attribute Name | Description |
---|---|
Read Only Type | It specifies whether a component can be edited by users. It offers the following options:
Reference: Read Only |
Conditional Disability:
Attribute Name | Description |
---|---|
Disability Type | It determines whether a component is disable on the layout. It offers the following visibility types:
Reference: Conditional Disability |
UI:
Attribute Name | Description |
---|---|
Layout | Field Layout allows you to arrange fields on the form. Reference: Field Layout |
Help Text | Provides additional guidance or information about a field or element to assist users in understanding how to complete it or what data is expected. |
Field Layout:
Attributes | Description |
---|---|
None | In the None layout, only the input/output field is visible, with no label displayed. |
Stacked | In a stacked layout, the input/output field is placed below the field label, with a small margin around the label. |
Horizontal | In a horizontal arrangement, the input/output field is placed before the field label, with a small margin around the label. |
Single Column | In a Single Column layout, the input/output field is larger than the field label, and displayed in single column grid. |
No Label | In the No Label layout, only the input/output field is visible, without the label. |
Label Source Type:
Attribute | Description |
---|---|
Model | From this source, users can select a Model field to be displayed as the label name. |
Variable | Here, users can select the label name from variables such as Record ID, Is Disabled, Is Read only, or Is Visible. |
Cookie Key | Choose the available cookie key whose value you want to include from your browser. |
Local Storage Key | Select the available Local Storage Key whose value you want to include from your browser. |
User | Here, you can choose the label from user fields such as First Name, Last Name, Email, Name, Phone, or Session ID. |
Merge Field Expression | Merge Field Expression displays the value selected from the chosen value source. |
Message Body | Inside the message body, user also can add the values manually. |
Conditional Visibility Type:
Attributes Name | Description |
---|---|
Destination Type | Users can select the destination type where the visibility criteria must be applied. Reference: Destination Type |
Operator | Here, users can select different operators to add filters. Reference: Filter Operator. |
Source Type | Here, you can select the source type from various sources. |
Value | Here user can select the value from different Source Type. Reference: Merge Text |
Destination Type
Destination Type | Description |
---|---|
Model | From this source, users can select a Model field to be displayed as the destination type. |
Variable | Here, users can select the destination type from variables such as Record ID, Is Disabled, Is Read only, or Is Visible. |
User | Here, you can choose the label from user fields such as First Name, Last Name, Email, Name, Phone, or Session ID. |
Record | It enables to choose record fields as destination type. |
Device | It enables user to decide whether the action will be visible on the specific device type or not. Devices supported:
|
Conditional Disability Type:
Attributes Name | Description |
---|---|
Destination Type | Users can select the destination type from various sources. Reference: Destination Type |
Operator | Here, users can select different operators to add filters. Reference: Filter Operator. |
Source Type | Here, you can select the source type from various sources. |
Value | Here user can select the value from different Source Type. Reference: Merge Text |
Conditional Read Only:
Attribute Name | Description |
Read Only Type | It specifies whether a component can be edited by users. It offers the following options:
|
Add Condition & Group Condition
Condition | Description |
---|---|
Add Condition |
|
Add Group Condition |
|
Filter Operator:
Note: Before using the filter criteria, it's important to understand which filter operators are supported for each field type
Filters Attributes:
Filter Operators
Operator | Supported Field Types | Description |
---|---|---|
Equal | Number, Currency, Date, Text, Boolean, Picklist | The equal operator is used to compare two values or expressions. It is used to compare numbers, strings, Boolean values, variables, objects, etc. The result is TRUE if the expressions are equal otherwise it’s FALSE |
Contains | Text, Picklist | The contains operator returns TRUE if the value on the left contains the value on the right, and otherwise FALSE |
Starts With | Text, Picklist | It returns TRUE if a string or number starts with the specified character otherwise it returns FALSE. |
Ends With | Text, Picklist | It returns TRUE if a string or number ends with the specified character otherwise it returns FALSE |
In | Text, Picklist | IN operator allows you to easily test if the expression matches any value in the list of values. Determines whether the value of an expression is equal to any of several values in a specified list. |
Events:
Events are essentially the automation of invoking the component's actions.
Here, we have onload event, click, double click actions are available for this components.
Icon Events | Description |
---|---|
onload | This event action is triggered when the Field component is loaded. |
change | This event action is triggered when the field is changed.. |
blur |
Below here is the onload event workflow action.
Note: Similarly you can create event action for change event and blur.
on Load Event:
In the image below, you can select the created workflows.
Note: You need to create a workflow for selecting from this list.
For more information about Workflow check this out.
Reference: Workflow
onload Events:
We have an onload event that runs when the component is loaded
For example, when a form is loaded, you can choose fields to be prepopulated by mapping field values using input mapping at the time the form component is loaded.
Input Mapping
Input Mapping: "Whenever an event is triggered and you want to pass data to destinations such as models, variables, or components, you can use input mapping to achieve that.
Add Comment