Revelation for Confluence Documentation Email support
Revelation for Confluence

Create and update with Rovo

Describe the model you want, let a Revelation agent help with the first draft, then refine it with your team.

You do not need a finished specification to begin. Describe the people, systems or steps you already know, and ask for a small model first. After reviewing it, give the agent a specific change or refine the diagram yourself.

Choose the right agent

Use the Revelation agent for C4, BPMN Lite, Sequence, ArchiMate, ER or Flowchart. Your site must provide access to the relevant Rovo AI features, and you need permission to edit the destination page. An agent operates on its own notation; it does not convert between all six types.

Create a first model

  1. Open Rovo in the context of the intended page and choose the Revelation C4 agent.
  2. Provide a request such as the example below. Supply the page ID if the agent cannot establish it from context.
  3. Review the result and keep the returned diagram ID.
  4. Insert or configure a Revelation diagram macro, choose Use a diagram already attached to this page, and select the new model.
  5. Inspect the diagram and its properties. Use Edit to refine it, then Save to page.
Create a C4 model called Student service on this page.
Include a Student actor, a Student portal system and a Student records datastore.
Student uses the portal. The portal reads and updates student records.
Set Owner to Registry on the datastore.

Update the same model

Give the agent the page and existing diagram ID, then request a bounded change. Ask it to read the current model before updating it. For example:

Update the existing Student service model, diagram ID [diagram ID], on page [page ID].
Read its current version. Rename Student portal to Student self-service.
Keep the existing IDs, relationships, custom properties and views.

The diagram ID is the model identifier returned by creation or contained in the attachment filename revelation-model-<diagram ID>.json. The page ID identifies the Confluence page. Use trusted page information or ask the page owner if you cannot find it; the read action is not a general diagram-search service.

What Rovo preserves and cannot do

Updates preserve existing view/layout settings and retained record IDs when used correctly. An added element may not enter an explicitly scoped view. Agents create or update attachments; they do not insert macros or create views. Use the editor for those tasks.

Custom properties in agent inputs must be scalar values: text, finite numbers, booleans or null. Full notation validation is not guaranteed. Review BPMN pool boundaries, sequence order and the meaning of architecture relationships.

Conflicts and uncertain saves

If the model changed after the agent read it, it should reread and reapply the requested edit. Repeated conflicts need coordination with other editors. Version checks reduce stale updates but are not an exclusive editing lock.

If the save outcome is uncertain, inspect the page attachment and model before asking for another creation. A timeout can occur after a write succeeded. Do not assume a failed response means no model was saved.

Next steps