Commands › › Launch Document Controller

Launch Document Controller

writes to model Public API · not yet exposed

Coming soon

Before you run this

DocumentController.WPF.exe must have been built at least once (dotnet build DocumentController/DocumentController.WPF/DocumentController.WPF.csproj) OR be deployed alongside the Adelphos add-in in the ApplicationPlugins folder.

After it runs

A DocumentController.WPF window is visible on the desktop. If a prior instance existed, that window is brought to the foreground. If the exe cannot be found, a recoverable error is raised listing every probed path for the user.

When to use this

User clicks the "Doc Controller" ribbon button to open the standalone document management desktop app while continuing to work in Revit.

Don't use this when

Hosting the Document Controller inside Revit (it is intentionally a separate process so it can run without Revit and share the web/desktop chat core). Launching from headless automation — requires a Windows desktop session.

What you'll see in the chat

on start

Launching the Document Controller desktop app...

thinking

Looking for DocumentController.WPF.exe in known locations...

on success

Document Controller is open.

on failure

Could not launch Document Controller: {error}

REST API

Not yet exposed

This command does not carry a [RestApi] attribute today. Once tagged, this section will auto-populate with:

POST /api/v1/commands/launch_document_controller
Request body schema (from [RestApiParam])
Response schema (from [RestApiResponse])
curl / JS / Python code examples

Keywords & intent patterns

open document controller · launch doc controller · document controller app · issue documents · drawing issue sheet · bim 360 upload
Patterns: open * document controller · launch * doc controller · start * document controller

Pillar