Audited Actions

When vault auditing is enabled and the audit log database is correctly configured, the Meridian logs vault activity to the specified table. The table has the structure shown in the following table. The audit data is the same whether it is stored in a standalone database or in the Meridian Enterprise Server database.

Audit Table Structure

The structure of the audit table is listed in the table below.

Audit table structure
Field Name	SQL Data Type
ID	int IDENTITY
Vault	nvarchar(255) NOT NULL
Context	nvarchar(255) NULL
LoginName	nvarchar(255) NOT NULL
UserFullName	nvarchar(255) NULL
Action	nvarchar(255) NOT NULL
ActionArg1	sql_variant NULL
ActionArg2	sql_variant NULL
ActionArg3	sql_variant NULL
ActionDate	datetime DEFAULT UTCNow
ObjectID	uniqueidentifier NULL
ObjectName	nvarchar(255) NULL
ObjectPath	nvarchar(255) NULL
ObjectRevision	nvarchar(255) NULL

Vault Content Actions

Note:

The values of Action for built-in Meridian actions are predefined strings in English. Custom command action strings must be defined by the custom functions.

The vault content actions that the Meridian logs to the audit log database are listed in the following table. The values of the action arguments (for example, ActionArg1) depend on the action performed. Custom actions can also be logged with the Vault.AuditEvent method.

Show entries

Filter:

Meridian Enterprise vault content actions
Category	Action	ActionArg1	ActionArg2	ActionArg3	Notes
Document	Asset Management Module create reference	Destination document ID (string)	Reference type internal name (string)	Reference ID (string)
Document	Asset Management Module remove reference	Destination document ID (string)	Reference ID (string)
Document	CAD link create reference	Destination document ID (string)	Destination document name (string)	Destination document path (string)
Document	CAD link remove reference	Destination document ID (string)	Destination document name (string)	Destination document path (string)
Document	CAD link update properties from file
Document	CAD link update properties to file				This action is not logged when Application Integration is in Online mode because the property values can still be changed by the user or other software and those changes cannot be logged. Therefore, we recommend that the Invoke action be audited instead to detect potential document property changes. For the MicroStation link in Remote mode, occurs twice for each update.
Document	Change type	New document type name (string)
Document	Change property	<PropertySet>.<PropertyDef>	New property value (first 255 characters)	Old property value (first 255 characters)	Changes to memo type properties are only detected for the last 2000 characters.
Document	Change redlines
Document	Copy

Showing 1 to 10 of 114 entries

Previous1 2 3 4 5…12Next

Vault Configuration Actions

The vault configuration actions that Meridian logs to the audit log database are listed in the following table.

Meridian Enterprise vault configuration actions
Action	Information
Commands	Created, changed, or deleted
Configuration data	Imported or exported
Document types	Created, changed, or deleted
Environment	Changed
Event script	Changed
Extensions	Created, changed, or deleted
Field-Path definition	Changed
Folder types	Created, changed, or deleted
Lookup lists	Created, changed, or deleted
Navigation views	Created, changed, or deleted
Opened in Configurator	Opened or opened read-only
Pages	Created, changed, or deleted
Property definitions	Created, changed, or deleted
Property sets	Created, changed, or deleted
Reference types	Created, changed, or deleted
Reports	Created, changed, or deleted
Roles and privileges	Changed
Scopes	Created, changed, or deleted
Tables and queries	Created, changed, or deleted
Work area templates	Created, changed, or deleted
Workflow definitions	Created, changed, or deleted

Meridian Explorer Repository Actions

The repository actions that Meridian Explorer logs to the audit log database are listed in the following table.