Skip to content

MedEvac: per-record body field tokens - #2917

Draft
morgang-adappt wants to merge 3 commits into
medevac/email-schedulerfrom
medevac/sse-body-tokens
Draft

MedEvac: per-record body field tokens#2917
morgang-adappt wants to merge 3 commits into
medevac/email-schedulerfrom
medevac/sse-body-tokens

Conversation

@morgang-adappt

@morgang-adappt morgang-adappt commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Description

Adds per-record body tokens for separate emails. A body field-select dropdown inserts {{Block N.field.path}} tokens, which the function then replaces with that row's value for each recipient. Nested paths are supported, and duplicate entries no longer accumulate in the body dataset field selector when the layout tab is reloaded.

Useful links

  • Please insert link to ticket
  • Please insert link to back-end branch if any
  • Please insert any useful link ( documentation you used for example )

Type of change

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

  • Test A
  • Test B

Screenshots

Please include screenshots of this change. If this issue is only back-end related, and does not involve any visual change of the platform, you can skip this part.

Checklist:

( * == Mandatory )

  • * I have set myself as assignee of the pull request
  • * My code follows the style guidelines of this project
  • * Linting does not generate new warnings
  • * I have performed a self-review of my own code
  • * I have put the ticket for review, adding the oort-frontend team to the list of reviewers
  • * I have commented my code, particularly in hard-to-understand areas
  • * I have put JSDoc comment in all required places
  • * My changes generate no new warnings
  • * I have included screenshots describing my changes if relevant
  • * I have selected labels in the Pull Request, according to the changes with code brings
  • I have made corresponding changes to the documentation ( if required )
  • I have added tests that prove my fix is effective or that my feature works
  • * New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

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.

2 participants