Difference between revisions of "TaskFlow/SaveAndRestore"
< TaskFlow
Akarpinska (talk | contribs) |
Akarpinska (talk | contribs) (Save restore task flow doc is created) |
||
| Line 1: | Line 1: | ||
Save and restore task flow. Brief description. | Save and restore task flow. Brief description. | ||
| − | What should be saved: | + | What should be saved:<br /> |
1. Task name (or other identifier, unique for each task). | 1. Task name (or other identifier, unique for each task). | ||
2. Task data required to execute and revert. | 2. Task data required to execute and revert. | ||
| Line 9: | Line 9: | ||
6. Flow state. | 6. Flow state. | ||
| − | Restoring the flow: | + | Restoring the flow:<br /> |
'''Flow can be created from the blocks template (as a new flow)'''. Then Flow state, kwargs and tasks data should be restored and set. Executed actions should be added to the proper collections. After the Flow can be resumed. | '''Flow can be created from the blocks template (as a new flow)'''. Then Flow state, kwargs and tasks data should be restored and set. Executed actions should be added to the proper collections. After the Flow can be resumed. | ||
Revision as of 14:44, 6 August 2013
Save and restore task flow. Brief description.
What should be saved:
1. Task name (or other identifier, unique for each task).
2. Task data required to execute and revert.
3. Task state (executed, failed, etc).
4. Executed actions ids.
5. Flow kwargs.
6. Flow state.
Restoring the flow:
Flow can be created from the blocks template (as a new flow). Then Flow state, kwargs and tasks data should be restored and set. Executed actions should be added to the proper collections. After the Flow can be resumed.
