Draft Saving for APIs/WebUIs in Progress
In the NocodilySuite console, you can temporarily save APIs or WebUIs that are under design or definition as drafts.
Because changes are not reflected in production until you explicitly run an upgrade,
you can edit and review as many times as needed while still in the draft state.
Why Draft Saving Matters
Console work — schema design, adding fields, configuring authentication, writing custom code — rarely finishes in a single session.
Without draft saving, any work in progress is at risk of being lost the moment you step away.
Draft saving prevents problems like:
- Losing work due to closing the browser or accidentally navigating away
- Long design sessions gone because nothing was saved
- Definitions disappearing mid-handoff to a team member
Draft Characteristics
| Feature | Description |
|---|---|
| No impact on production | A draft is just an editing state. It has no effect on a running API or WebUI until you run an upgrade |
| Save as many times as needed | Save mid-task and resume later. Carry over partially completed changes safely |
| Persists until discarded | Drafts are retained until you explicitly discard them |
| Shared with the team | Saved drafts are visible to team members in the console |
Use Cases
- Large schema changes — Work through adding or modifying many fields across multiple sessions
- Changes awaiting review — Save a draft, share it with the team, and run the upgrade only after getting sign-off
- Parallel work — Switch to another task and return to finish editing where you left off
- Trial and error — Try different configurations, compare them, and discard and start over if something goes wrong