Running through the full loop for a scenarios-based workflow and noticed that the scenario once applied is NOT auto-deleted. What is considered best practice to prevent users from accidentally applying a scenario twice? Is it best to delete them afterwards? If so, why is auto-delete not enabled?
When applying a scenario, do we have to delete the scenario as well, to prevent applying the changes twice?
65 Views Asked by mpena At
1
There are 1 best solutions below
Related Questions in FOUNDRY-SCENARIOS
- Correctly formatting boolean in bar chart with scenario
- Apply scenario on inline edit in table
- Foundry Scenarios edited data materialized as dataset
- What is the difference between closing/X'ing out of an action and undoing an action in the Foundry Scenario summary widget?
- Does Foundry Scenarios support Quiver?
- What's the difference between “scenario to load data from” set to a dynamic scenario variable and “compare against scenario” set to a scenario array?
- In Foundry Scenarios, what does the delete button do when a Scenario is saved and backed by an Object?
- In Foundry Scenarios, Is it possible to run functions across multiple scenarios?
- In Foundry Workshop, is it possible to reset a scenario when a user navigates away from a Workshop tab?
- How can I save a Foundry Scenario and use it in another Workshop module?
- In Foundry Workshop, how do I save and writeback all values set within a Scenario?
- When applying a scenario, do we have to delete the scenario as well, to prevent applying the changes twice?
- How to pass the scenario id as a parameter in Workshop?
- Is it possible to run a modification action and then a function following it in workshop?
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
you could delete but usually I would add a flag called "applied" and filter my list of displayed scenarios by
"applied" == falseor something like that.If you ever want to use your scenarios for metrics. E.g. how many scenarios have been applied / maybe write some stats to the scenario object on apply this data is all lost if you're deleting on apply. I believe that's also why it's not part of the workflow by default. The idea is that you should make that decision for your use case.