Workspaces Tab

The Workspaces tab limits a webhook configuration to parts of the Asset, Document and Data Object trees.

Workspace with included folders for Documents, Assets and Data Objects

Defining a Workspace

Use the Add button of the element type to add an entry, then set its Path by dragging a folder from the element tree onto the entry. Enable include to include that path, or clear it to exclude the path.

An entry covers the path and everything below it.

warning

The prefix is matched as a plain string, not on folder boundaries. An entry for /Product Data therefore also matches a sibling folder whose name starts with the same text, such as /Product Data Archive. Keep that in mind when naming folders next to a configured workspace path.

How a Path Is Matched

Leaving the tab empty is the simplest case: every element is in scope, and every matching event dispatches a request.

As soon as one entry exists for an element type, matching works like this:

1. An entry whose path equals the element's path wins outright, and its include value decides.
2. Otherwise the deepest entry whose path is a prefix of the element's path decides.
3. An element matched by no entry at all is excluded.

Rule 3 is the one to keep in mind: once you configure any workspace entry for an element type, everything outside the configured paths stops triggering the webhook.

Nesting an excluded path inside an included one therefore works as expected. Given these entries:

Path	include
/Product Data	yes
/Product Data/Internal	no

objects under /Product Data trigger the webhook, except those under /Product Data/Internal, because the deeper entry wins.

Each element type is matched against its own list. Configuring paths for Objects leaves Assets and Documents unrestricted.

note

Workspaces do not apply to the workflow events. workflow.entered and workflow.completed are matched by workflow name only, so this tab has no effect on them.