After a scenario is approved, and then edited, the approved scenario is no longer public, and goes back in the reviewer queue.
Option 2:
After a scenario is approved, and then edited, the original is still public, and a new, temporary scenario is generated with the updated information and sent back through the reviewer process. When the reviewer approved the edit, :
2.a it will either remove the public boolean on the original scenario and turn it on for the new one that has the update. This would keep a history of the changes for audit purposes. This might take up lots of room in the DB.
Or
2.b it will merge the data into the original scenario and publish it.
Option 1:
After a scenario is approved, and then edited, the approved scenario is no longer public, and goes back in the reviewer queue.
Option 2:
After a scenario is approved, and then edited, the original is still public, and a new, temporary scenario is generated with the updated information and sent back through the reviewer process. When the reviewer approved the edit, :
2.a it will either remove the public boolean on the original scenario and turn it on for the new one that has the update. This would keep a history of the changes for audit purposes. This might take up lots of room in the DB.
Or
2.b it will merge the data into the original scenario and publish it.