Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -30,9 +30,14 @@ To define a workflow trigger the following information is needed:

## Integration

Once a trigger resources is defined, it can be attached to a Node Shape by using a special-purpose non-validating Property Shape resources.
Such property shapes use a `shui:provideWorkflowTrigger` statement to define, which workflow trigger are to be represented.
SHACL path statements on such Property Shape resources are meaningless and ignored, but may be provided.
A `shui:WidgetIntegration` shape element needs to be created from the previously defined workflow trigger.

![](create_new_widget_integration.png)


Once the widget is created, it can be attached to a Node Shape by using a special-purpose non-validating [Widget property](../node-shapes#widgets).

![](adding_widget_to_node.png)

## Payload Structure

Expand All @@ -44,9 +49,11 @@ Workflow Payload
``` json
{
"graphIRI": "http://example.org/example-graph",
"resourceIRI": "http://example.org/example-graph/examle-resource"
"resourceIRI": "http://example.org/example-graph/example-resource"
}
```

- `graphIRI` is the IRI of the graph that is currently viewed, and
- `resourceIRI`is the IRI of the resource that is viewed.

To make use of this dynamic payload, the underlying workflow should define variable input using [Replaceable Datasets](../../../../build/workflows#replaceable-datasets).
Loading