Bring the Litify PTO request process closer to production-ready: cleaner request page, populated partial-day ending date/time, Eastern-time display cleanup, approval limited to Sam/Jenni/Janelle, and a firm-owned Outlook calendar path.
The visible Time Off Request layout was already cleaned up by removing Length Minutes, Beginning Hour, and Beginning Minute. New_Time_Off_Request v46 was already activated so new partial-day requests populate Ending_Date_Time__c. Recent partial-day records were backfilled: Bulk job 750UV00000lE9TOYA0, 115 of 115 succeeded. A follow-up scan found no remaining Time_Off_Request__c.Name UTC-style hits.
Four rollback-ready Salesforce packages are staged and check-only validated in LITIFY_ORG. Specific Hours Fix 0AfUV000001VDzh0AG succeeded with 3 components, 11 tests, 0 failures. Data Quality Guard 0AfUV000001VE1J0AW succeeded with 1 validation rule, 9 tests, 0 failures. Page Context 0AfUV000001VDwT0AW succeeded with 5 components, 9 tests, 0 failures. Approval Guard 0AfUV000001VDoP0AW succeeded with 5 components, 9 tests, 0 failures.
The session log and rollback commands are saved at /Users/samaguiar/Documents/Projects/admin/session_logs/pto-request-config-execution-2026-04-25.md.
No human Slack approval phrase was present as of the latest check at 2026-04-24 23:34 EDT. Live Salesforce deploy remains gated. The consolidated phrase is APPROVE PTO SALESFORCE BUNDLE; individual phrases are APPROVE PTO SPECIFIC HOURS FIX, APPROVE PTO DATA QUALITY GUARD, APPROVE PTO PAGE CONTEXT, and APPROVE PTO GUARD.
The Microsoft calendar write remains separate. Use APPROVE SAIL-AWAY MAILBOX only when ready to create the shared mailbox/calendar target.
Read-only Graph and Salesforce verification found that current PTO events still resolve to hatfield@kylawoffice.com and Nathaniel Hatfield's SAIL Boat calendar. SAIL-AWAY / sailaway@kylawoffice.com is currently a Microsoft 365 group, not a user or shared mailbox, and app-only Graph gets 403 ErrorAccessDenied on that group calendar. No user or shared mailbox currently exists at sail-away@kylawoffice.com. Salesforce metadata and repo search did not find a Graph callout, Named Credential, Remote Site, Apex writer, or repo script that owns PTO Outlook sync, so the writer is most likely external automation such as Power Automate, Zapier, Pipedream, or a non-repo script.
Continue from /Users/samaguiar/Documents/Projects/admin/session_logs/pto-request-config-execution-2026-04-25.md. First read Sam's Slack DM D0ASWN69Q4F. If a human reply contains APPROVE PTO SALESFORCE BUNDLE, deploy the four Salesforce packages in order: Specific Hours Fix, Data Quality Guard, Page Context, Approval Guard, then assign PTO_Approver only to sam@kylawoffice.com, jhubbard@demandsam.com, and janelle@kylawoffice.com. If only an individual approval phrase appears, deploy only that package. Use the rollback commands in the local session log if any deploy fails. If APPROVE SAIL-AWAY MAILBOX appears, create the shared mailbox/calendar target only after confirming the Exchange/Graph write path, then find and repoint the external PTO Outlook sync away from Nathaniel Hatfield's SAIL Boat calendar.
A. Use the consolidated Salesforce bundle phrase by default (recommended). Keep APPROVE PTO SALESFORCE BUNDLE as the standard for compatible, validated PTO Salesforce packages with rollback paths.
B. Require one approval phrase per metadata package. More granular, but slows cleanup and increases Slack noise.
C. Approve only the smallest hotfix first. Deploy Specific Hours Fix alone, then defer layout and guard polish.
D. Other.