Hi all. When using FixtureScripts, there can be many actions that, on the real world, are execute in different time contexts.
For example, a user creates an Account on the webapp and after that executes different actions. That’s relevant if using the queryResultsCache service (or the new planned “@Action” annotation extension) because the results previously created (i.e., the Account) might be available on the cache. So perhaps some mechanism like the nextTransation() method might be also introduced on FixtureScripts. What do you think? Regards, Oscar
