Story: Party/counterparty follow-ups
Table of Contents
This page documents a story in Product backlog — next. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Pick up the two follow-ups Commission: party, counterparty, and party_status (Sprint 23, DONE) deliberately left out of its own finish line: confirm counterparty's orchestration/workflow-step needs before further codegen regen, and add a generate_short_code button to Qt Create dialogs for natural-key entities.
Status
| Field | Value |
|---|---|
| State | BACKLOG |
| Parent sprint | None (product backlog) |
| Now | Not yet started. Split out of the Sprint 23 story at its close so the tail didn't keep it open. |
| Waiting on | Nothing. |
| Next | Either task is independently startable when pulled into a sprint. |
| Last touched | 2026-07-20 |
Acceptance
- Counterparty's orchestration/workflow-step-command needs are investigated and either covered or explicitly deferred with a filed capture.
- generate_short_code is wired into Qt Create dialogs for entities whose codegen model marks a natural (non-UUID) is_key field.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Investigate orchestration/workflow-step command usage in counterparty | BACKLOG | Party's save handler has a hand-written workflow-step-command branch (bypasses JWT, used by orchestration) with no template/facet coverage. Check whether counterparty has or needs equivalent orchestration support before its save() workflow paths (if any) are lost to codegen regen. | ||
| Wire generate_short_code into Qt Create dialogs | BACKLOG | Add a generate/suggest button next to the short code field on generated Create dialogs that calls the existing generate_short_code utility from the entity's full name, for entities whose codegen model marks a natural (non-UUID) is_key field. |