In SAS Visual Investigator, workflows are used to manage the investigation process. Workflows consist of a series of tasks that directly proceed to the next task in the sequence as each is completed.
For example, Acme Insurance might want a workflow such that, when an investigation is created, the workflow automatically starts and a new task for Investigators is created. Acme insurance can also configure the workflow so that the investigation is passed on to a manager or closed depending on what the investigator deems appropriate.
Workflows consist of five types of elements: events, gateways, notifications, services, and tasks. (these are grouped in the interface according to how they are used). Workflow templates are built by adding these elements to the workflow editor.
- There are two types of events: Start and End.
- A Start event must be the first element in the workflow. It is automatically added to the editor when a new workflow template is created. You can have only one Start event in each workflow.
- The End event is the last element in the workflow. When the workflow reaches the End event, the workflow terminates. Each workflow must have a Start event and an End event.
- Gateways enable the workflow to split. There are two types of gateways: parallel gateways and exclusive gateways.
- Parallel gateways enable the flow to take multiple paths and run concurrently.
- Exclusive gateways direct the process to only one path.
- The notification element can send an email to specified users or groups. The subject and body of the message can be configured, and either can contain a workflow variable. Entity links can also be inserted into the message text. When the workflow proceeds through the email notification element, the email is sent.
- Services provide a way to manipulate the workflow process behind the scenes, without any user completing a task. Two types of services can be included in workflow templates.
- REST services enable communication with external systems or other SAS Visual Investigator components using a URL. The URL is called, and the workflow is updated using this element. REST services can update workflow variables but not entity fields.
- Write services, in contrast, enable both workflow variables and entity fields to be updated. They are similar to user tasks in this regard but require no action to be taken by a user. They can be used to auto-update entities.
- There are two types of tasks: user tasks and script tasks.
- User tasks require direct action from a user in order to advance the process through the flow. Tasks can be specifically restricted by user type. For example, you might create an Approve Investigation task that is to be completed only by those with Manager status.
- Script tasks enable advanced scripting options to be used in the workflow. They can modify workflow variables and entities. You must be comfortable with JavaScript in order to use a script task.
- Lastly, sequence flows link workflow elements together. If a sequence flow is coming from an Exclusive Gateway node, then a condition property should be set so that the gateway can determine which path the flow should take.
The path a workflow takes is controlled by workflow variables. For example, an exclusive gateway uses the value of the variable to determine which path to take in the workflow. The two types of workflow variables are entity defined and user defined.
- Entity-defined variables are based on internal entity fields and take their initial values from those fields.
- User-defined variables are created in the workflow and are global variables available to the entire workflow.
Workflows are fully customizable and can be as simple or as complex as an organization needs.
Find more articles from SAS Global Enablement and Learning here.
