Actions that you can take on flow definitions
You can take the following actions on flow definitions: publish, unpublish, disable or enable event triggers, submit and remove flows.
| Action | Description |
|---|---|
| Publish | Shares a flow definition with other users. When a flow definition is published, other users can link the flow definition as a subflow in other flows and submit the flow definition to run as a flow. |
| Unpublish | Removes sharing of the flow definition to other users. The flow definition can no longer be linked by reference as a subflow in other flows. Only the user who created the flow definition can view the flow definition and submit it to run as a flow. |
| Disable Event Triggers | Prevents Process Manager from running a flow, even though the flow definition has been committed. If the flow definition contains any events that cause work items in the flow to run automatically (for example, calendar event, file event) work items in the flow will not be submitted until the flow definition is released or the events are manually triggered. |
| Enable Event Triggers | Requests that Process Manager again manage a flow definition: to release a flow definition that is on hold, with disabled event triggers. |
| Submit | The act of initiating the running of a flow. When a flow definition is submitted, a flow is created. |
| Remove | The act of removing a flow definition from the system. After a flow definition is removed, Process Manager no longer knows about it and cannot schedule any new occurrences of the flow. |