Component Workflows
Component Workflows are re-usable templates that can be used for these sub-processes. It is then a simple matter to drag and drop the component into the workflow template.
There are processes within your organization that need to be performed on a regular basis, or are fairly generic and can be used organization-wide. These ‘sub-processes’ are often included within other processes, such as purchase order requests, training requests, and updates to a human resource system.
Using Component Workflows offers considerable time savings, specifically:
no need to re-create the sub-process for each workflow template that uses it
updating the component also updates all the templates in which it exists.
Workflow components can be inserted into templates or into other components, but not directly in a request. The tasks in a component are automatically expanded in the request dependency diagram.
Creating a Component Workflow
Select Admin > Workflow Template.
The Workflow Template Administration window appears.
Select New. The Workflow Components dialog box appears.
Type a relevant name for the workflow component in the Workflow Template Name field.
Select OK. The Workflow Template <name> Details window appears. This window is similar to the Request Details window.
You can now specify information on all fields as you would in a request, such as link CMDB items, create tasks, set action dates for the tasks, create task dependencies, specify task assignment, set agreements for the requests and tasks created from this template, and finally specify request assignment. Your workflow template can be as detailed or as generic as you want it to be. You can even create a blank template for a workflow process. When you open a task in the dependency diagram on a template or a workflow component, the task opens in Review mode.
Any tasks you create for a workflow template will have an additional field on theTask Details window: Request Status on Completion, where you can update the request with the specified status once the current task is closed.
Some fields and features are not available from the workflow template details, such as the ability to perform asset management transactions.
Insert any further workflow components that you want to be part of this workflow component.
Although you can select extension fields defined through ASM Designer as an item for which to create a Condition or Action for a Conditional Branching Task within a Workflow Template, extension fields are not available for Conditional Branching Tasks within a Component Workflow because Component Workflows are not exclusively related to a given Workflow Template and its forms.
Save the component workflow.
Insert the component workflow into the workflow template(s) as required.
Inserting a Component Workflow into a Workflow Template
Workflow Components can be inserted into templates or into other components, but not directly in a request. The tasks in a component are automatically expanded when a request is created from the template.
Components can include any type of task from the palette, and can even include other components.
While a component does not have a Start Task like a request workflow, it does have in and out connectors. These connectors are linked into the workflow. There can be multiple connectors in and out of a workflow to accommodate multiple workflow branches, as demonstrated in the diagram below. Connectors are represented by a circle.
The contents of a component are only visible when editing the component directly, or once a request has been generated from a template in which it is contained. When viewing a component in a workflow template, it will be represented by a single icon with connectors.
Care should be taken when using Component Workflows as it is possible to create an infinite loop. For example, you cannot insert Component Workflow A into Component Workflow A (A into A); however, it is possible to insert A into B, and then insert B into A, thus creating a loop.
Last updated