Validate and smoke tests

Goal: confirm a healthy baseline after installation.

SQL checks

  • Database exists; key tables present (e.g., MFProcessBatch, MFContextMenu)

  • Run a minimal check (examples): - exec spMFUpdateAssemblies (returns OK — reloads/confirms the CLR assemblies) - SELECT TOP 1 * FROM setup.MFVaultSettings

  • Since 5.13.38.82, confirm the automatic reload path is in place on the Integration Connector: the MFSQL Validate M-Files Version SQL Agent job exists, and (if applicable) the WMI Event Alert deployed by 35.703.script.CreateMFilesUpdateAlert.sql exists for each MFSQL application database. On SQL Server Express (no SQL Agent), neither exists by design — run spMFUpdateAssemblies manually after any future M-Files upgrade instead.

M‑Files checks

  • VAF application appears in M‑Files Admin; dashboard loads

  • License status visible (until license added it will show unlicensed)

Context menu check (optional)

  • Insert a simple menu row into MFContextMenu and validate it shows for test users

  • Trigger an action and confirm entries in MFProcessBatch and MFProcessBatchDetail

See also