It is common for workflows to be focused around data. These non-user workflows are usually focused on tasks like:
It can often be difficult to know when there are problems when automating processes. For this reason, Decisions concentrates on fixing the relationships between processes and users in order to easily leverage our user tasking to help with this. Even in the middle of a data-oriented use case, a user can be involved to make decisions or intervene in some other way if something goes wrong or there is an unexpected condition.
Not only can a user (or groups of users) start a workflow, but they can also be engaged in the process as it is automated. A few ways to involve users in workflows could be assigning a form or engaging a user via email or telephone. If a workflow has an assignment for a user, it will pause and wait until the user completes the task.
Similar to waiting for a user interaction, a workflow can also wait for a system to interact. This waiting can be either passive (waiting for the system to make an API call to tell workflow it’s done/give needed data) or active (the workflow checking an external system, file, FTP site, email account, database). The assignment system is where both user-based and system-based ‘tasks’ can be reported on, managed, or even overridden.
Some workflows start with form interactions. This could be a form created using Workflow.com designers and published on a company intranet. These interactions can also occur on an external form in another application or on a website.
Workflows can be scheduled to start running on a given date, a computed date, or on defined intervals. You can also create a workflow to figure out when the start date should be.
Trigger events can be any number of things that happen in other systems, workflows, or monitored data sources.