Introduction to Processes

Introduction to Processes

While normal functions are single user functions, processes are functions typically spanning multiple users, where an event created by one user, generates a work item to another.

Processes are designed in Comflow Studio. Interaction with, and monitoring of, the running processes are done via the browser runtime GUI.

The sequence flow of a process can be decided by information content, non events and other business logic.

Modeled processes are, when put in a running state, ready to be triggered by a user, timer or application event. Such a trigger event will create a new instance of the process. It is important to understand the distinction of a process definition (a modeled process) on global level and the numerous process instances that are created from that definition.

A process instance exchanges information between users (assigned to roles) and, possibly, external systems in a synchronous or asynchronous way. Asynchronous process/user information exchange is done via notifications. Synchronous process/user information exchange is done via work items. The information routing can be fully content based.

When an end user (assigned to a specific role), synchronously or asynchronously, interacts with a running process he or she, typically, does so using the tasks in the My Work folder (see chapter 3) in the runtime GUI.

Process administration includes starting, stopping and monitoring processes. An administrator also has the possibility to reassign users to specific work items, study process statistics etc.

A brief description of what a process can look like will follow below:

Figure 44 provides an example of a simple item registration process modeled in Comflow developer studio:

Figure 44 Process model example

The process is instantiated by a user, acting in the role as ItemResponsible, registers an item. This event will trigger an electronic process instance of the modeled and deployed process.

Two work items, “Add Purchase Info” and “Add Quality Info”, will be sent to two different roles. The “content of the work items are in this example to add purchase- and quality information to the item that was previously registered.

The work items will end up in a work list of the users assigned to the PurchaseResp- and QualityResp roles. If no role/user assignment have been done the work items will end up in a common claim “inbox” in the work list for all users that possibly can act in the different roles.

When the work items has been sent the process will be in a “wait for event” state, waiting for the add purchase info and add quality info events to occur. When those events has occurred the process instance will send an “Approve” work item to the ItemResponsible role, wait for that event to occur and then end.

This manual deals with processes in runtime, both the administration of the process instances created from the defined process, but also how to work with work lists as mentioned above.

Note that this is a very simplified process example. Typically a process like this handles a lot of other things like non-event handling, content based routing, external application information exchange etc. This said, the simplified process does provide an example of a Business Process Management solution.

A process model, and its running counterpart, that fully explores the possibilities of Business Process Management provide a number of fantastic benefits for any organization:

The people that really know the business processes are the ones that define the process model and the blueprint is handed over to the IT department. This effectively bridges the gap between business and IT.

The electronic process instance owns and drives the process, handling non events and making sure that nothing falls between chairs.

Minimizes manual work (automates as far as possible)

Flexibility! In today’s world it is very important for a company to be able to react and change rapidly to new market demands. Electronic business processes that are modeled and running in Comflow are easy to change to fit the new needs.

The modeling of the business processes will result in scrutinizing the existing processes and getting a visualized image and easy understanding of the “new” ones.

Business logic is to a great extent visualized in the model and no longer hidden in a “black box” layer.

Reusability. Whole or part of already modeled business processes can be reused for other similar processes or in other branches of a company.

All these benefits and more can be utilized when running processes on Comflow!