Story: Edit a party on a standard entity page

Table of Contents

This page documents a story in Sprint 30, carried unfinished from Sprint 28 at close. It captures the goal, current status, acceptance criteria, and the tasks that compose it.

1. Goal

A party is edited on one standard entity page, in dialogs on its cards, like a currency. The wizards are gone, and the page is ready for the four-eyes approval that another story adds.

2. Status

Field Value
State BACKLOG
Parent sprint Sprint 30
Now Not yet started.
Waiting on Nothing.
Next Break the story into tasks.
Last touched 2026-11-08

3. Acceptance

  • The Parties list adds a party in a dialog, and a row opens the party page.
  • The party page has tabs for the details, the identifiers, the contacts, the memberships, the structure and the history, and each card is changed in a dialog.
  • The three party wizards, their routes and their cards are removed.
  • The page follows the entity screen specification and shares its parts with the other record screens.

4. Tasks

Task State Start End Description
Scaffold story: Edit a party on a standard entity page DONE 2026-10-11 2026-10-24 Story scaffolding rides this task: documents, sprint wiring, and the scaffold PR. Close it before merging that PR.
Edit a party on a standard entity page DONE   2026-11-08 Build the party list, page and dialogs from the shared record parts, and remove the party wizards.
Label the party picture as a logo BACKLOG     The Details card calls the party's picture Flag, which is the currency's word. A party's picture is its logo.
Show a party's history BACKLOG     The History tab of a party is empty. The server keys a party's versions by its short code, and the page asked with the identifier. The identifiers, contacts and business units may be keyed in their own way too.
Fix the Memberships tab and the missing strings BACKLOG     The Memberships tab shows the heading Countries it operates in twice, and the Contacts tab shows the raw key refdata.parties.address for its Address column. Find why and fix both, and check every string the party page uses exists in English, French and Portuguese.
Split the Structure tab into Business centres and Counterparties BACKLOG     The Structure tab holds the business units and the counterparties a party can see. Rename it to Business centres, and give the counterparties the party may trade with a tab of their own.
Give party codenames a numeric suffix BACKLOG     A party codename ends in letters, such as purple_dream_d, because the table forbids digits and the generator encodes its sequence in base 26. A codename should end in a number, such as purple_dream_4.
Give the Acme parties offices, countries and currencies BACKLOG     The four Acme parties have no contact information, no countries and no currencies in the sample data, so the Contacts and Memberships tabs are empty. Add an office for each contact type to every party, and the countries and currencies each one operates in, to the Acme dataset and to the way it is published.
Give the Acme parties counterparties to trade with BACKLOG     The Acme dataset links no counterparty to any party, so the Counterparties tab is empty. Add a set of counterparties and link each party to the ones it may trade with.
Page the lookups of the party link panels BACKLOG     The Memberships and Counterparties tabs read every country, currency and counterparty to name the few a party links, and a tenant holds about 13000 counterparties. The panels should look up the few rows they draw and search the rest on the server, as the entity specification says.

5. Decisions

  • Reviewed on 2026-11-08 at sprint 30 start. The page is built. What remains is follow-up fixes and Acme sample data found while testing it.

6. Out of scope

  • The four-eyes gating of party changes, the request screens for them, and the apply. The story Build the four-eyes framework does them.
  • Counterparties. They follow the same pattern after parties are signed off.

Emacs 29.3 (Org mode 9.6.15)