React UI + local FastAPI runner that configures Azure DevOps for the Microsoft Business Process Catalog from Excel workbooks.
The app lives in bpctool/. This repo root is only the entry point for docs and git.
cd bpctool
# macOS: double-click Start BPCTool.command
# Windows: double-click Start BPCTool.bat
# or: npm run setup && npm start
Prerequisites: Node.js 20+, Python 3.11+.
In the browser: set org URL + PAT → confirm Multivalue: installed (or install when prompted) → process/project names → template workbook path (user-provided ADO guideline .xlsx) + catalog folder → Preview plan → Run (Runner mode).
Required org extension: Multivalue control (Microsoft DevLabs) — needed for Multi-select fields and for process / layout / project setup. The Connection panel checks the org and can install via API when the PAT allows; otherwise install as an org admin.
UI screenshots (Connection, workflow cards, run config, Catalog Threads): see bpctool/README.md.
| Doc | Purpose |
|---|---|
bpctool/README.md |
Launch, checklist, workflow, modes |
bpctool/USER_GUIDE.md |
Full usage, API, troubleshooting |
bpctool/CHANGELOG.md |
Release history |
bpctool/docs/workflow-and-script-comparison.md |
Workflow, quarterly releases, X vs H, catalog, incremental re-runs & conflicts, reference scripts vs BPCTool |
bpctool/docs/reference/ |
Process template after creation (MSBPC snapshot analysis) |
bpctool/
src/ React UI (Vite)
runner/ FastAPI Excel→IR→plan→apply engine
scripts/ Env + Vite local-runner plugin
docs/ Workflow & reference-script comparison; reference/ post-create analysis
Start BPCTool.* One-click launchers
bpctool.env.example Optional folder settings (copy to bpctool.env)
runner-out/ Run outputs per org/project (keep; gitignored)
~/BPC Files/<YYYY-Qn>/ Your template + catalog workbooks, one folder per quarterly release
Template and catalog workbooks are not bundled — supply absolute paths (or set BPCTOOL_TEMPLATE / place the guideline beside the catalog folder).
CC0 1.0 Universal — dedicated to the public domain.