Commands  ›  Architecture / Comments  ›  Architecture Load Client Comments From Revision Clouds In Current Model

Architecture Load Client Comments From Revision Clouds In Current Model

Architecture / Comments writes to model Public API · not yet exposed

Coming soon

Before you run this

Revision clouds placed in the current model with comment text on the Comment / Mark / Description parameter. Project comment register configured.

After it runs

One comment row per revision cloud, linked back to the cloud's element id, view and revision; existing rows updated by element id; revision clouds untouched.

When to use this

Don't use this when

Revision clouds carrying drawing changes (those are revisions, not comments), or models without revision-cloud comments configured.

Decision flow

1. Find every Revision Cloud in the current document.
2. Read its Comment / Mark / Description parameter and the views it sits on.
3. Resolve the view + revision id for each cloud.
4. Create or update a comment row per cloud (keyed by cloud element id) in one Transaction.
5. Report rows created vs updated and any clouds skipped (no comment text).

What you'll see in the chat

on start
I'll harvest the revision clouds into the comment register now.
thinking
Reading each cloud's comment text and resolving its host view and revision.
on success
Done — {n_created} comments created, {n_updated} updated from {n_clouds} revision clouds.
on failure
Couldn't harvest revision clouds: {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/architecture_load_client_comments_from_revision_clouds_in_current_model
  • Request body schema (from [RestApiParam])
  • Response schema (from [RestApiResponse])
  • curl / JS / Python code examples

Keywords & intent patterns

revision cloud comments · in-model comments · harvest revision clouds · comment from clouds · register sync

PillarArchitecture / Comments