Batch 5 hygiene note, 2026-05-17: Complete historical PTO policy update. The live Knowledge Center change was verified and no Litify blocker remains for this request. Optional skill/runbook improvement remains useful, but this page should not appear as an open policy blocker. Indexed in the SAIL Knowledge Base Hygiene Hub - 2026-05-12.
Update the live Litify Knowledge Center PTO and Attendance policy to reflect Sam's requested rule: any leave other than bereavement or workers' compensation should require available PTO to be used first.
I loaded the Litify live defaults and Knowledge Center workflow, then validated the live org instead of relying on older notes. The target record was Knowledge__c article Attendance, PTO, and Scheduling Policy, record ID a5mUV0000004ly1YAA, already published in Litify.
I updated the policy body in Body__c to add a PTO-first rule under PTO usage and attendance rules. The new language says that, except for bereavement leave and workers' compensation absences, available PTO must be used first for approved time away from work, including other paid leave, unpaid leave, extended leave, approved leave programs, medical leave, personal leave, or any other non-working time away arrangement. It also includes Sam's example: if an employee receives six weeks of approved paid leave during the year, available PTO is applied to that leave first and should not remain available to extend time away later in the same year.
I also adjusted the opening approval section so it no longer frames bereavement as ordinary PTO. It now says PTO is the leave bank used first for vacation, illness, appointments, personal absences, and other approved time away unless bereavement leave, workers' compensation, a written agreement, an approved accommodation, or a legal requirement controls.
Live REST PATCH returned HTTP/1.1 204. A post-update SOQL read confirmed the article remains Published, LastModifiedDate = 2026-05-12T20:40:10.000+0000, LastModifiedBy = Sam Aguiar, and the updated body contains the PTO-first rule, the six-week paid-leave example, and the opening correction. A local HTML balance check confirmed matching p, ul, li, and ol tag counts in the updated body.
Local rollback package: /Users/samaguiar/Documents/Projects/admin/backups/litify-knowledge-pto-policy-20260512T163938/
Key files are current-record.json, old-body.html, new-body.html, update-payload.json, rollback-payload.json, and post-update-record.json. The rollback path is a Salesforce REST PATCH using rollback-payload.json against /services/data/v66.0/sobjects/Knowledge__c/a5mUV0000004ly1YAA.
Session log: /Users/samaguiar/Documents/Projects/admin/session_logs/litify-pto-policy-update-2026-05-12.md
QA queue mirror: /Users/samaguiar/Documents/Codex/_qa-queue/2026-05-12.md
The requested live policy update is complete and verified. No live Litify blocker remains for this request.
A future agent can use the same pattern for single-record Knowledge Center edits: identify the live Knowledge__c article, snapshot the current record, generate update and rollback payloads, patch only the intended field, then verify via SOQL. It may be worth adding that concise recipe to the litify-knowledge-center skill so later policy updates do not need to rediscover the pattern.