@@ -20,12 +20,15 @@ The JSON format defines the steps within the workflow by referencing the fully q
20
20
21
21
| Field | Description |
22
22
| ----------------------- | --------------------------- |
23
- | Id | Workflow Definition ID |
24
- | Version | Workflow Definition Version |
25
- | DataType | Fully qualified assembly class name of the custom data object |
26
- | Steps[ ] .Id | Step ID (required unique key for each step) |
27
- | Steps[ ] .StepStepType | Fully qualified assembly class name of the step |
28
- | Steps[ ] .NextStepId | Step ID of the next step after this one completes |
23
+ | Id | Workflow Definition ID |
24
+ | Version | Workflow Definition Version |
25
+ | DataType | Fully qualified assembly class name of the custom data object |
26
+ | Steps[ ] .Id | Step ID (required unique key for each step) |
27
+ | Steps[ ] .StepStepType | Fully qualified assembly class name of the step |
28
+ | Steps[ ] .NextStepId | Step ID of the next step after this one completes |
29
+ | Steps[ ] .Inputs | Optional Key/value pair of step inputs |
30
+ | Steps[ ] .Outputs | Optional Key/value pair of step outputs |
31
+ | Steps[ ] .CancelCondition | Optional cancel condition |
29
32
30
33
``` json
31
34
{
@@ -69,12 +72,12 @@ Full details of the capabilities of expression language can be found [here](htt
69
72
"StepType" : " MyApp.AddNumbers, MyApp" ,
70
73
"NextStepId" : " Bye" ,
71
74
"Inputs" : {
72
- "Value1" : " data.Value1" ,
73
- "Value2" : " data.Value2"
74
- },
75
+ "Value1" : " data.Value1" ,
76
+ "Value2" : " data.Value2"
77
+ },
75
78
"Outputs" : {
76
- "Answer" : " step.Result"
77
- }
79
+ "Answer" : " step.Result"
80
+ }
78
81
},
79
82
{
80
83
"Id" : " Bye" ,
0 commit comments