PSI Routing Manager (Business Central)
The Business Central replacement for the legacy WPF Route Manager (
PSI.All/PSI.Route) — machine-build side only (MW / MA / EA; process services / CC 125 is PRGJSMES territory, and JS was deliberately dropped).
| Property | Value |
|---|---|
| Repo | PSI-BC → apps/PSI.RoutingManager (tests: tests/PSI.RoutingManager.Test) |
| Object range | 53100–53149 (registry: PSI-BC/OBJECT-IDS.md) |
| Spec / acceptance oracle | route-manager-functional-inventory.md + its extraction/ appendices |
| Tracking | PSI.All#222 |
| Deploy | PSI-BC deploy.yml (canonical release asset per version; sandbox-first; Production held) |
Using it? Start with the user guide.
What it is
Item-level MW/MA/EA routing-status state machine (Y/C/N/D/R enum on Item; never-all-N,
completion date stamp, auto-certify, un-certify on rework, laser-op warning, downgrade on routing
delete), routing template flags on Routing Header (the legacy RT.* convention), and the
Routing Worksheet — the single-pane page: planning-line queue with inline status editing,
standard-routing + prod-order-routing parts, template apply, Rework Items view. M3 adds
released-order routing maintenance under the legacy guard rules (actuals-lock, insert/delete
guards, outside-op PO-received confirm, per-operation complete/un-complete).
A sandbox-only demo seed (worksheet action) creates real legacy routings for twelve
machine-build parts, harvested from SROUTE.* via the UniData API.
Current state
Don’t trust prose for state — check the living sources: PSI-BC PRs/releases
(tags PSI.RoutingManager/vX.Y.Z.0), apps/PSI.RoutingManager/README.md (per-milestone object
tables), and PSI.All#222 for the roadmap (M4 queue fidelity → M5 broadcast follow → M6 planning
gate). Known coordination items: PSI-BC-MES declares a colliding Item field (blocks DEV installs
until resolved); Dispatch API writes prod-order routings that the M3 guards govern.