In this article:
Client Workflows - Introduction to client workflows
Server Workflows - Introduction to server workflows
Business Workflows - Introduction to business workflows
Overview
The Adaptiva workflow engine supports three types of workflows; client, server and business.
Different workflow types perform different functions and can be utilized in different places throughout the workbench. It is important to select the correct type of workflow for the correct usage. This article highlights the usage of each of the three types of workflow.
Client Workflows
Client workflows are executed by the Adaptiva client. These workflows can execute on any device (Server, Desktop, Workstation, Laptop, Tablet etc.) that is running the Adaptiva Client. They can also execute on the Adaptiva Server and it is the Adaptiva Client component running on the server that will perform the execution of these workflows.
Server Workflows
Server workflows run only on the Adaptiva Server. These workflows are primarily used for running background or event-driven tasks. These are non-interactive and can be set to run on receipt of a specific message, upon a specific event triggering or as part of a server policy for actions such as Content Push.
The most common use case for server workflows is for Peer-to-Peer PXE approval workflows. Server workflows can be assigned as a PXE approval workflow to perform additional tasks upon receipt of a PXE request. These tasks could include looking up the PXE-booted device in a configuration database, overriding the boot image ID sent back from the server to the RVP, logging the PXE boot request in a database table or file etc.
Server workflows cannot be launched directly from the workbench, and they do not support forms or scheduling. Where these components are desired, a business workflow should be used instead.
Business Workflows
Like server workflows, business workflow also run only on the Adaptiva Server. Business workflows however, are used primarily for execution of on-demand or user-interactive workflows.
Business workflows support launch forms so that user-data can be provided at runtime. This allows for workflows that perform dynamic tasks where the input is different each time and is to be input by the person running the workflow.
In addition to being able to run business workflows on-demand, they can also be scheduled via the workflow management perspective. Business workflows can be set to run on any desired schedule which is particularly useful for automation tasks, housekeeping, server-based orchestration and general routine tasks.