cncf
/
wg-serverless
mirror of https://github.com/cncf/wg-serverless.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

adding description

This commit is contained in:
tsurdilo 2019-11-06 11:48:28 -05:00
parent aa13d8c2bb
commit 00af78f696
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
workflow/spec/spec.md
View File

@ -1071,10 +1071,10 @@ true, the branches parallel parent state must wait for this branch to finish bef
It is often the case that you want to group your workflows into small, **reusable** logical units that perform certain needed functionality.
Even tho you can use the Event state to call an externally deployed services (via function), at times
there is a need to include another serverless workflow (from classpath/local fily system etc). In that case you would use the Invoke State.
there is a need to include/nest another serverless workflow (from classpath/local fily system etc). In that case you would use the Invoke State.
It also allows users to model their workflows with reusability and logical grouping in mind.
This state allows you to call a uniquely identified workflow and start its execution.
This state allows you to include/nest a uniquely identified workflow and start its execution.
Another use of this state is within [branches](#parallel-state-branch) of the [Parallel State](#Parallel-State). Instead of having to define all states
in each branch, you could separate the branch states into individual local workflows and call the Invoke state
as a single state in each.