Public workflows

So far, all discussed workflow executions have been handled within a single workspace. So a user has deployed a workflow to their own workspace and then called it from the username that matches the workspace in which the workflow was deployed. However, the WR also supports public workflows. These are specified by the owning users who deploy a workflow to their own workspace and also provide a configuration for that workflow specifying any/all of the following:

• A workflow is available to all Hub users (public)
• A subset of users who can call this workflow
• (In future) A workflow as a User-service
• (In future) A subset of user groups who can call this workflow

If no workflow configuration is provided the workflow defaults to public and it can only be run by the someone logged into the deploying workspace.

In order to call a public workflow, you can simply use the execution endpoint that includes the owning (deploying) workspace but ensure you are logged into your Hub account. If the specified workflow is public or the logged in username is specified in the list of allowed users, then the workflow is executed within the calling user’s workspace, just as before. Workflow logs and outputs will be available to the calling user, as if it was their own workflow. The deploying user simply provides the workflow, no further knowledge of the execution is available to them.