Overview

The Form component is a normal form used to input, create, edit, and view records from objects or external services. To utilize its functionality, the Form must be associated with a model. Once a model is assigned, the fields will appear on the left side of the interface, allowing you to drag and drop them into the Form. Additionally, multiple actions can be added to the Form for enhanced functionality.

Attributes

Attributes are the options available for each component, allowing you to customize its appearance and control their behavior. It includes various sections explained below.

Basic:

Attribute Name	Description
Component Size	This allows users to modify the size of a specific component according to the grid size of layout. This feature allows for flexible customization, enabling users to resize components to fit their specific needs within the defined grid structure. For example, If the layout grid size is 3 then layout is divided into 3 sections then you can changes the components size between 1 to 3.
Layout Type	It is used to set the layout type in two ways as: Grid: The Grid Layout Type provides a grid-based layout system consisting of rows and columns. This layout simplifies the process of designing and structuring a layout, allowing for precise placement and alignment of components within the grid. Flow: The Flow Layout Type is used for positioning and formatting components within a layout. This layout type allows components to be positioned in relation to each other. Note: By default, this attribute is set to a value of Grid Layout Type.
Grid Size	It defines the width of the component in terms of grid columns, allowing users to control how much horizontal space the section occupies on the page.
Model	All the Models (Salesforce Object) you have created will appear in the list. You can select a specific model from the list to save and display its field values. Note: Only one model (Record Type - Single) can be bound at a time.
Field Layout	Field Layout allows you to arrange fields on the form. For more details check this Reference: Field Layout
No Action Bar	If the "No Action Bar" checkbox is selected, the action bar, which contains all associated actions for the form, will be hidden.
Action	You can include multiple actions, each displayed as a button. Clicking a button initiates a specific action or workflow. Note: After creating the action, it will be displayed on the canvas. Reference: Action
Primary Actions	You can select a primary action from the available actions. Pressing the Enter key will execute this selected action.
Overflow After	If the number of actions exceeds the provided limit, the additional actions will be displayed in a dropdown. For example, if you have 3 actions, all will be displayed in the section header. If you added the 4th action, it will appear in the drop-down list, along with any subsequent actions.

UI Attributes:

Attribute Name	Description
Padding Location	Padding Location typically refers to the configuration of spacing around elements.
Padding Size	Padding Size refers to the amount of space added inside an element, between the element's content and its border or edge.
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	It is used to apply custom styles to section, such as color, font, size, and more. It allows you to define the appearance of a component by specifying CSS properties directly within the attribute.
Classes	It is used to apply SLDS classes to component, if needed.
Flow Type	It specifies the arrangement of content within the section, allowing users to choose between different layout flows as ‘Fit to content’ or ‘Equally distributed’.
Show Border	It is used to simply add border surrounding the section. Note: Currently, noKodr supports only black borders.

UI State:

Attribute Name

Description

Visibility Type

It determines whether a component is visible on the layout. It offers the following visibility types:

Always: The component will always be visible.
Conditional: The component's visibility is determined based on specific criteria, which can make it either visible or hidden as needed.
You can explore more about Visibility Type here.

Reference: Conditional Visibility.

Read Only Type

It specifies whether a component can be edited by users. It offers the following options:

Never: The component will always be editable at any time.
Always: The component will never be editable.
Conditional: The component's editability is determined based on specific criteria, which can make it either editable or read only as needed.
You can explore more about Read Only here.

Reference: Read Only

Disability Type

It determines whether a component is disable on the layout. It offers the following visibility types:

Never: There is no disable option for this component
Always: The component will always be visible.
Conditional: The component's visibility is determined based on specific criteria, which can make it either visible or hidden as needed.
You can explore more about Visibility Type.

Reference: Condition Disability.

Field Layout Configuration

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.

Actions

Attributes	Description
Label	A Label is the name shown to users and can come from various sources. Reference: Label Source Type
Name	Enter a unique the name for your action.
Icon	This option lets you choose from various icons to add to the action button.
Variant	This feature allows users to change the appearance of the action button. Neutral Brand Outline Brand Success Destructive
Visibility Type	It determines whether a component is visible on the layout. It offers the following visibility types: Always: The component will always be visible. Conditional: The component's visibility is determined based on specific criteria, which can make it either visible or hidden as needed.
Disability Type	It determines whether a component is disable on the layout. It offers the following visibility types: Never: There is no disable option for this component Always: The component will always be visible. Conditional: The component's visibility is determined based on specific criteria, which can make it either visible or hidden as needed.

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. Reference: Variable
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.

Note: After adding fields to the form, you can configure specific fields. The table below shows all available attributes.

Form Fields Attributes

Basic:

Attribute Name	Description
Component Size	This allows users to modify the size of a specific component according to the grid size of layout. This feature allows for flexible customization, enabling users to resize components to fit their specific needs within the defined grid structure. For example, If the layout grid size is 3 then layout is divided into 3 sections then you can changes the components size between 1 to 3.
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	A Label is the name shown to users and can 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.

UI :

