...
Attribute | Description | ||
---|---|---|---|
Visibility Type | It determines whether a component is visible on the layout. It offers the following visibility types:
Note: By default,
| ||
Read Only Type | It specifies whether a component can be edited by users. It offers the following options:
|
Base UI:
...
Include Page | ||||
---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
...
Label Source Type Attribute | Description |
---|---|
Static | It includes only records from the manually input value. |
Model (Salesforce Object) | From this source, users can select a Model (Salesforce Object)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 | 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. |
User | Here, you can choose the label from user fields such as First Name, Last Name, Email, Name, Phone, or Session ID. |
...
Include Page | ||||
---|---|---|---|---|
|
Events:
In noKodr, Events define the triggers for automation created by workflows. They determine when a specific workflow should be executed based on user interactions or changes in the application.
...
onload Events:
This triggers the assigned workflow every time the component is loaded.
...
Include Page | ||||
---|---|---|---|---|
|
Custom Action Event:
This event changes as you create new actions for the component. For example, in the image below, I have created a custom action called “New Candidate.” The event associated with this action is visible, which means that whenever you click on this action, the assigned workflow will be triggered.
...