Skip to content

Release v0.37.15

Choose a tag to compare

View all tags
@github-actions github-actions released this 27 Mar 19:28
· 113 commits to main since this release
v0.37.15
b9c7038

🤖 AI-Generated Changelog

Added

  • notify_submitter field on WorkflowNotification: Workflow notification rules now support a dedicated "Notify submitter" toggle. When enabled, the form submitter is automatically included as a recipient, replacing the need for legacy per-event notify flags.

Changed

  • Third/fourth-width form fields now render side-by-side: Consecutive fields set to third or fourth width are grouped into a single row, so they actually appear in a multi-column layout as intended rather than each on its own row.
  • WorkflowNotification admin layout: The notify_submitter toggle is now displayed prominently alongside notification_type, and email_field/static_emails are grouped together on the same row for clarity. notify_submitter is also exposed as a list column and filter in the admin list view.
  • Legacy notify flags marked as deprecated in admin: The "Legacy Notifications" section in the WorkflowDefinition admin is now labelled as deprecated and includes updated guidance explaining that a data migration has already converted enabled flags into WorkflowNotification rows.

Deprecated

  • Legacy notify_on_* flags (notify_on_submission, notify_on_approval, notify_on_rejection, notify_on_withdrawal): These per-event toggles on WorkflowDefinition are superseded by WorkflowNotification rows with notify_submitter enabled. The legacy tasks (send_submission_notification, send_approval_notification, send_rejection_notification, send_withdrawal_notification) now exit early when a corresponding WorkflowNotification row exists, preventing duplicate emails. The legacy flags remain functional for now and will be removed in a future release.

Migration Notes

  • A data migration (0067) automatically converts all enabled legacy notify_on_* flags into WorkflowNotification rows with notify_submitter=True. Any additional_notify_emails are preserved as static_emails on the new rows. The migration is idempotent and will not create duplicate rows if a WorkflowNotification for that event already exists.
  • After migrating, verify that WorkflowNotification rows appear in the admin for each workflow that previously had legacy flags enabled, then optionally disable the legacy flags.

🔗 Full Changelog: v0.37.14...v0.37.15

Assets 2
Loading