Skip to content

Return category-level metadata fields from ScheduleExceptionOutputWrapper#48

Draft
Copilot wants to merge 2 commits into
mainfrom
copilot/add-category-level-metadata
Draft

Return category-level metadata fields from ScheduleExceptionOutputWrapper#48
Copilot wants to merge 2 commits into
mainfrom
copilot/add-category-level-metadata

Conversation

Copilot AI commented Apr 3, 2026

Copy link
Copy Markdown
Contributor

Flow users had no visibility into computed category ranges and allocations after invocation — only scheduleExceptions and errorMessage were returned.

Changes

  • ScheduleExceptionOutputWrapper — added 16 optional @InvocableVariable fields (4 per category: cat1/cat2/cat3/post):

    • {cat}Start, {cat}End — actual computed date range
    • {cat}HoursPerDay — computed hours per working day
    • {cat}UsableDays — workdays in range after excluding holidays/onsite gap
  • processSingleSchedule — populates the above fields from already-computed locals before returning. Error paths are unchanged; fields remain null on error (optional by design).

  • Tests — two new cases: one asserting all metadata fields are populated and consistent on a valid run, one asserting they are all null when an error is returned.

ScheduleExceptionOutputWrapper w = results[0];
// now available to Flow
w.cat1Start;        // Date
w.cat1End;          // Date
w.cat1HoursPerDay;  // Decimal
w.cat1UsableDays;   // Integer
// …cat2, cat3, post equivalents

Copilot AI changed the title [WIP] Extend ScheduleExceptionOutputWrapper with category-level metadata Return category-level metadata fields from ScheduleExceptionOutputWrapper Apr 3, 2026
Copilot AI requested a review from ethandunzer April 3, 2026 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Return category-level metadata for Flow (optional but helpful)

2 participants