Overview

The Calendar component provides three viewing options: Monthly, Weekly, and Daily. This flexibility allows users to navigate and manage their schedules according to their preferences.

By default, the Calendar highlights today’s date, making it easy for users to focus on the current day’s activities. This feature helps ensure that important dates and tasks are not overlooked.

Additionally, users can save records directly within the Calendar component. This functionality enables seamless tracking and management of events, tasks, or appointments across different time frames. By consolidating important dates and activities in one location, the Calendar helps users stay organized and efficiently manage their schedules.

Notes:

Click the Calendar icon to view the date, month, and year in calendar format. Use the Month drop-down menu to select between Month, Week, and Day views.
You need to create workflows for the New and Refresh buttons of the Calendar component. A workflow is a container that automates specific actions based on defined criteria. If the criteria are met, the actions will be executed otherwise, no action will occur.
You can create a new record by using New Action and for the record creation, click on the New button.

Reference: Workflow

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.

Basic:

Attribute Name

Description

Component Size

This allows users to modify the size of a specific component according to the grid size of layout.
This feature allows for flexible customization, enabling users to resize components to fit their specific needs within the defined grid structure.

For example, if the layout grid size is 3 then layout is divided into 3 sections then you can changes the components size between 1 to 3.

Model

Models are essential for displaying content (fields) in the layout, and they are primarily used for creating or editing records.
When performing any action related to events, you need to include a model to ensure proper functionality.
Detailed guidance on creating and configuring these models can be found in the Models section, which provides the necessary support for setting up and using models appropriately.

Note: Specifically, for the Calendar component, you should create a Multi Record Model to manage and display multiple records effectively.

Reference: Calendar Model Setup

Base UI:

Attribute Name	Description
Margin Location	"Margin Location" refers to the spacing around the outside edge of an element
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.
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:

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.

Reference: Conditional Visibility

Calendar Model Setup:

Calendar Model Attributes	Description
Model	Here, you can choose an existing record or create a new model to create a new model, refer the below link Reference: Model Creation
Date Field	The date field represents the date selected from the calendar.
Label Field	The label field represents the text label that is specified or selected for display.
Class	Here, users can enter the name of the class.

Conditional Visibility Type:

Attributes Name	Description
Destination Type	Users can select the destination type where the visibility criteria must be applied. Reference: Destination Type
Operator	Here, users can select different operators to add filters. Reference: Filter Operator.
Source Type	Here, you can select the source type from various sources.
Value	Here user can select the value from different Source Type. Reference: Merge Text

Destination Type

Destination Type	Description
Model	From this source, users can select a Model field to be displayed as the destination type.
Variable	Here, users can select the destination type from variables such as Record ID, Is Disabled, Is Read only, or Is Visible.
User	Here, you can choose the label from user fields such as First Name, Last Name, Email, Name, Phone, or Session ID.
Record	It enables to choose record fields as destination type.
Device	It enables user to decide whether the action will be visible on the specific device type or not. Devices supported: Mobile Desktop Tablet

Conditional Disability Type:

Attributes Name	Description
Destination Type	Users can select the destination type from various sources. Reference: Destination Type
Operator	Here, users can select different operators to add filters. Reference: Filter Operator.
Source Type	Here, you can select the source type from various sources. Reference: Available Sources.
Value	Here user can select the value from different Source Type. Reference: Merge Text

Conditional Read Only:

Attribute Name

Description

Read Only Type

It specifies whether a component can be edited by users. It offers the following options:

Never: The component will always be editable at any time.
Always: The component will never be editable.
Conditional: The component's editability is determined based on specific criteria, which can make it either editable or read only as needed.

Add Condition & Group Condition

Condition	Description
Add Condition	The Add Condition feature allows users to define multiple criteria that must be met for a validation rule to trigger. This feature is used to create complex logic by combining different conditions that Salesforce evaluates before allowing a record to be saved.
Add Group Condition	The Add Group Condition feature allows users to group multiple conditions together, creating complex logic that involves different sets of criteria. This feature is particularly useful when combining conditions that should be evaluated as a unit (logical OR within a group) or when nesting conditions for more advanced logic.

Filter Operator:

Note: Before using the filter criteria, it's important to understand which filter operators are supported for each field type

Filters Attributes:

Filter Operators

Operator	Supported Field Types	Description
Equal	Number, Currency, Date, Text, Boolean, Picklist	The equal operator is used to compare two values or expressions. It is used to compare numbers, strings, Boolean values, variables, objects, etc. The result is TRUE if the expressions are equal otherwise it’s FALSE
Contains	Text, Picklist	The contains operator returns TRUE if the value on the left contains the value on the right, and otherwise FALSE
Starts With	Text, Picklist	It returns TRUE if a string or number starts with the specified character otherwise it returns FALSE.
Ends With	Text, Picklist	It returns TRUE if a string or number ends with the specified character otherwise it returns FALSE
In	Text, Picklist	IN operator allows you to easily test if the expression matches any value in the list of values. Determines whether the value of an expression is equal to any of several values in a specified list.

Events:

Events are essentially the automation of invoking the component's actions.
Here, we have onload event, new event, select event actions are available for this components.

Calendar Events	Description
onload	This event action is triggered when the component is loaded.
new	This event action is triggered when the new record is created.
Select	This event action is triggered when the calendar date is selected.

Note: You need to create workflows for the New and Refresh buttons of the calendar component.

Below here is the onload event workflow action.

Note: Similarly you can create event action for new event, select events.

on Load Event:

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 set as `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.
Operator	It is specifically operator value such as Set, Equals, Greater than, Equals than.
Source Type	In this option, you can select various sources from which you want to display values. Reference: Source Type Note: By default, the `Source Type` is set as `Static`.
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.

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 as `Source`.
Output Variable	Select from the output variables created in the layout whose value you want to use as `Source`.
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.