Skip to content

docs(intent): notify link placeholders - {recordUrl} / {inboxUrl} - #185

Merged
delchev merged 1 commit into
masterfrom
docs/notify-deep-links
Aug 15, 2026
Merged

docs(intent): notify link placeholders - {recordUrl} / {inboxUrl}#185
delchev merged 1 commit into
masterfrom
docs/notify-deep-links

Conversation

@delchev

@delchev delchev commented Aug 15, 2026

Copy link
Copy Markdown
Contributor

Documents the notify block's link placeholders, added by eclipse-dirigible/dirigible#6744 (closes eclipse-dirigible/dirigible#6553).

{appUrl} supplied only the application's origin, so a body that wanted to link back to the record had to hand-type the generated app's route — the layout the model is forbidden to know, correct until a template changes it. {recordUrl} and {inboxUrl} are resolved to complete addresses instead.

  • docs/help/intent/glue.md — a new "Links back to the application" section under the notify block: the three-token table, the reserved-name rule, the "never hand-type a route" rule with the concrete addresses each token resolves to, the DIRIGIBLE_APP_BASE_URL origin and its tenant override, why the intent never writes the path, and the fan-out scoping ({recordUrl} links the row, {record.<field>} reads the anchor).
  • docs/help/intent/dsl-reference.md — the index row.

Anchors verified against the built HTML (#links-back-to-the-application-recordurl-inboxurl-appurl); npm run docs:build clean.

🤖 Generated with Claude Code

…s a route

`{appUrl}` gave a notify block only the application's origin, so a body that
wanted to link back to the record had to hand-type the generated app's route -
the layout the model is forbidden to know, correct until a template changes it.

Document the two reserved tokens that finish the job: `{recordUrl}` (the record
the message is about) and `{inboxUrl}` (the recipient's process Inbox), both
resolved to a complete address, with `{appUrl}` reframed as the escape hatch for
addresses the other two cannot express. Covers the reserved-name rule, the
`DIRIGIBLE_APP_BASE_URL` origin and its tenant override, why the intent never
writes the path, and the fan-out scoping (`{recordUrl}` links the row).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

intent: notification deep links - app base-URL token in notify bodies

1 participant