When users perform a Recorded Run (RR) they need to specify the 'driver' script that executes their workflow, which we call the Run Configuration. This is a parameter that should be able to be changed each Recorded Run (Recorded Run 'A' doesn't need to use the same Run Configuration as Recorded Run 'b'). For this reason, the Run Configuration should be saved with each 'Run'. Note that this would require versioning 'Runs' instead of 'Versions'.
Since this parameter is essential for performing the recorded run, it needs to be saved
Within the Whole Tale system so that the Recorded Run can be run again (vs ephemerally passing it to the RR)
Within the manifest of exported Tales so that imported Tales with recorded runs can be re-run, using the same run configuration
When users perform a Recorded Run (RR) they need to specify the 'driver' script that executes their workflow, which we call the Run Configuration. This is a parameter that should be able to be changed each Recorded Run (Recorded Run 'A' doesn't need to use the same Run Configuration as Recorded Run 'b'). For this reason, the Run Configuration should be saved with each 'Run'. Note that this would require versioning 'Runs' instead of 'Versions'.
Since this parameter is essential for performing the recorded run, it needs to be saved