Administer > Workflows

Workflows

A business processA set of activities that performs a specific task. is a set of activities that performs a specific task. A workflowA business process that can be triggered by a user action, a time-based event, or another business process. is a type of business process, typically structured in HEAT to handle support tickets and escalations that can be long running. Workflows can be triggered by a user action, a time-based event, or another business process.

A workflow executes in parallel to the client user interface and interacts with the HEAT Application Server and the database. It can include timing-based logic, function along logical if-then paths, occur on the server independent of the activities of a client or user, and can create or update records behind the scene.

A workflow process is created (a copy of the workflow design) for a record (incident, change, etc.) with an event (trigger) that satisfies the conditions of that workflow. These events are added to a queue and are processed in a first-in-first-out basis by the Workflow EngineExecutes the activities created within the Workflow Designer.. There is no preset time limit on how long a workflow can take to run and finish.

By default, HEAT comes with a variety of workflows, but you can create your own to service your organization. The default business objects that use workflows are change, release, release milestones, problems, knowledge, and service requests.

A workflow can take up to 20 minutes to be instantiated and start executing the blocks after the events are queued. Do not expect immediate (real time) response when triggering a workflow.