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
    • Procedures and functions used by Connector
  • Naming Convention prefixes
  • Custom changes
  • Procedures and functions for applications
• M-Files Installation
• Context Menu
  • Context Menu Procedures
    • Procedure without input parameter (action type 1)
    • Procedure with object version as input parameter (action type 3)
  • Formatting result message for UI
    • Line Breaks in output
• 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 programs (.dll) to enable the interaction between M-Files and SQL. The main purpose of the assemblies is to wrap the standard M-Files API’s into code classes that allows data to be extracted from M-Files into SQL tables and also to update M-Files from the SQL Tables. There are four assemblies included.

• The Metadata Structure Tables contain the metadata of the vault, settings, and transaction logging data. The Connector tables are all prefixed with MF to distinguish them from non Connector tables in the database. The Metadata tables is about metadata table contain the information about the structure of M-Files (e.g. classes, properties, valuelists etc. ) Connector Table related to this type of metadata include Object Types; Classes; Properties; ClassProperty; Valuelists; Valuelist items; Workflows; Workflow States; UserAccounts; LoginAccounts

  • Utility Tables are Connector supporting tables and include: Datatypes; Settings; Process; DeploymentDetail

  • Logging Tables reference processing logs and unclude: MFLog; UpdateHistory; ProcessLog

  • Class tables represent the data in the vault such as Customers, Contacts and any other class in the vault. Class tables are not created by default, but created when the data that is required for the specific application has been determined. The Class Tables therefore represent the metadata of the specific classes of objects that the application will interact with.

• Procedures and Functions are T-SQL procedures and functions to perform operations on the tables and the use the assemblies.

• Context Menu controls users interaction with SQL from within M-Files

• Supporting Applications include several utilities and sample files as general add-ons to the product

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