As mentioned earlier, each holiday that you want to honor will be represented by an individual Record in a Holiday Provider App.

To get started, create a new App named Holiday Provider that contains the following Fields:

1. holiday_date (date, required)  Specifies the date of the holiday. A required Field.
2. calendar_name (combo, required)  Specifies which calendar the holiday should fall under. The values of the combo should represent specific calendars (e.g., 2019 US Holidays, 2020 US Holidays). For example, let’s say that you have an office in the United States and the United Kingdom. Some holidays, like Independence Day, should only be listed the US calendar, to prevent incorrect date calculation for your UK office.

3. active (checkbox)  Represents if the holiday is active or inactive. This checkbox should be given an initial value of true.

4. In most cases, we recommend that you hide both the pre-created requester_name and requester_emails Fields, as they are not important to this configuration.
5. Repurpose the pre-created name Field by changing its label to Holiday Name.

Next, perform the following set up tasks:

1. From any App’s Advanced Designer sidebar, navigate to the Holiday Provider node.

2. Click the Holiday Provider node and click the plus button to create a new provider.

3. Configure the new provider as follows:

• Name: Enter a name for the provider. We recommend using simply Holiday Provider.
• Apps: Select the App that you just created named Holiday Provider.

• Holiday Date Mapping: Select Holiday Date (holiday_date). This identifies the Field in your App that will contain the date of the holiday.
• Holiday Name Mapping: Select Holiday Name (name). This identifies the Field in your App that will contain the name of the holiday.
• Calendar Name Mapping: Select Calendar Name (calendar_name). This identifies the Field in your App that will contain the date of the calendar that holiday lives within.
• Active/Inactive Mapping: Select Active (active). This identifies the Field in your App that indicates whether or not a holiday is active. Note that this setting is optional: if you leave it blank, all holidays will be used whether set as active or not.

• Enabled?: Check this box to enable the provider.

Your Holiday Provider App is now fully set up! Before you can use it, be sure to create some Records in the App, each of which will represent holidays.

Below is a screenshot of a Dashboard for a Holiday App that contains a series of holiday Records.

Any of the following Liquid expressions will honor holidays defined in a Holiday Provider App:

• add_business_days
• calculate_business_days
• subtract_business_days

For example, let’s say that you had a holiday of July 4, 2019 defined in your Holiday Provider App. Based on this holiday, you could run the following Liquid expression:

{% assign baseline_date = "2020-07-01" | to_date %}

{{ baseline_date | add_business_days: 25, "2020 US Holidays" }}

The outputted value would be 2020-08-05.

In this example, the arguments passed into the Liquid expression are as follows:

• 7/1/2020 is the baseline date that you want to add to. This can be defined as a hard-coded date (as seen above), or via a date Field in an App, or view the now keyword.
• 25 is the number of business days that you want to add to the baseline date.
• 2020 US Holidays is the name of the calendar within which you want the Liquid expression to check.

You can designate the Holiday Provider App as a Transaction List Provider. Doing so allows you to perform list lookups into the Holiday Provider App to determine if any given date falls on a holiday. For example:

{% capture conflict_check %}

{{ event_date | date:"%m/%d/%Y" | list_lookup: 'Holiday Provider', 'holiday_date', 'name' }}

{% endcapture %}

{% if conflict_check != blank %}The date you have selected conflicts with {{conflict_check}}

{% break %}

{% else %}No conflict

{% endif %}