⠿ Enums · Action + CounterpartyRole User Runebook
T−14+
⤢ ⌃ ⧉ ✕
</> RUNE legacybank-event-enum.rosetta legacybank-party-enum.rosetta + Valid
</> JAVA-GEN Generate
1 2 3 4 5 6 7
namespace legacybank.eventversion "0.1.0" // TODO — declare LegacyBankActionEnum here.// See the helper drawer (right) for naming convention + the 4 variants// you need (drawn from the outbound message's `event.action` field).
TEMPLATE GUIDE
Define LegacyBankActionEnum

You're in the legacybank.event namespace — everything about what happened to a trade lives here. Convention: one namespace per domain concept, lowercase + dotted.

File-naming convention

legacybank-event-enum.rosetta follows <project>-<domain>-<kind>.rosetta. Types and enums get separate files even in the same namespace — the matching legacybank-event-type.rosetta arrives in the Lesson 4 closeout.

Enum-naming convention

PascalCase + the Enum suffix — LegacyBankActionEnum. Project-prefixed so a downstream model can host this alongside other legacy systems without name clashes.

Do it
  1. Add an enum LegacyBankActionEnum: block (note the colon).
  2. Below it, indent and declare four variants — one per line: NEW, AMEND, CANCEL, REPLACE (these are the four values present in the outbound message's event.action field).
  3. Each variant carries a doc string on the next line, indented: <"Initial booking."> for NEW, and so on. The doc strings travel through to the generated Java + regulatory reports — not optional.
  4. Hit Generate once the four variants + doc strings are in place. A green pill means the enum compiled.

Stuck? Use Open the completed runebook on the lesson panel.