When building or editing a scenario, I often need to check the execution history to see exactly what data was returned by specific modules and how that data was formatted. This is especially useful when updating an existing scenario or continuing work on a scenario that depends on real execution data.
While it is possible to run a module individually, this can become difficult when the module requires parameters. In those cases, you first need to find or recreate the correct input data, which can take time. Most of the time, it is much easier to inspect a previous execution and look at the actual data that was returned.
At the moment, when I am working in the scenario editor, my workflow looks like this:
  1. Shift-click the scenario button in the menu to open it in a new tab.
  2. Open the scenario again.
  3. Go to the History tab.
  4. Open the execution I want to inspect.
This means I end up with two tabs open just to check the data returned by a module.
I have two suggestions that could improve this workflow:
  1. Load module metadata or output from a previous execution
It would be very useful to right-click a module and have an option such as:
“View data from previous execution”
or
“Refresh metadata from execution”
This would allow users to inspect the actual data returned by that module in a past run without leaving the scenario editor. It could also help when configuring mappings or troubleshooting formatting issues.
  1. Quick access to scenario history
As a simpler improvement, add a button in the scenario editor that opens the scenario history directly in a new tab.
This would already remove several steps from the current workflow and make it much faster to inspect previous execution data while actively building a scenario.