ores.inbox.notification_argument
Table of Contents
The values a notification's message names, one row each: the role, the tenant, the step. The screen renders the kind's message with them in the reader's language, so a notification stores no finished sentence and no document.
A row is identified by the notification and the argument's name.
1. Flags
It states no :events:. Its component has no service-side composition point for change events yet, so a generated event registrar would publish nothing.
2. Left
The notification the argument belongs to.
References ores_inbox_notifications_tbl.id (soft FK).
ctx.generate_uuid()
3. Right
The argument's name, as the message names it.
Examples: 'role', 'tenant', 'step'.
std::string(faker::word::noun())
4. Columns
4.1. value
The argument's value, as the message shows it.
std::string(faker::word::noun())
5. SQL
5.1. Flags
6. Foreign keys
6.1. notification_id
The notification the argument belongs to; must exist in ores_inbox_notifications_tbl.
7. Repository
8. C++
8.1. Flags
8.2. Domain includes
#include <string> #include <boost/uuid/uuid.hpp>
8.3. Entity includes
#include <string>
8.4. Conventions
8.5. Table display
| column | header |
|---|---|
| notification_id | Notification |
| name | Name |
| value | Value |
| version | Version |
8.6. Presentation
An argument is identified by the pair it links, so the model declares no key field.
9. See also
- Notification requirements — words in the person's language.
- ores.inbox.notification — the notification an argument belongs to.