Understanding Application and Record Layouts
Layout Creation
In this section, you will learn what information is needed to create a layout, including:
Attribute | Description |
---|---|
Label | Allows to specify the label or name for the layout. |
Name | Allows to provide a unique API name for the layout. |
Type | Allows to specify the layout type:
|
Object | Allows to select the object that will be associated with the layout. Notes:
|
Layout Type:
In this section, you will learn about the two distinct types of layouts:
Type | Application Layout | Record Layout |
---|---|---|
Purpose | Allows building applications that do not require record IDs for execution. | Allows building applications that require record IDs for execution. |
Usage | Once you structure and publish an Application Layout, you can add it to:
| After structuring and publishing the layout, you can add it to:
Note: When creating a Record Layout, you need to select the associated object. |
Difference Between Application and Record Type Layouts
Type | Application Layout | Record Layout |
---|---|---|
Form Component with Predefined Actions | Does not include any predefined components. | The form component includes default action buttons such as:
|
Model | Does not include any predefined models. | Provides a record model for the selected object, allowing you to:
|
Variables | Does not include any predefined variables. | Lists variables that can be used to store temporary values. |
Workflows | Does not include any predefined workflows. | Predefined workflows:
|
Events | Does not include any predefined events. | This includes several events for communicating with other layouts, such as:
|
Note: These predefined elements are locked and cannot be modified or deleted. They are provided as references to help you create new elements or you can use this template with some modifications, such as adding the required fields to the form, tailored to your needs.