Summary

This session continued the Litify PTO cleanup for 2026 only. WFH was clarified as not leave and should not receive a Leave Type value. Calendar/source titles now use First L. - WFH for WFH/Remote rows unless the record is explicit PTO, and First L. - OOO for PTO/OOO rows.

Shipped

• Deployed Time_Off_Request__c.Outlook_Event_Title__c formula update. Final deploy id: 0AfUV000001WZID0A4.
• Targeted test class TimeOffRequestPolicyServiceTest ran 6 tests with 0 failures.
• Backfilled 176 approved 2026 legacy blank leave rows to Leave_Type__c = PTO using Bulk API job 750UV00000m6jq1YAA.
• Verified sample records:
  • Wedding for Will McKenzie now shows Will M. - OOO and was backfilled to PTO.
  • Adam McDonald Remote remains blank Leave Type and shows Adam M. - WFH.
  • Alex Blair blank WFH remains blank Leave Type and shows Alex B. - WFH.
  • Alex Blair explicit PTO row mentioning WFH now correctly shows Alex B. - OOO.
• Wayne House rows were excluded from the 2026 PTO backfill scope. No deletes or calendar cancellations were performed.

Current State

• Current-year approved rows by Leave Type after backfill:
  • PTO: 248 rows, 298.75 PTO days.
  • Blank: 145 rows, 42.564 PTO days.
  • Workers' Compensation Treatment: 2 rows, 0 PTO days.
  • Other: 1 row, 0 PTO days.
• 43 attempted PTO backfill rows failed validation because existing Required PTO values do not satisfy the current PTO rule. They remain blank and are listed in the results workbook.
• WFH remains without a Leave Type value by design.

Artifacts

• Results workbook: /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/tmp/pto-2026-title-and-candidate-cleanup-2026-05-12/PTO-2026-Backfill-Results-2026-05-12.xlsx
• Results CSV: /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/tmp/pto-2026-title-and-candidate-cleanup-2026-05-12/pto-2026-backfill-results.csv
• Bulk success rows: /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/tmp/pto-2026-title-and-candidate-cleanup-2026-05-12/750UV00000m6jq1YAA-success-records.csv
• Bulk failed rows: /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/tmp/pto-2026-title-and-candidate-cleanup-2026-05-12/750UV00000m6jq1YAA-failed-records.csv
• Rollback manifest for successful backfill IDs: /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata/tmp/pto-2026-title-and-candidate-cleanup-2026-05-12/pto-2026-backfill-rollback.csv

Suggested Next Step

Review or normalize the 43 validation-blocked legacy rows before deciding whether to set them to PTO. The safer path is to inspect those Required PTO values first, because the current validation is intentionally preventing irregular PTO amounts from being edited into explicit PTO records.