Skip to main content
September 15, 2026
Question

Fusion Scenario Documentation

  • September 15, 2026
  • 3 replies
  • 42 views

Hi!

Looking for some help here. :) 

I watched a Adobe video a while back that someone shared how they use AI to help document the Fusion scenario by using exported JSON file and prompt the AI to fill a template out. Back then, our team hasn’t started the automation yet. (I should’ve bookmarked it.) Now that we start to leverage Fusion, I want to capture proper documentation but can’t find the video anymore. 

Does some know which video that is or have something they can share on this topic?

Thank you in advance for any of your sharing!

3 replies

Level 2
September 16, 2026

Hi,

I haven't watched the video, but I've used Copilot to document Fusion scenarios by exporting the scenario JSON and providing it to Copilot for analysis and documentation. If you have a reference document, Copilot can use it as a template and try to align the output with the same structure and style. Otherwise, the default output is usually a good starting point. From there, you can iteratively refine both the prompt and the document, creating a reusable template that can serve as a reference for future documentation efforts.

Level 1
September 16, 2026

Hi Maureen, I’m a fusion developer - I haven’t seen the video neither, but vk2023 is spot on.

In addition, to reduce iterations of the output you get from the LLM or CoPilot in this case, you can follow the steps below. It’s helped save time and produced great documentation. You can always adapt it to your circumstance. I do have a template I can share with you.

Hope it helps!
Jide

 

Paste this prompt with the blueprint JSON and a template (if you have one) into your LLM of choice. Strip API keys, emails and hostnames from the JSON first if applicable!

You are documenting an Adobe Workfront Fusion scenario. I will give you (1) the exported scenario blueprint JSON and (2) a documentation template. Fill in every section of the template from the JSON.

Rules:

  • Number modules to match the id values in the blueprint's flow array.
  • Keep modules nested inside router routes grouped under their router; do not flatten them.
  • Translate every mapping expression and filter condition into plain English alongside the raw expression.
  • If the JSON does not contain the information (scheduling, connection names, business purpose, notification recipients), write "⚠ confirm manually" rather than inventing it.
  • Where error handling is absent, state that explicitly.
  • List anything you inferred under "Assumptions & Open Questions".
  • Output in Markdown, preserving the template's headings and table structure.
DavidGevorgyan
Community Manager
Community Manager
September 16, 2026

We also delivered a new feature that allows you to describe scenarios using AI

 

New Describe with AI button in Scenario description

You can now click Describe with AI in the description field of a scenario’s Settings panel to have AI generate a description of the scenario for you automatically, based on the scenario’s modules and configuration.

For more information, see Configure scenario settings.