Vocabularies

The lists a case is described with. Each is a small table an OPN administrator maintains here; everyone else sees the terms as choices on the New case and Edit case dialogs, as columns and filters on the cases list, and over the API.

Every term is visible to everyone

The lists are shared, not scoped: every operator at every entity — an FI, an integrator, a provider — sees every term, active or retired, on every dialog and over the API. So never use a customer's name, an environment's id, or anything one institution shouldn't learn about another as a term. A per-case sandbox vocabulary was built and removed for exactly this reason: a list of sandbox names and ids would have told every institution what the others run. Describe the kind of thing, never the instance.

Case types

What kind of request a case is: access, transfer, configuration and the rest. The guides describe what to gather and say for each seeded type. Two types are built in — the tool relies on them — and can be renamed but not retired: Other, the default, and Noise, which the Dismiss as noise action sets and the figures leave out. They are marked built-in in the table.

Components

A definable part of the OPN software stack: the Management Console, FedNow, RTP, RTNCORE, the sandbox, the OPay app, the digital-banking extension, AWS, the firewall, and so on. A case's component is optional and blank by default; set it when the request makes it plain, and leave it blank rather than guess. A description on the term helps the person choosing.

Renaming, retiring, restoring

• Edit changes a term's label and description. Its key — the short identifier exports, filters and the API carry — never changes once the term exists.
• Retire takes a term out of every list. Cases already carrying it keep it and still read correctly; the Cases count on the row says how many. Restore brings it back.
• Nothing is deleted. Every change here is an audit event.