I have a scenario variable in a workshop app and within the scenario, I create an object with a randomly generated primary key. The object shows up in the table reading the object set from the scenario. Great.
Now if I create a button to apply the scenario (and have a longer running follow-up action), I can reset the scenario variable only after the follow-up action was applied. This results in a timeframe where two objects are displayed since the apply scenario event re-runs the action on the scenario and likely two objects with distinct primary keys are generated?.
To my best knowledge, the follow-up action runs not on the scenario but after it was applied. I think it would make sense to be able to reset the scenario variable immediately after it was applied - not only after the follow-up action.
For my users it is disturbing to see more than one object created for a few seconds - it confuses them.
While I do like the concept of scenarios, things like this make it hard to implement with good user acceptance. Also the fact that a lot of actions do not work e.g. in table mode. In addition, the “apply to scenario” button message can not always be overwritten e.g. when editing an object table. This may be hard to explain to users when they dont know / care about the implementation, only about the result e.g. being able to edit multiple objects one after another before committing the changes similar to a DB transaction.