Problem
notify subject/body interpolation covers entity fields ({total}, {Customer.name}) — but a notification cannot carry a link to the record or task, because generated glue has no notion of the application's external base URL. Operationally, "you have an approval waiting" mails without a link get ignored.
Ask
A config-backed token (e.g. {appUrl}, resolved from a DIRIGIBLE_APP_BASE_URL-style configuration, tenant-overridable) usable in subject:/body:, so a body can say Review it here: {appUrl}/.... The concrete route should be assembled by the template layer (which knows the generated paths), keeping the intent layer path-agnostic.
Problem
notifysubject/body interpolation covers entity fields ({total},{Customer.name}) — but a notification cannot carry a link to the record or task, because generated glue has no notion of the application's external base URL. Operationally, "you have an approval waiting" mails without a link get ignored.Ask
A config-backed token (e.g.
{appUrl}, resolved from aDIRIGIBLE_APP_BASE_URL-style configuration, tenant-overridable) usable insubject:/body:, so a body can sayReview it here: {appUrl}/.... The concrete route should be assembled by the template layer (which knows the generated paths), keeping the intent layer path-agnostic.