[Quickstart] Add history models

.quickstart/quickstart.yml

@@ -11,6 +11,10 @@ table_variables:
   workday__using_personal_info_v2_schema:
     - personal_information_common_data
     - country_personal_information
+  employee_history_enabled:
+    - worker_history
+    - worker_position_history
+    - personal_information_history
 
   _fivetran_quickstart_person_name:
     - person_name
@@ -49,5 +53,15 @@ public_models: [
   "workday__employee_overview",
   "workday__job_overview",
   "workday__position_overview",
-  "workday__organization_overview"
+  "workday__organization_overview",
+  "workday__employee_daily_history",
+  "workday__monthly_summary",
+  "workday__worker_position_org_daily_history"
 ]
+
+supported_vars:
+  employee_history_start_date:
+    type: date
+    value: "2025-03-01"
+    description: "Set the first date for bringing in employee history data."
+    display_name: "Employee History Start Date"

CHANGELOG.md

@@ -1,3 +1,11 @@
+# dbt_workday v0.8.2
+
+## Feature Updates
+- Updates the `quickstart.yml`:
+  - Adds `workday__employee_daily_history`, `workday__monthly_summary`, and `workday__worker_position_org_daily_history` to the list of public models.
+  - Adds `supported_vars` entry for `employee_history_start_date` to allow users to configure the employee history start date in Quickstart.
+  - Adds `employee_history_enabled` table variables for `worker_history`, `worker_position_history`, and `personal_information_history` to prevent missing sources from blocking downstream Quickstart models.
+
 # dbt_workday v0.8.1
 
 [PR #26](https://github.com/fivetran/dbt_workday/pull/26) includes the following updates:

README.md

@@ -109,7 +109,10 @@ To connect your multiple schema/database sources to the package models, follow t
 If you have History Mode enabled for your Workday HCM connection, we now include support for the worker, worker position, worker position organization, and personal information tables directly. You can view these files in the [`staging`](https://github.com/fivetran/dbt_workday/blob/main/models/workday_history/staging) folder. This staging data then flows into the employee daily history model, which in turn populates the monthly summary model. This will allow you access to your historical data for these tables for the most accurate record of your data over time.
 
 #### Enabling Workday HCM History Mode Models
-The History Mode models can get quite expansive since it will take in **ALL** historical records, so we've disabled them by default. You can enable the history models you'd like to utilize by adding the below variable configurations within your `dbt_project.yml` file for the equivalent models.
+The History Mode models can get quite expansive since it will take in **ALL** historical records, so we've disabled them by default. You can enable the history models you'd like to utilize by adding the below variable configurations:
+
+- In Quickstart, by syncing the `worker_history`, `worker_position_history`, and `personal_information_history` tables.
+- In dbt Core, within your `dbt_project.yml` file.
 
 ```yml
 # dbt_project.yml
@@ -122,14 +125,19 @@ vars:
 #### Filter your Workday HCM History Mode models
 By default, these history models are set to bring in all your data from Workday HCM History, but you may be interested in bringing in only a smaller sample of historical records, given the relative size of the Workday HCM history source tables. By default, the package will use the minimum `_fivetran_start` date for the historical end models. This default may be overwritten to your liking by leveraging the below variable.
 
-We have set up where conditions in our staging models to allow you to bring in only the data you need to run in. You can set a global history filter that would apply to all of our staging history models in your `dbt_project.yml`:
+We have set up where conditions in our staging models to allow you to bring in only the data you need to run in. You can set a global history filter that would apply to all of our staging history models:
+
+- In your Quickstart Settings tab, by configuring the `Employee History Start Date` variable.
+- In dbt Core, in your `dbt_project.yml`:
 
 ```yml 
 vars:
     employee_history_start_date: 'YYYY-MM-DD' # The first `_fivetran_start` date you'd like to filter data on in all your history models.
 ```
 
-The default date value in our models is set at `2005-03-01` (the month Workday was founded), designed for if you want to capture all available data by default. If you choose to set a custom date value as outlined above, these models will take the greater of either this value or the minimum `_fivetran_start` date in the source data. They will then be used for creating the first dates available with historical data in your daily history models.
+In dbt Core, the default date value in our models is set at `2005-03-01` (the month Workday was founded), designed for if you want to capture all available data by default. If you choose to set a custom date value as outlined above, these models will take the greater of either this value or the minimum `_fivetran_start` date in the source data. They will then be used for creating the first dates available with historical data in your daily history models.
+
+For Quickstart users, this variable is available as **Employee History Start Date** in the Quickstart Settings tab. The default value is `2025-03-01`, bringing in data from the last year to ensure your first Quickstart run has recent correct data. Set a different date to increase or reduce the volume of historical records the package processes.
 
 ### (Optional) Additional configurations
 
@@ -183,8 +191,6 @@ vars:
   workday__using_personal_info_v2_schema: false  # To leverage old schema. Default is currently true
 ```
 
-</details>
-
 ### (Optional) Orchestrate your models with Fivetran Transformations for dbt Core™
 <details><summary>Expand for details</summary>
 <br>

dbt_project.yml

@@ -1,6 +1,6 @@
 config-version: 2
 name: 'workday'
-version: '0.8.1'
+version: '0.8.2'
 require-dbt-version: [">=1.3.0", "<3.0.0"]
 
 models:

integration_tests/dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'workday_integration_tests'
-version: '0.8.1'
+version: '0.8.2'
 config-version: 2
 
 profile: 'integration_tests'