{"id":"6aecdee00e07f8a2f36e87ea","title":"2026 11 05 Issue 273","path":"how-to/committee/release-notes/2026-11-05-issue-273","contentMarkdown":"# 05-Nov-2026 — preserve written configuration bodies in automated emails [#273](https://github.com/nbarrett/ngx-ramblers/issues/273)\n\n## [build 1061](https://github.com/nbarrett/ngx-ramblers/actions/runs/42095565898) — [commit 005a262](https://github.com/nbarrett/ngx-ramblers/commit/005a262ce9a5647b8e744692cd363cd1c1bc8a93)\n\n_____\n\n## What's new\n\n- Emails using an automated template now include the wording saved in their email configuration in both preview and send.\n- Built-in process emails keep their generated content when no written body is saved or the body is still the composer placeholder.","contentHtml":"<h1>05-Nov-2026 — preserve written configuration bodies in automated emails <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/273\">#273</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/42095565898\">build 1061</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/005a262ce9a5647b8e744692cd363cd1c1bc8a93\">commit 005a262</a></h2>\n<hr>\n<h2>What&#39;s new</h2>\n<ul>\n<li>Emails using an automated template now include the wording saved in their email configuration in both preview and send.</li>\n<li>Built-in process emails keep their generated content when no written body is saved or the body is still the composer placeholder.</li>\n</ul>\n"}