@@ -1809,7 +1809,7 @@ definition "id" must be a constant value.
1809
1809
| dataInputSchema | Used to validate the workflow data input against a defined JSON Schema| string or object | no |
1810
1810
| [constants](#Workflow-Constants) | Workflow constants | string or object | no |
1811
1811
| [secrets](#Workflow-Secrets) | Workflow secrets | string or array | no |
1812
- | [start](#Start-Definition) | Workflow start definition | string | yes |
1812
+ | [start](#Start-Definition) | Workflow start definition | string | no |
1813
1813
| specVersion | Serverless Workflow specification release version | string | yes |
1814
1814
| expressionLang | Identifies the expression language used for workflow expressions. Default value is "jq" | string | no |
1815
1815
| [timeouts](#Workflow-Timeouts) | Defines the workflow default timeout settings | string or object | no |
@@ -1964,6 +1964,8 @@ If `object` type, it defines a JSON object which contains the constants definiti
1964
1964
For more information see the [Workflow Constants](#Workflow-Constants) section.
1965
1965
1966
1966
The `start` property defines the workflow starting information. For more information see the [start definition](#Start-Definition) section.
1967
+ This property is not required. If not defined, the workflow starting state has to be
1968
+ the very first state defined in the [workflow states array](#Workflow-States).
1967
1969
1968
1970
The `specVersion` property is used to set the Serverless Workflow specification release version
1969
1971
the workflow markup adheres to.
@@ -4524,6 +4526,9 @@ Event states define that workflow instances are triggered by the existence of th
4524
4526
Defining a cron-based scheduled starts for the runtime implementations would mean that there needs to be an event service that issues
4525
4527
the needed events at the defined times to trigger workflow instance creation.
4526
4528
4529
+ Defining a start definition is not required. If it's not defined, the starting workflow
4530
+ state has to be the very first state defined in the [workflow stated array](#Workflow-States).
4531
+
4527
4532
# #### Schedule Definition
4528
4533
4529
4534
` Schedule` definition can have two types, either `string` or `object`.
0 commit comments