Skip to content

Notifications

Application address: /admin/notifications · Product baseline: 0.4.0

Reference status

Screen inventory extracted from the implementation. Labels and explicitly declared input constraints are recorded below. This is not a claim that every control, calculation, or business workflow has been verified in a running system.

Open this screen

Use OSERP navigation to find Notifications, or open /admin/notifications on your OSERP application after signing in. Confirm the active company before reading or changing records.

Menu access: settings:manage

Menu access only determines whether the screen is offered. Saving, posting, deleting, exporting, and approving can require additional server permissions.

Fields and input controls

Limits in this section are interface declarations. A missing maximum is not a promise of unlimited storage. Read how field limits work. Labels may differ with language and configuration.

Document type

PropertyReference
Reference keydocument-type
LocationScreen / contextual panel
Input controlselect
Required in interfacenot declared on control
Maximum charactersNot explicitly declared on this control
EditingNo disabled/read-only condition declared directly on this control.

Only events with a rule

PropertyReference
Reference keyonly-events-with-a-rule
LocationScreen / contextual panel
Input controlcheckbox
Required in interfacenot declared on control
Maximum charactersNot explicitly declared on this control
EditingNo disabled/read-only condition declared directly on this control.

On

PropertyReference
Reference keyon
LocationScreen / contextual panel
Input controlcheckbox
Required in interfacenot declared on control
Maximum charactersNot explicitly declared on this control
EditingNo disabled/read-only condition declared directly on this control.

Where to send it

PropertyReference
Reference keywhere-to-send-it
LocationScreen / contextual panel
Input controlinput
Required in interfacenot declared on control
Maximum charactersNot explicitly declared on this control
PlaceholderWhere to send it
EditingNo disabled/read-only condition declared directly on this control.

Value

PropertyReference
Reference keyvalue
LocationScreen / contextual panel
Input controlinput
Required in interfacenot declared on control
Maximum charactersNot explicitly declared on this control
PlaceholderValue
EditingNo disabled/read-only condition declared directly on this control.

Subject

PropertyReference
Reference keysubject
LocationScreen / contextual panel
Input controlinput
Required in interfacenot declared on control
Maximum charactersNot explicitly declared on this control
EditingNo disabled/read-only condition declared directly on this control.

Message

PropertyReference
Reference keymessage
LocationScreen / contextual panel
Input controltextarea
Required in interfacenot declared on control
Maximum charactersNot explicitly declared on this control
EditingNo disabled/read-only condition declared directly on this control.

Template name or ID

PropertyReference
Reference keytemplate-name-or-id
LocationScreen / contextual panel
Input controlinput
Required in interfacenot declared on control
Maximum charactersNot explicitly declared on this control
Placeholdere.g. order_shipped
EditingNo disabled/read-only condition declared directly on this control.

Approved in

PropertyReference
Reference keyapproved-in
LocationScreen / contextual panel
Input controlinput
Required in interfacenot declared on control
Maximum charactersNot explicitly declared on this control
Placeholderen
EditingNo disabled/read-only condition declared directly on this control.

{{partyName}}

PropertyReference
Reference keyparty-name
LocationScreen / contextual panel
Input controlinput
Required in interfacenot declared on control
Maximum charactersNot explicitly declared on this control
Placeholder{{partyName}}
EditingNo disabled/read-only condition declared directly on this control.

Named actions

These are labels found in screen components; availability and consequences depend on record state. Confirm the operation before executing it.

  • Remove rule
    • Another wording
  • Close
  • Always send
  • Save
    • Add a variable
  • {{#lines}}…{{/lines}}
  • {{#if …}}…{{/if}}
  • Refresh

Help text and messages

The following wording is embedded in this screen. It describes interface guidance, rather than independently verified system guarantees.

  • This rule uses a combined condition that this simple editor cannot show. Saving here replaces it with the single test below.
  • GL Mapping Engine · configure auto-JE per stage
  • Which document stages create a journal entry, in which book, from which template.
  • No stage posting rules. Click Seed Defaults or + Configure Stage.
  • Which ledger account each role resolves to. Lower priority wins; keep an unconditional fallback.
  • Ranked from your chart of accounts (name + group nature). Click Use to create the mapping rule.
  • The engine’s vocabulary. A template names a role; a mapping rule points it at a real account.
  • No account roles. Click Seed Defaults.
  • The journal recipe: which roles are debited and credited, and on what amount.
  • No posting templates. Click Seed Defaults or + New Template.
  • Parallel ledgers — one document posts a balanced JE per active book (e.g. IFRS + local GAAP + tax).
  • No accounting books. Click Seed Defaults (creates the leading book) or + Add Book.
  • BLOCK stops a posting; WARN shows a caution in the confirmation popup. Evaluated against the document before its journal entry.
  • No validations. Click + New Validation.
  • Open periods accept postings; Closed/Locked periods reject them. Posting into a closed or locked period is blocked across the whole system.
  • No periods. Generate a fiscal year to begin.
  • Analytic dimensions tag journal lines so reports can be sliced by cost centre, profit centre, segment, or project.
  • Spread revenue straight-line across periods. Running recognition posts Dr Deferred Revenue · Cr Revenue for every period now due.
  • Replays your recent documents through the engine. Tick “candidate rule” to preview the impact of a mapping change before you save it.
  • Run What-If to replay recent documents.
  • A versioned, restorable history of your entire GL configuration. Restore rolls back roles, templates, stage matrix, rules and books (a safety snapshot is taken first).
  • Feed the engine amounts and see the journal it would produce — without touching a document.
  • Nothing has been sent yet.

Verification still required

Business purpose for each control, dynamically generated fields, backend limits, saved defaults, permission combinations, audit effects, and complete workflow outcomes require manual review against the published application.

See the operating manual, coverage register, and troubleshooting guide.

OSERP Atlas · Understand every field. Master every workflow.