Build Your Workflow

Create a Workflow

ASM ships with a predefined Change Workflow. All you need to do is update it to reflect the settings you need (Status, assignments, etc) to support your specific Change Process. You can find out more about workflows here.

A workflow is the logic you build to support some level of automation of a request. The request then, is merely the container. It houses all the details of what the user is asking you for; a Change, some software or hardware, or something else they may want or need. The real powerhouse is the workflow itself. In the workflow are all the tasks, AKA "Work Items" or "Ticket", that form the body of work required to fulfill the request. Because of this, you don't actually action or work a request, rather you work the tasks that it contains. Some tasks may be automated, and some might be manual. There are 17 task types available for you to use.

The task options are displayed in the task palette at the top of the diagram when you are in Action mode. Configuring the tasks is easy and intuitive.

Best Practice: Carefully consider the number of email messages you send during a given workflow

Many tasks contain fields that only display whilst in the workflow template. Alemba recommends you do not hide these fields because you will need to configure them in the template. For example, Request Status on Completion is only visible when working with the task in the Workflow template.

Available Task types

Last updated