View Revisions: Issue #6135
| Summary | 0006135: Add Parameters as replacement tokens in Notification templates | ||
|---|---|---|---|
| Revision | 2023-11-30 14:42 by pmarzullo | ||
| Description | When configuring templates for Notifications, we should allow all parameters to be available to use. This will allow the customer to define a system property, that gets converted to a parameter, to use the value in portions of the notification like the subject (if e-mail) or the body-before or body-after to make sure the source of the notification is known. For example, you may want to have the environment of the SymmetricDS in the subject, like TEST, QA, or PRODUCTION. If you consider it related, it would be useful to also make the SMTP page to allow some kind of variable values as well. If you recall, I mentioned that we use exactly the same SQL import for 5 different AWS installations, and it would be useful to set up the SMTP server and target emails as parameters so notifications can be sent to the correct email group. I can make just a templated email work (using mail rules in Outlook, our mail client), but a more flexible SMTP set up would even be more useful. |
||
| Revision | 2023-11-29 21:42 by pmarzullo | ||
| Description | When configuring templates for Notifications, we should allow all parameters to be available to use. This will allow the customer to define a system property, that gets converted to a parameter, to use the value in portions of the notification like the subject (if e-mail) or the body-before or body-after to make sure the source of the notification is known. For example, you may want to have the environment of the SymmetricDS in the subject, like TEST, QA, or PRODUCTION. |
||