Attribute Name	Description
Layout	Field Layout allows you to arrange fields on the form. For more details check this Reference: Field Layout
Is Copy Enabled	After marking the checkbox as true, a copy icon will appear beside the name field.
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.

Validation:

Attribute Name	Description
Required Type	Here, users can apply validation based on filter conditions. Never: This field is never required. Always: This field is always required.. Conditional: The required field is determined based on specific criteria of And, OR condition
Required Error	Enter the error message you want to display for required fields.
Minimum Length	Set the minimum number of characters required for the input field.
Min Length Error Message	Enter the error message to display if the input does not meet the required minimum length.
Maximum Length	Set the maximum number of characters allowed for the input field.
Max Length Error Message	Enter the error message to display if the input exceeds the maximum allowed length.
Pattern	A regex pattern or regular expression pattern, is a sequence of characters that defines a search pattern. It's used for pattern matching within strings, such as validating input, searching for specific text, or replacing text.
Pattern Error Message	A "Pattern Error Message" typically refers to an error generated when input data does not match the expected format defined by a regular expression pattern. This message is usually displayed to inform users that their input is invalid or incorrectly formatted.

UI State:

Attribute Name

Description

Visibility Type

It determines whether a component is visible on the layout. It offers the following visibility types:

Always: The component will always be visible.
Conditional: The component's visibility is determined based on specific criteria, which can make it either visible or hidden as needed.
You can explore more about Visibility Type.

Reference: Conditional Visibility.

Disability Type

It determines whether a component is disable on the layout. It offers the following visibility types:

Never: There is no disable option for this component
Always: The component will always be visible.
Conditional: The component's visibility is determined based on specific criteria, which can make it either visible or hidden as needed.
You can explore more about Visibility Type.

Reference: Conditional Disability

Read Only Type

It specifies whether a component can be edited by users. It offers the following options:

Never: The component will always be editable at any time.
Always: The component will never be editable.
Conditional: The component's editability is determined based on specific criteria, which can make it either editable or read only as needed.

Reference: Conditional Read Only

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	It is used to apply custom styles to section, such as color, font, size, and more. It allows you to define the appearance of a component by specifying CSS properties directly within the attribute.
Classes	It is used to apply SLDS classes to component, if needed.
Hide Space	After marking this checkbox as true, it will crop the extra corners of the fields.

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: Mobile Desktop Tablet

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. Reference: Available 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:

Never: The component will always be editable at any time.
Always: The component will never be editable.
Conditional: The component's editability is determined based on specific criteria, which can make it either editable or read only as needed.

Add Condition & Group Condition

Condition	Description
Add Condition	The Add Condition feature allows users to define multiple criteria that must be met for a validation rule to trigger. This feature is used to create complex logic by combining different conditions that Salesforce evaluates before allowing a record to be saved.
Add Group Condition	The Add Group Condition feature allows users to group multiple conditions together, creating complex logic that involves different sets of criteria. This feature is particularly useful when combining conditions that should be evaluated as a unit (logical OR within a group) or when nesting conditions for more advanced logic.

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, only onload event actions are available for this components.

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

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.

After clicking on Pencil icon, user can view the screen to set Input Mapping as follows:

After clicking on + button, user can set up input mapping using Input Mapping Screen as follows:

Condition	Description
Destination Type	It specifies the destination where the connector mapping is to be done. Reference: Destination Type Note: By default, the `Destination Type` is set as `Model`.
Model	It is specifically dependent on Destination Type one chooses. If you choose another Destination Type, you will get that field label here.
Note: Fields below this will only be enabled once user filled above two fields.
Field	After choosing the second condition field, you will get this field visible in modal. If you chose Model as second condition field, this will be field and if you chose variable as second field, there will be variable.
Operator	It is specifically operator value such as Set, Equals, Greater than, Equals than.
Source Type	In this option, you can select various sources from which you want to display values. Reference: Source Type Note: By default, the `Source Type` is set as `Static`.
Value	The available options will change depending on the selected source type. For example, if you choose "Static" as the source, you can provide a fixed static value.

Destination Type

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.
Input Variable	Here, users can select the input variable which they have created earlier.
Cookie key	By using the `Cookie Key`, the result is fetched by the value that has been added under the Cookie Key. But, have to make sure that the value that we are adding is from the Cookie Key value.
Local Storage Key	By using the `Local Storage Key`, the result is fetched by the value that has been added under the Local Storage Key. But, have to make sure that the value that we are adding is from the Local storage value.

Source Type

Source Type	Description
Static	Use this option to provide a fixed static value.
Field	Select the field from the chosen object in the model whose value you want to include.
Model	Choose the field from other models whose value you want to include.
Variable	Select from the variables created in the layout whose value you want to use as `Source`.
Output Variable	Select from the output variables created in the layout whose value you want to use as `Source`.
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	You can also select fields from the current logged-in user in your organization to include in the merge. Note: The User source refers to the currently logged-in user in your organization. This means that if you include the `First Name` field from the user, each time a different user logs in, they will see their own First Name displayed.
Null	It enables assign null value to the Destination Type field we chose.
Blank	It enables assign blank value to the Destination Type field we chose.