Release v0.38.2

🤖 AI-Generated Changelog

No user-facing changes in this release.

---

🔗 Full Changelog: v0.38.1...v0.38.2

Release v0.38.1

🤖 AI-Generated Changelog

Changed

• Bumped version from 0.38.0 to 0.38.1

---

🔗 Full Changelog: v0.38.0...v0.38.1

Release v0.38.0

🤖 AI-Generated Changelog

Changed

• Extended notification batching support to all WorkflowNotification event types, ensuring consistent batching behavior across all workflow notification events

---

🔗 Full Changelog: v0.37.17...v0.38.0

Release v0.37.17

🤖 AI-Generated Changelog

Fixed

• Corrected input alignment drift in shared rows when field labels wrap to multiple lines

---

🔗 Full Changelog: v0.37.16...v0.37.17

Release v0.37.16

🤖 AI-Generated Changelog

Removed

• Dropped legacy notify_on_* fields and four legacy notification tasks, streamlining the notification system and removing deprecated configuration options

Migration note: If your workflow configurations or code reference any notify_on_* fields or the associated legacy notification tasks, these must be updated to use the current notification system before upgrading.

---

🔗 Full Changelog: v0.37.15...v0.37.16

Release v0.37.15

🤖 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

Release v0.37.14

🤖 AI-Generated Changelog

Fixed

• Eliminated redundant database queries in workflow processing, improving performance for high-traffic scenarios
• Resolved N+1 query issue in admin list views, reducing database load when viewing workflow records

---

🔗 Full Changelog: v0.37.13...v0.37.14

Release v0.37.13

🤖 AI-Generated Changelog

Fixed

• Fixed WorkflowNotification admin configuration
• Suppressed approval history display in email notification contexts

---

🔗 Full Changelog: v0.37.12...v0.37.13

Release v0.37.12

🤖 AI-Generated Changelog

Added

• Granular workflow-level notification rules (WorkflowNotification): Administrators can now configure independent, per-event email notification rules directly on a workflow definition. Each rule specifies:
  • Trigger event: submission received, final approval, final rejection, or withdrawal
  • Dynamic recipients: resolved at send time from a form field value (e.g. advisor_email)
  • Static recipients: fixed comma-separated email addresses
  • Optional conditions: same JSON format as stage trigger conditions — rule is skipped if conditions are not met against the submission's form data
  • Custom subject line: supports {form_name} and {submission_id} placeholders; falls back to a sensible default if left blank
• Withdrawal notification dispatch: Workflow-level notification rules are now also triggered when a submission is withdrawn by the submitter
• Admin UI support: WorkflowNotification rules are configurable as an inline on both the WorkflowDefinition admin page and the FormDefinition change page

---

🔗 Full Changelog: v0.37.11...v0.37.12

Release v0.37.11

🤖 AI-Generated Changelog

Added

• Phone number fields now display a placeholder (555) 867-5309 to guide users on the expected format
• Draft submissions viewed on the submission detail page now show Continue Editing and Discard Draft action buttons, allowing submitters to resume or abandon their draft directly from the detail view

Changed

• Phone number field validation now enforces a stricter format: (###) ###-#### for domestic numbers and +## (###) ###-#### for international numbers. Previously accepted formats like 555-555-5555 or +1 555 555 5555 are no longer valid — existing data or integrations relying on the old format should be updated accordingly
• Updated phone validation error message to clearly show the accepted format examples

---

🔗 Full Changelog: v0.37.10...v0.37.11