Add Email Notifications

It adds email notification support for a specific status transition: when a record moves into the final or completed state, the app sends an email to the record creator. The template includes the capability addition in plugin.rb, a mailer template, and the controller update hook that triggers delivery. It is meant for a single, clear workflow rather than a general notification system.

It works for any record type that has a status field and a creator relationship, such as incident logs, maintenance requests, equipment returns, visitor records, or inventory adjustments. The key requirement is that the record has a defined final or completed state. If your app uses a different lifecycle, you can customize the trigger condition to match that status value.

The email sends once when the record changes into the target completed state. It should not fire on every edit, only on the transition that matches the configured status. If the record is edited again later while already completed, the template should not resend unless you intentionally change the trigger logic.

By default, the notification goes to the record creator. That makes it useful for workflows where the person who opened the record needs confirmation that the item is done. If your process needs a different recipient, such as a manager, assignee, or shared mailbox, you can adjust the mailer target in the template.

Yes, if the email is used as an operational alert and not as the system of record. For regulated workflows, the app should still keep the status change inside the record history, with the email acting as a notification layer. If the record is part of a compliance process, make sure the status values, audit trail, and retention rules are defined separately.

A common mistake is triggering the email on any update instead of only on the status transition. Another is sending before the record is successfully saved, which can create false alerts. Teams also forget to handle missing email addresses, duplicate sends, or the case where a record is already in the completed state when the update runs.

Yes. The mailer template is the right place to change the subject line, body copy, and the fields included in the message. You can add record name, status, completion time, or a link back to the detail screen. Keep the message short and action-oriented so it is easy to scan in an inbox.

In spreadsheets, someone has to notice the status change and remember to send the email, which is easy to miss when the list gets busy. This template automates the handoff at the moment the record reaches its final state. That gives you a repeatable notification path without relying on manual follow-up.

Confirm the exact final status value, the creator field, and the email delivery settings in your app. Test the update flow with a sample record so you can verify the message only sends once and reaches the right person. It is also worth checking how the app behaves when the creator has no email address or when the status is changed back and forth.