Roadmap
The Roadmap screen lets you read the delivery phases of the platform: priority, deliverable, bricks involved and exit criteria of each phase. Portal path: /developer/roadmap. It is used by architects, project managers and developers who plan their work on the platform.
What the screen shows
- A text box with the cross cutting concerns of the roadmap, when the roadmap has one.
- A table with one row per phase and the columns
phase(number),priority(status badge),deliverable,bricks(list) andexit_criteria. The deliverable and the exit criteria are shown in the language of the portal.
The roadmap comes from GET /v1/roadmap.
Actions
| Button or action | What it does | API call | Roles |
|---|---|---|---|
| Retry (error state) | Reads the roadmap again. | GET /v1/roadmap | Every signed in user |
Roles
The portal asks no role on this screen. The roadmap is read only.
Typical tasks
Check what a phase delivers
- Find the phase. Phases are listed by number. Read the
phasecolumn. Expected result: the row of the phase. If it fails: No roadmap published means the Control Plane has no roadmap. - Read the exit criteria. They tell when the phase is done. Read
exit_criteria. Expected result: the list of conditions. If it fails: nothing else to do on this screen. - Open the bricks. The
brickscolumn names the bricks of the phase. Look them up on the Brick catalog screen. Expected result: the cards of these bricks. If it fails: search by identifier there.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| No roadmap published | The roadmap has no phase. | Check the deployment of the Control Plane. |
| Error state | GET /v1/roadmap failed. | Click Retry, then check the Control Plane. |