Page Header
Overview
The Page Header component in noKodr is used to define the title of a section and to serve as a container for other components within the layout. It can be positioned at the top of the layout, offering a clear and identifiable section title.
Title Display: The Page Header displays the name or title of the section in the top left corner of the layout, providing a clear identifier for users.
Container for Components: It acts as a container where you can drag and drop additional components, allowing for a structured and organized layout.
For example, in an application for managing project tasks, you might use the Page Header to title different sections such as Upcoming Tasks
, Completed Tasks
or Task Overview
.By placing this title at the top of each section, users can easily navigate and understand the context of the content below, while also using the header area to organize related components.
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 |
For example, |
Layout Type | It is used to set the layout type in two ways as:
Note: By default, this attribute is set to a value of |
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. |
Header | Name of the header which is displayed on the top left corner of the component. |
Sub Header | Sub Header is displayed above the Header in the layout. The size of the Sub Header is smaller than the Header. |
Icon |
|
Header Actions |
|
Overflow After | This feature allows you to control the number of actions displayed. Setting the limit to |
Base UI :
Attribute Name | Description |
---|---|
Padding Location |
|
Padding Size |
|
Margin Location | `Margin Location refers to the spacing around the outside edge of an element. |
Margin Size |
|
Style |
|
Classes | It is used to apply SLDS classes to section, if needed. |
UI State:
Attribute Name | Description |
Visibility Type | It determines whether a component is visible on the layout. It offers the following visibility types:
|
Read Only Type | It specifies whether a component can be edited by users. It offers the following options:
|
UI:
Attribute Name | Description |
No Body | When the checkbox is marked as true, the "Add to Component" section of the Page Header will be hidden. |
Header and sub Header Source Type:
Page Header Action:
Attributes | Description |
---|---|
Label | A Label is the name shown to users and can come from various sources. |
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.
|
Visibility Type | It determines whether a component is visible on the layout. It offers the following visibility types:
|
Disability Type | It determines whether a component is disable on the layout. It offers the following visibility types:
|
Is Bulk Action Checkbox | If the bulk action checkbox is marked as true, it enables users to perform bulk actions on the selected items. |
Minimum Record Count | The |
Label Source Type:
Attribute | Description |
---|---|
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 | 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. |
Column actions
Events