Connector Content

• Assemblies
• Metadata Structure Tables
• Class tables
  • Class Table Columns
  • Class Tables and there columns
  • MF Ad-hoc Columns
  • Non Connector Columns
  • Special columns
  • Default columns
  • Process_id values
  • Indexes on class tables
  • Object change history
  • Object Versions
• Utility Tables
  • MFDataType
  • MFDeploymentDetail
  • MFSettings
  • MFProcess table
• Logging Tables
  • Class Record Updates
  • Procedure Processing logs
  • Error logs
• Procedures and Functions
  • spMFCreateObjectInternal
  • CLR and internal procedures
  • Naming Convention prefixes
  • Custom changes
  • Procedures and functions for applications
• M-Files Installation
• Context Menu
  • Context Menu Procedures
  • Formatting result message for UI
• Supporting Applications
  • Custom tables, views, procedures and functions
  • Code On Time
  • Content
• MFSQL Connector Operations
  • Scope of MFSQL Connector
  • Operations related to setup
  • Operations related to the metadata structure
  • Operations related to metadata alignment
  • Operations related to class objects
  • Operations related to monitoring, analytics and exploration of results
  • Operations related to processing activity

The Connector components supplied as part of the deployment package include:

• The Assemblies are proprietary assemblies (.dll) that enable interaction between M-Files and SQL. They wrap the standard M-Files APIs into classes that allow data to be extracted from M-Files into SQL tables and updated back to M-Files from SQL tables.

• The Metadata Structure Tables contain the metadata of the vault, settings, and transaction logging data. Connector tables are prefixed with MF to distinguish them from non‑Connector tables. Metadata tables capture the structure of M-Files (e.g., classes, properties, value lists, etc.). Related tables include: ObjectTypes, Classes, Properties, ClassProperty, ValueLists, ValueListItems, Workflows, WorkflowStates, UserAccounts, and LoginAccounts.

• Utility Tables are supporting tables and include: DataTypes, Settings, Process, DeploymentDetail.

• Logging Tables reference processing logs and include: MFLog, UpdateHistory, ProcessLog.

• Class tables represent the data in the vault (e.g., Customers, Contacts). Class tables are created only for classes used by the application.

• Procedures and Functions are T‑SQL procedures and functions that operate on the tables and invoke the assemblies.

• Context Menu controls user interactions with SQL from within M-Files.

• Supporting Applications includes utilities and sample files as add‑ons to the product.

• M-Files Installation installs components in the vault, including the content package, vault applications, and UI extensibility applications.