Understanding the Requirement:
The user needs to view the exact API request and the corresponding response a module executes in
Adobe Workfront Fusion.
This is critical for debugging, troubleshooting, or validating API operations within scenarios.
Why Option B is Correct:
Execution History:
The execution history logs detailed information about every module that runs in a scenario.
It provides access to the API request sent, including the headers, parameters, and body.
It also displays the API response received, including HTTP status codes, returned data, and error
messages (if applicable).
This feature is indispensable for debugging and verifying the behavior of modules.
Why the Other Options are Incorrect:
Option A ("Using the Bundle Inspector"):
The Bundle Inspector provides a view of processed data bundles but does not include API
request/response details.
Option C ("Using the Fusion DevTool scenario debugger"):
Fusion does not have a specific "DevTool debugger." The execution history serves this purpose.
Option D ("Using the Fusion DevTool error evaluator"):
While error logs help evaluate issues, they do not directly show the API request/response unless an
error occurs. Execution history is a more comprehensive source of this data.
Steps to View Execution History:
Run the scenario or inspect a previously executed scenario.
Navigate to the Execution History tab for the scenario.
Select a specific module to view its details.
Inspect the API request and response, which includes all relevant parameters and data.
Reference and Supporting Documentation:
Adobe Workfront Fusion Documentation: Execution History
Workfront Community: Debugging with Execution History
