Docs
Search K

Appearance

Core Capture Concepts ​

Capture is built on a small number of fundamental concepts. Understanding these building blocks is essential to effectively using and configuring the system.

Capture Template ​

What is it? ​

A Capture Template defines the structure, behavior, security, and lifecycle of captures created from it.

Think of a template as a blueprint that determines:

  • What submission type to use (Submit vs Approve/Reject)
  • Who can access captures created from this template
  • What fields are displayed and required
  • What happens when a capture is submitted, approved, or rejected
  • How artifacts are handled and validated

Where are they managed? ​

Templates are created and configured in:

Console → Capture Templates

Key Template Properties ​

  • Name - Display name shown to users
  • Submission Type - Submit only, or Approve/Reject workflow
  • Security Roles - Controls who can create and access captures
  • Fields Configuration - Custom fields and metadata
  • Event Handlers - PowerShell scripts or workflows triggered on actions
  • Artifact Rules - How associated files are validated and managed
  • Mesh Integration - Whether template is available in Mesh

Example Templates ​

  • "Drawing Transmittal" - For submitting drawing packages to clients
  • "Engineering Review" - For approve/reject reviews of design documents
  • "AI Validation" - For human review of AI-generated outputs
  • "Change Request" - For approval of proposed system changes

Capture ​

What is it? ​

A Capture is a single instance created from a template. Each capture represents one specific review, submission, or approval process.

Capture Lifecycle ​

Created → Open → In Review → Completed (Submitted/Approved/Rejected)

What's in a Capture? ​

Each capture contains:

  • Metadata - Fields defined by the template
  • Associated Artifacts - Links to files or records being reviewed
  • Timeline - Complete history of all actions and state changes
  • Markups - Visual annotations added during review
  • Status - Current state (open, under review, approved, rejected, etc.)

Example Captures ​

  • Capture #12345: "Project ABC Drawing Package Transmittal"

    • Created from: "Drawing Transmittal" template
    • Artifacts: 15 PDF drawings
    • Status: Submitted

  • Capture #12346: "Pump Assembly Design Review"

    • Created from: "Engineering Review" template
    • Artifacts: 1 Inventor assembly, 3 drawings
    • Status: Approved with markups

Artifact ​

What is it? ​

An Artifact is an external record or file associated with a capture. Artifacts are the items being reviewed, approved, or submitted.

Types of Artifacts ​

Artifacts can be:

  • Vault files - CAD drawings, models, documents stored in Autodesk Vault
  • Documents - PDFs, Office documents, specifications
  • Records - Database records or system objects
  • External files - Files from network locations or other systems

Artifact Association ​

Artifacts can be added to captures:

  • Manually by users during capture creation
  • Automatically by workflows
  • From Mesh search results
  • Via API or system integrations

Artifact State Management ​

Capture tracks the state of artifacts to detect changes during review. If an artifact is modified while a capture is in progress, the capture may become "stale" (see Configuration Guide for stale capture management).

Inbox ​

What is it? ​

The Inbox is the user-facing queue where captures appear for action.

Inbox Features ​

Users can:

  • View all captures requiring their attention
  • Filter by template type
  • Filter by capture status
  • Filter by custom field values
  • Sort and search captures
  • Open captures for review

Access Control ​

The inbox only shows captures that:

  • The user has permission to access (role-based)
  • Match the user's assigned responsibilities
  • Are in states requiring action

Review Environment ​

What is it? ​

The Review Environment is the dedicated UI for reviewing, marking up, and completing a capture.

Available in Two Versions ​

  • Legacy Capture Environment - Original interface
  • Modern Capture Environment - Improved performance, better tools (recommended)

The environment is selected in the template configuration.

What Can You Do in the Review Environment? ​

  • View artifacts - Open associated files and documents
  • Add markups - Annotate drawings and documents visually
  • Review metadata - See all capture fields and data
  • Add comments - Provide feedback and instructions
  • Take action - Submit, approve, or reject the capture
  • View timeline - See complete history of the capture

Model Viewing ​

The review environment can display:

  • 2D CAD drawings (AutoCAD DWG, DXF)
  • 3D models (Inventor, STEP, other formats)
  • PDF documents
  • Images and other file types

A Model Viewing Service Account controls what files can be accessed and displayed.

Submission Types ​

Capture supports two submission types configured at the template level:

Submit ​

Use when: Simple submission or data collection is needed

Behavior:

  • User creates capture
  • Adds artifacts and fills in fields
  • Clicks "Submit"
  • Capture is completed

Example use cases:

  • Document transmittals
  • Data collection forms
  • Request submissions

Approve / Reject ​

Use when: Review and approval decision is required

Behavior:

  • Capture is created (by user or automation)
  • Reviewer opens the review environment
  • Reviews artifacts and metadata
  • Clicks "Approve" or "Reject" with comments
  • Different actions can be triggered based on outcome

Example use cases:

  • Engineering reviews
  • Quality approvals
  • AI validation
  • Change request approvals

Event Handlers ​

What are they? ​

Event handlers are automations that execute when specific capture actions occur.

When Do They Run? ​

  • On Submit - When a capture is submitted
  • On Approve - When a capture is approved
  • On Reject - When a capture is rejected

Two Types ​

Legacy: PowerShell Scripts ​

  • Custom PowerShell code executed on the MinuteView server
  • Direct access to Vault APIs and system resources
  • Configured in template settings

Modern: Workflow Integration ​

  • Triggers MinuteView workflows
  • Recommended for new implementations
  • Better integration with other automation
  • Easier to maintain and debug

Example Event Handlers ​

  • On Approve: Trigger workflow to publish drawings to document control
  • On Submit: Send notification email to project manager
  • On Reject: Create task for original author to address feedback

Capture States ​

Captures move through different states during their lifecycle. Understanding states is important for filtering, reporting, and automation.

Common states:

  • Open - Capture created, awaiting review
  • Under Review - Reviewer has opened the capture
  • Submitted - User has submitted (for Submit type)
  • Approved - Reviewer has approved (for Approve/Reject type)
  • Rejected - Reviewer has rejected (for Approve/Reject type)
  • Stale - Associated artifacts have changed

See Reference: Capture States for complete details.

Security & Roles ​

Capture uses role-based access control to determine who can:

  • Create captures from specific templates
  • View captures in their inbox
  • Approve or reject captures
  • Access specific artifacts

Roles are assigned to users in the MinuteView Console and enforced consistently across all capture interfaces.

Next Steps ​

Now that you understand Capture's core concepts, you're ready to:

Tentech