Triage Bundle Laravel Package

Product Decisions This Supports

• Queue/appointment management roadmap: novosga/triage-bundle is the triage/appointment-scheduling module of the Novo SGA service-desk platform. This release supports decisions on whether to build queue triage in-house or adopt/extend an existing domain model (priority triage, appointment scheduling, unit-level rules).
• Build vs. buy (or build vs. extend): v2.3.0 modernizes the dependency floor (Symfony 7.4 LTS) and adds a configurable "appointment max delay." If your roadmap includes scheduling windows, late-arrival policies, or grace periods, this is a signal the package is actively maintained and configurable rather than hard-coded.
• Correctness/trust in scheduling data: The timezone fix (parsing scheduled appointment datetimes against the unit's timezone rather than server/default timezone) materially affects multi-site, multi-region deployments. This influences decisions about supporting geographically distributed units or daylight-saving transitions.
• Platform lifecycle and upgrade planning: Symfony 7.1 → 7.4 LTS plus deprecation cleanup is a forward-compatibility investment. This de-risks staying on a supported framework branch and reduces future migration cost.
• Operational policy configurability: New config for max appointment delay shifts a business rule from code into configuration — a decision enabler for per-tenant/per-unit policy without forking.
• Use cases: walk-in + scheduled appointment blending, priority-based triage, service-desk/call-center queueing, clinic or branch office attendance flows, and any Laravel/Symfony app needing a triage domain model with an admin surface.

When to Consider This Package

Adopt when:

• You are on (or moving to) Symfony 6.4/7.x — this is a Symfony bundle, not a Laravel package, despite the "Laravel/PHP" framing. It will not drop into a Laravel app without an integration/adapter layer, and its service wiring, config tree, and event system assume Symfony's kernel.
• You need an existing, maintained domain model for triage plus appointment scheduling rather than a greenfield build.
• Multi-unit / multi-timezone correctness matters (the v2.3.0 timezone fix is directly relevant).
• You need configurable business rules (e.g., max delay before an appointment is considered missed) rather than hard-coded thresholds.
• You value long-term support posture: Symfony 7.4 LTS, PHPStan 2, PHPUnit 11, PHPCS 4 indicate active quality tooling and a maintainer investing in the codebase.
• You are comfortable with the Novo SGA ecosystem and its assumptions about units, services, and priority ordering.

Look elsewhere when:

• You are a Laravel-only shop. The integration cost is non-trivial; evaluate a Laravel-native scheduling package first unless you specifically need Novo SGA's triage semantics.
• You need a standalone, framework-agnostic scheduling library — this is bundle-coupled.
• You need enterprise support SLAs, a vendor contract, or a published LTS/security policy — this is a community-maintained project; verify maintainer bandwidth and release cadence yourself.
• Your requirement is calendar sync (Google/Outlook), recurring appointments, or resource capacity planning — the scope here is triage and appointment delay, not full calendar/RMS functionality.
• You cannot absorb major-version framework upgrades; note that Symfony 7.x requires PHP 8.2+, and 7.1→7.4 deprecation work signals more churn ahead.

Version-specific notes for v2.3.0:

• No breaking changes indicated. This is a minor release: bug fix, dependency/tooling upgrades, deprecations resolved, one new feature.
• The new Appointment max delay config is additive — plan a config review if you rely on prior implicit behavior.
• Requires Symfony 7.4 LTS; confirm your app's Symfony constraint before upgrading. If you're on 6.4 LTS, check the bundle's composer constraints for a compatible branch.

How to Pitch It (Stakeholders)

For executives (30 seconds): We evaluated novosga/triage-bundle, the appointment-and-triage module of the Novo SGA service-desk platform. The v2.3.0 release shows a healthy, actively maintained component: it moved to Symfony 7.4 LTS (a long-support framework version), cleared deprecations, and added a configurable rule for how long past an appointment time a patient/customer can still be served. Two things matter commercially: (1) it fixes a timezone bug that would have caused wrong appointment times across regions or during daylight-saving shifts — a real operational and compliance risk; and (2) the new config lets us change scheduling policy per site without engineering work. Recommendation: shortlist for evaluation if we need queue triage and appointment handling, with the caveat that it's a Symfony component, so a Laravel-based stack carries integration cost. No licensing or breaking-change red flags in this release.

For engineering leads:

• Minor version, additive feature, no documented breaking changes; safe to trial on a branch.
• Hard requirement: Symfony 7.4 LTS / PHP 8.2+. Verify composer constraints if you're on 6.4 LTS.
• The timezone fix (unit timezone for scheduled appointment parsing) is a behavioral change where units span multiple timezones — add regression tests around DST boundaries and cross-region units.
• New Appointment max delay setting: confirm defaults preserve current behavior before deploying; audit any hard-coded delay logic that should now move to config.
• Dev tooling moved to PHPStan 2 / PHPUnit 11 / PHPCS 4 — expect static-analysis and test-suite adjustments if you contribute upstream or vendor it.
• It is not Laravel-native. Budget for an adapter (service container bridging, config translation, auth/event integration) or treat this as a Symfony-side service with an API boundary.

Ask: Approve a short, time-boxed spike (1–2 sprints) covering Symfony version compatibility, multi-timezone appointment correctness, and the effort to expose max delay as per-unit configuration.