MD.OFFICE
FAL

Daily Log - 2026-05-21

Filing Initiation Email Alerts (Phase 1 & 2)

Achievements

  • Scope Pivot: Shelved "email on dynaform submission" approach and transitioned to a "filing initiation" flow executing upon successful file metadata validation.
  • Core Trigger Logic: Added two separate alert types for normal filings and Fit & Proper (F&P) filings. Hooked request generation into FileMetadataValidationEmailFilterImpl.
  • Liquibase Migrations: Authored a dedicated, idempotent changelog to register alerts, default expression variables, and HTML body templates using sequence reset blocks.
  • F&P Recipient Fixes: Enhanced F&P recipient resolution to lookup emailOfFPInitiator via explicit repository query (tbl_dynaform_fp_initiation.created_by) to ensure initiators are notified reliably.

Decisions

  • Template Simplification: Simplified alert body templates by removing ambiguous multi-variables, retaining only reliable keys (Return Name, Entity, Upload ID) with explicit <br>/<p> paragraph formatting.
  • Payload Management: Decided against synthetic otherData injection for initiation alerts, utilizing linked filing-upload ID resolutions to derive variables predictably in the backend resolver.

Technical Details

  • Added: field.emailAlert.filing.initiated and field.emailAlert.fitProper.filing.initiated constants.
  • Added: V1_1779100000000_create_filing_initiated_email_alerts.xml using dynamic sequence lookups (MAX+1) for master tables.