Overview

Button Groups organize multiple buttons into a single unit, presenting them in a neatly arranged horizontal series. This grouping includes various button styles, such as basic buttons, icon-based buttons, and other design variations.

Buttons are essential interactive elements in the user interface, designed to trigger specific actions when clicked by the user. They facilitate various functions, such as submitting forms, navigating between pages, or executing commands.

For example, In a Salesforce custom application for managing customer support tickets, you might use a Button Group on the ticket detail page to streamline common actions. This Button Group could include custom buttons like "Assign to Me," "Escalate," and "Add Comment."

Assign to Me: Allows a support agent to quickly take ownership of the ticket.
Escalate: Moves the ticket to a higher priority or another support level.
Add Comment: Lets the agent add notes or updates to the ticket.

Basic Attributes:

Attributes are the options available for each component, allowing you to customize its appearance and functionality. They help you tailor the look and behavior of your components to fit your needs.

Attribute Name

Description

Actions

You can include multiple actions, each displayed as a button. Clicking a button initiates a specific action or workflow.
You have the option to add multiple actions. To create a new action, simply click on the + icon.

Note: After creating the action, it will be displayed on the canvas.

Reference: Button Action

Overflow After

This feature allows you to control the number of actions displayed. Setting the limit to 1 will show only one action, with additional actions appearing in a drop-down menu.

Alignment

Here, you can adjust the button alignment.

Left Alignment: The buttons will be aligned to the left side of the section where they are placed.
Center Alignment: The buttons will be aligned to centre of the section.
Right Alignment: The buttons will be aligned to the right side of the section.

UI Attributes:

Attribute Group	Attribute Name	Description
UI	Component Size	This allows users to modify the size of a Button within the layout according to the grid size. This feature allows for flexible customization, enabling users to resize components to fit their specific needs within the defined grid structure. Note: Currently, we support Component Size 1 for Section. All other sizes will throw an error alert displaying Max allowed value is 1.
	Margin Location	"Margin Location" refers to the spacing around the outside edge of an Button
	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. You can explore more about Styles attribute
	Classes	It is used to apply SLDS classes to section, if needed.

Visibility and Components:

Attribute Group

Attribute Name

Description

Visibility

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 attribute.

Component

Component Label

It simply shows the name of the component.

Button Action:

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. You can explore more about Visibility Type attribute
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 attribute.

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.

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 Event:

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

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.