Commands  ›  Clash Manager / Forma  ›  Qa Manager Push Issues To Autodesk Forma

Qa Manager Push Issues To Autodesk Forma

Clash Manager / Forma writes to model Public API · not yet exposed

Coming soon

Before you run this

APS bearer token + project id supplied; network; ≥ 1 matching clash.

After it runs

0-N APS issues created; clash rows updated with issue id via comment append.

When to use this

Don't use this when

Acquiring the OAuth token itself — done by DocumentController.

Inputs

NameKindTypeRequiredDefaultDescription
PresetKind config string no "clash_tolerances" Deterministic config preset

Decision flow

1) bearer token + project id required; WireError otherwise.
2) Pull rows from repo.ListByState(state_filter ?? "active").
3) For each, render title/description via DescriptionTemplateService.
4) await PushClashAsFormaIssue.PushAsync(payload).
5) On ok, append comment "Pushed to Forma as issue {id}" via repo.TransitionState (state unchanged).
6) Aggregate; emit summary.

What you'll see in the chat

on start
Pushing clashes to Autodesk Forma…
thinking
Listing matching clashes…
Rendering title + description from template…
POSTing issues via PushClashAsFormaIssue…
on success
Pushed {pushed}/{total} issues.
on failure
Forma push failed: {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/qa_manager_push_issues_to_autodesk_forma
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

qamanagerpushissuestoautodeskforma · push to forma · qa forma sync

PillarClash Manager / Forma