Resolve SYSDF_NULL System Event

[Rajandeep98]

Title

Add dissolve event to filing table for backtrack system event.

Description

Update the filing table to support recording an system event .

Requirements

• Add the required system event record to the filing table for backtrack line activity.
• Follow the existing event structure and conventions used by other filings.
• Include the relevant timestamp and audit information.

Acceptance Criteria

• A system event is created in filing for the applicable backtrack line.
• The event contains the correct event type and backtrack line reference.
• Existing functionality and event handling are unaffected.

[Rajandeep98]

SYSDF_NULL is migrating properly with involuntary dissolution filing.

[vishnup0422]

Hello @Rajandeep98, Can you please provide Testing Instructions !

Thank you !

[vishnup0422]

Ticket #35040 / #34989 — SYSDF_NULL validation summary

Checked all 12 corp_nums from ticket #35040 (BC0694820, BC0694866, BC0695388, BC0695471, BC0695508, BC0695616, BC0695710, BC0696149, BC0696558, BC0696847, BC0696872, BC0697068) for correct migration of the SYSDF_NULL involuntary-dissolution fix (#34989).

COLIN side: confirmed all 12 have a SYSDF event with no filing row (the SYSDF_NULL pattern) followed by an HDF/HIS dissolved state, and all 12 later restored to ACT.
LEAR side: confirmed all 12 migrated with a matching dissolution/involuntary filing (timestamps exact match to COLIN's SYSDF event) followed by a restoration/fullRestoration filing — business summaries correctly show the involuntary dissolution.
Result: 12/12 pass. SYSDF_NULL fix validated clean.
Side note (not a defect): BC0695388 currently shows HISTORICAL state, but that's from a separate, later dissolution/administrative filing dated 2026-09-21 (post-migration-tombstone) — unrelated to the SYSDF_NULL fix. Flagged for Rajandeep to confirm it's expected in the QA batch.

[vishnup0422]