You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: specification.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3329,10 +3329,10 @@ This is to assure consistency and portability of the events format used.
3329
3329
The `name` property defines a single name of the event that is unique inside the workflow definition. This event name can be
3330
3330
then referenced within [function](#Function-Definition) and [state](#Workflow-States) definitions.
3331
3331
3332
-
The `source` property matches this event definition with the [source](https://github.com/cloudevents/spec/blob/master/spec.md#source-1)
3332
+
The `source` property matches this event definition with the [source](https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md#source-1)
3333
3333
property of the CloudEvent required attributes.
3334
3334
3335
-
The `type` property matches this event definition with the [type](https://github.com/cloudevents/spec/blob/master/spec.md#type) property of the CloudEvent required attributes.
3335
+
The `type` property matches this event definition with the [type](https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md#type) property of the CloudEvent required attributes.
3336
3336
3337
3337
The `kind` property defines this event as either `consumed` or `produced`. In terms of the workflow, this means it is either an event
3338
3338
that triggers workflow instance creation, or continuation of workflow instance execution (consumed), or an event
@@ -3345,7 +3345,7 @@ Otherwise, (i.e., when the `kind` property is set to `consumed`), the `source` p
3345
3345
Event correlation plays a big role in large event-driven applications. Correlating one or more events with a particular workflow instance
3346
3346
can be done by defining the event correlation rules within the `correlation` property.
3347
3347
This property is an array of [correlation](#Correlation-Definition) definitions.
3348
-
The CloudEvents specification allows users to add [Extension Context Attributes](https://github.com/cloudevents/spec/blob/master/spec.md#extension-context-attributes)
3348
+
The CloudEvents specification allows users to add [Extension Context Attributes](https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md#extension-context-attributes)
3349
3349
and the correlation definitions can use these attributes to define clear matching event correlation rules.
3350
3350
Extension context attributes are not part of the event payload, so they are serialized the same way as other standard required attributes.
3351
3351
This means that the event payload does not have to be inspected by implementations in order to read and evaluate the defined correlation rules.
@@ -3590,8 +3590,8 @@ correlation:
3590
3590
3591
3591
Used to define event correlation rules. Only usable for `consumed` event definitions.
3592
3592
3593
-
The `contextAttributeName` property defines the name of the CloudEvent [extension context attribute](https://github.com/cloudevents/spec/blob/master/spec.md#extension-context-attributes).
3594
-
The `contextAttributeValue` property defines the value of the defined the CloudEvent [extension context attribute](https://github.com/cloudevents/spec/blob/master/spec.md#extension-context-attributes).
3593
+
The `contextAttributeName` property defines the name of the CloudEvent [extension context attribute](https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md#extension-context-attributes).
3594
+
The `contextAttributeValue` property defines the value of the defined the CloudEvent [extension context attribute](https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md#extension-context-attributes).
3595
3595
3596
3596
##### OnEvents Definition
3597
3597
@@ -3948,7 +3948,7 @@ References a `produced` and `consumed` [event definitions](#Event-Definition) vi
3948
3948
The `data` property can have two types: string or object. If it is of string type, it is an expression that can select parts of state data
3949
3949
to be used as payload of the event referenced by `produceEventRef`. If it is of object type, you can define a custom object to be the event payload.
3950
3950
3951
-
The `contextAttributes` property allows you to add one or more [extension context attributes](https://github.com/cloudevents/spec/blob/master/spec.md#extension-context-attributes)
3951
+
The `contextAttributes` property allows you to add one or more [extension context attributes](https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md#extension-context-attributes)
3952
3952
to the trigger/produced event.
3953
3953
3954
3954
The `consumeEventTimeout` property defines the maximum amount of time (ISO 8601 format) to wait for the result event. If not defined it should default to the [actionExecutionTimeout](#Workflow-Timeout-Definition).
@@ -4878,7 +4878,7 @@ one of the defined `produced` events in the [events](#Event-Definition) definiti
4878
4878
The `data` property can have two types, object or string. If of string type, it is an expression that can select parts of state data
4879
4879
to be used as the event payload. If of object type, you can define a custom object to be the event payload.
4880
4880
4881
-
The `contextAttributes` property allows you to add one or more [extension context attributes](https://github.com/cloudevents/spec/blob/master/spec.md#extension-context-attributes)
4881
+
The `contextAttributes` property allows you to add one or more [extension context attributes](https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md#extension-context-attributes)
4882
4882
to the generated event.
4883
4883
4884
4884
Being able to produce events when workflow execution completes or during state transition
0 commit comments