status-im
/
spiff-arena
mirror of https://github.com/status-im/spiff-arena.git
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
spiff-arena/docs/Building_Diagrams/task_data.md

18 lines
1.1 KiB
Markdown
Raw Normal View History

update the docs on data
2023-11-03 15:38:59 +00:00
# Task Data
Task data is copied from task to task.
For example, consider the following sequence of tasks:
1. Start Event
2. Set Variable (sets variable a)
3. Read Variable (reads variable a)
In this scenario, if the "Set Variable" task sets the value of variable a to the number 1, the "Read Variable" task that follows can access that value (oh, cool, 1).
When the flow splits, as in a set of parallel branches, each branch gets a copy of the same data.
Then, when the data is merged back together at a merging gateway, if multiple branches write to the same variable, the last branch to complete will be the data that is propagated to tasks after the merging gateway.
Proof and ventilate all docs (#1822) * let us proof everything * proof and ventilate everything * restore removed content * add back in some headers * add back more headers * restore header * fix header * fix backend * restore two long files from main to avoid mangling * update edit_all for testing * fix docs * notes * more spacing --------- Co-authored-by: burnettk <burnettk@users.noreply.github.com>
2024-06-26 02:55:03 +00:00
Therefore, if you have tasks a, b, and c that run in parallel, it might not be a good idea for both a and b to set the "desired_withdrawal_amount" variable since, depending on how fast a and b run (and other implementation details around the parallel processing), the expected "winner" would not be knowable in advance.
update the docs on data
2023-11-03 15:38:59 +00:00
This general branching and merging strategy is applied to all parallel constructs, including inclusive gateways.