Using the Diagram Editor

Using SAS Workflow Studio's diagram editor, the business analyst can graphically design the relevant collection of tasks that comprise the workflow. Each workflow is a group of elements assembled using the following object model:

A task is a step or unit of work in the workflow. Tasks can be atomic nodes (tasks) or can contain collections of related nodes (local subflows). In the workflow tree, tasks are represented by a task icon (). The root workflow and its subflows are represented by a process icon ().

A task can be manual, or it can be automated by a script or a policy.

Data objects represent the business data values required to perform the workflow tasks. Data objects can mirror values retrieved from external data systems. In this way, SAS Workflow Studio is only loosely coupled with external data systems.

Data objects can be defined at the root workflow level or at the local task level. Data objects defined at the workflow level are global data objects. Global data objects can be accessed by all tasks and policies within the workflow.

Data objects defined at the task level are local data objects. They are accessible only for use by the parent task and its children.

Also, general workflow data and logic should be separated from actionable business data and logic. Workflows embody the abstract data and logic. Data objects embody the relevant portions of business data required to drive path execution and policies represent specific business actions.

A policy is a workflow element that associates event-driven logic with a task or subflow. Policies are usually triggered automatically by an event such as a status change or a timer event. A policy can reference workflow data to add, change, or update peer workflows at run time. These events occur when there is a change in the workflow. Events can be triggered in either of the following cases:

Policies support workflow automation in an extremely flexible manner. They are customizable using properties defined for each action.

A status is the outcome of a task. Status values are used to trigger state changes in tasks and subflows and to trigger the execution of policies. The status of a task is typically used to trigger the next task. Status values are part of the data that policies use to execute automated tasks. Status values have descriptive names such as Done, Cancel, and Accept to illustrate changes that occur in the workflow. Statuses link the workflow logic and solution logic because they represent transition states between tasks and other workflow elements.

A participant is a resource that performs the work represented by a workflow task instance. This work is typically manifested as one or more work items assigned to the workflow participant via the tasks in a workflow. (The tasks assigned to a participant are sometimes referred to as the participant’s worklist.) The list of solution users, groups, roles, or privileges (that is, platform identities) are mapped to standard roles in workflows as a participant. The participant is the actual mapping between the platform or solution user, group, role, or privilege (identity) and the workflow role. Participants drive task access and authorization by linking the workflow authorization roles to the SAS platform users, groups, organizational roles, and privileges.