@@ -20,11 +20,11 @@ You can find the specification roadmap [here](roadmap/README.md).
20
20
- [ Project Components] ( #Project-Components )
21
21
- [ Specification Details] ( #Specification-Details )
22
22
- [ Core Concepts] ( #Core-Concepts )
23
+ - [ Workflow Definition] ( #Workflow-Definition )
23
24
- [ Workflow Model] ( #Workflow-Model )
24
25
- [ Workflow Data] ( #Workflow-Data )
25
26
- [ Workflow Functions] ( #Workflow-Functions )
26
27
- [ Workflow Expressions] ( #Workflow-Expressions )
27
- - [ Workflow Definition] ( #Workflow-Definition )
28
28
- [ Workflow Error Handling] ( #Workflow-Error-Handling )
29
29
- [ Defining Errors] ( #Defining-Errors )
30
30
- [ Defining Retries] ( #Defining-Retries )
@@ -107,8 +107,8 @@ This section describes some of the core Serverless Workflow concepts:
107
107
### Workflow Definition
108
108
109
109
A workflow definition is a single artefact written in the Serverless Workflow
110
- language. It consists of a set of [ workflow model ] ( #Workflow-Model ) constructs,
111
- and defines a blueprint used by runtimes for its execution.
110
+ language. It consists of the core [ Workflow Definition Structure ] ( #Workflow-Definition-Structure )
111
+ and the [ Workflow Model ] ( #Workflow-Model ) It defines a blueprint used by runtimes for its execution.
112
112
113
113
A business solution can be composed of any number of related workflow definitions.
114
114
Their relationships are explicitly modeled with the Serverless Workflow language (for example
@@ -1349,7 +1349,7 @@ We can now get back to our previously defined "IsAdultApplicant" expression func
1349
1349
As previously mentioned, expressions are evaluated against certain subsets of data. For example
1350
1350
the `parameters` param of the [functionRef definition](#FunctionRef-Definition) can evaluate expressions
1351
1351
only against the data that is available to the [action](#Action-Definition) it belongs to.
1352
- One thing to note here are the top-level [workflow definition](#Workflow-Definition) parameters. Expressions defined
1352
+ One thing to note here are the top-level [workflow definition](#Workflow-Definition-Structure ) parameters. Expressions defined
1353
1353
in them can only be evaluated against the initial [workflow data input](#Workflow-Data-Input).
1354
1354
1355
1355
For example let's say that we have a workflow data input of :
@@ -1374,7 +1374,7 @@ which would set the workflow version to "1.0.0".
1374
1374
Note that the workflow "id" property value is not allowed to use an expression. The workflow
1375
1375
definition "id" must be a constant value.
1376
1376
1377
- # ## Workflow Definition
1377
+ # ## Workflow Definition Structure
1378
1378
1379
1379
| Parameter | Description | Type | Required |
1380
1380
| --- | --- | --- | --- |
@@ -4843,7 +4843,7 @@ Metadata includes key/value pairs (string types). Both keys and values are compl
4843
4843
4844
4844
Metadata can be added to :
4845
4845
4846
- - [Core Workflow definition ](#Workflow-Definition)
4846
+ - [Workflow Definition ](#Workflow-Definition-Structure )
4847
4847
- [Function definitions](#Function-Definition)
4848
4848
- [Event definitions](#Event-Definition)
4849
4849
- [State definitions](#State-Definition)
0 commit comments