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 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. Note: It is invisible until you fill above 2 mapping fields. |
Operator | It is specifically operator value such as Set, Equals, Greater than, Equals than. Note: It is disabled until you fill above 3 mapping fields. |
Source Type | In this option, you can select various sources from which you want to display values. Reference: Source Type Note:
|
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. Note: It is disabled until you fill above 3 mapping fields. |
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. |
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. |
Add Comment