Can Fusion "Undo" removal of tasks if something on a project triggered it to remove tasks and the user wants the tasks back?

[amazingjameso]

I have a fusion scenario that builds a project "recertified" with tasks based on a template. if a user selects a certain Status "decommission" Fusion goes in and removes the tasks from the project and adds a new template with different "decom" tasks. Now, if the user didn't mean to choose that status or perhaps down the line, this project didnt need to be decom'd, can fusion be setup to undo, or re-add those old tasks back in and remove the decom tasks. Basically re-setting the project back to its original "recertified" state again? would this take a large level of work to build this scenario or would it be better to tell the users to be careful in their choice?

[Lawson02]

If the user may have accidentally selected the choice you can add a sleep module right after your event trigger then a read which will recheck the object to make sure the status is still the same.

For the recertified state it would probably depend on how much information you needed to store. Off the top of my head, not saying this is the only way, you would probably need to export essential project data, assignees, comments, ect. and then retrieve that when you're rolling back the project. This would cause data loss within the task's states themselves but the project log would still contain all it's events.

[Sven-iX]

Hey @amazingjameso 
Rather than deleting, if you create a parent task at the bottom of the list, and MOVE those tasks, you don't lose anything. You could even change durations and planned hours so they don't affect the plan (and store them in custom fields you can read out if you need to undo). 

But - it depends on when users make that change: If they do it while the project is not live - I would have 2 template snippets (the decom and the recertified tasks. Then you delete the tasks not wanted, and attach the appropriate snippet and if needed move them to the right spot. Depending on the complexity of your project schedule (task structure) and whether you would need to conserve any in-flight data (ie user changes project type while project is active) - the template swapping might be easiest. 

Oh another option: 
If a user makes the change, create a copy of the project; set the current one to DED/Cancelled and modify the new copy; set a custom field that the decomm project is ID XXXXXX. "reverting" then means Cancelling the recert project and reenabling the Decomm project.