Current status

Repaired historical PTO report-cleanup record. The report rebuild described here was completed and verified, while legacy pending-row cleanup and later PTO work moved into newer PTO/Litify records. Do not use this page alone for current PTO decisions; verify live LITIFY_ORG state or start from newer PTO pages and the hygiene hub.

Objective

Clean up the live Pending PTO Requests approval report so approvers see the request impact instead of notice-hours noise.

What was accomplished

• Live-validated the report definition in LITIFY_ORG and confirmed it was built on Employees with Time Off Requests with the standard date filter incorrectly pointed at Employee Date of Birth.
• Confirmed the main bad-output issue: Notice Hours Excluding Weekends was showing huge values like 5898.38, 5706.36, and 1363.42 for far-future pending requests.
• Retrieved the report metadata into the repo and rebuilt the live report to show:
  • employee
  • submitted at
  • leave type
  • beginning and ending dates/times
  • PTO Applied
  • Scheduled PTO Applied
  • Unscheduled PTO Applied
  • current PTO balance
  • current unscheduled PTO remaining
  • remaining PTO after this request
  • remaining unscheduled PTO after request
• Added four request-level formula fields on Time_Off_Request__c:
  • Unscheduled_PTO_Applied__c
  • Scheduled_PTO_Applied__c
  • Remaining_PTO_After_Request__c
  • Remaining_Unscheduled_PTO_After_Request__c
• Added field visibility for the new report fields in Admin_Permissions and Employee_Records_Access.
• Deployed the live change successfully with deploy id 0AfUV000001UefN0AS after a successful dry run 0AfUV000001Uedl0AC.

Verification

• Queried FieldDefinition in LITIFY_ORG to confirm all four new formula fields are live.
• Queried pending Time_Off_Request__c rows to confirm the new scheduled/unscheduled and projected remaining values are resolving on real records.
• Ran the live Analytics API describe for report 00O8W0000073GUUUA2 and confirmed the detail columns now use request-centric fields and no longer include Notice_Hours_Excluding_Weekends__c.

Decisions made

• Keep the report itself, but rebuild it around request impact rather than notice-hour calculations.
• Use additive formula fields instead of new Apex so the fix stays narrow and low-risk.
• Keep legacy pending rows visible even if they still show blank Leave Type or bad historic PTO values, because that is an input-data cleanup issue rather than a reporting issue.

Remaining work