Understanding a Business Process

Copyright © Cloud Software Group, Inc. All Rights Reserved

Chapter 1 Introduction : Understanding a Business Process

Understanding a Business Process

At the heart of the iProcess Workspace (Browser) is the iProcess “procedure,” which defines the flow of information in your application. Procedures are defined with a TIBCO tool called TIBCO Business Studio™. A procedure consists of a number of “steps,” including manual steps (which require user action), automatic steps (which are executed automatically by the iProcess Engine), and condition steps (which branch based on the result of a condition).

An example of a very simple procedure is shown below.

Someone using the iProcess Workspace (Browser) starts a “case” of a procedure, which typically causes a screen to be displayed onto which the user enters information. For example, if the procedure defines the processing of a loan application, the first screen may involve entering demographic information for the applicant. The next step might involve another person reviewing the application — the procedure would be defined such that the information entered in the first step is automatically sent to the person(s) responsible for reviewing it. The application process will progress through the steps of the procedure until it is completed.

The following table provides definitions of terms that are used throughout this document and in your iProcess Workspace (Browser).

Term

Description

Procedure

Represents the definition of a business process, which ensures that information flows in a consistent and timely manner through the system. An iProcess procedure is defined using TIBCO Business Studio. An example is shown in the illustration above.

Case

This is a particular instance of an iProcess procedure. A case is created when a procedure is “started,” and remains in existence until that instance of the procedure is purged from the system.

Step

A procedure is made up of a number of steps, which define the activities that take place within the flow of a procedure. Each step defines what must be done, who must do it, and, optionally, a deadline by which it must be done.

Work Queue

This is a list of work items (see below) that are awaiting action. A work queue can belong to an individual user (personal work queue) or to a group of users (group work queue). If it is a group work queue, any user that belongs to that group has access to the work items in that group queue.

Work Item

A work item represents an action item listed in a work queue. It relates to a step in an active case. A user manages the work items in their work queue by performing some sort of action upon them, such as entering data on a form, forwarding the item to another user or group, “keeping” it (placing it back in the work queue for further action at a later time), or “releasing” it (completing the required action and sending it on to the next step in the procedure).

You may not necessarily need to understand the entire structure of the procedure(s) you are working on. Generally, users are focused on performing some sort of work on the work items that appear in their work queue. The type of work you perform will depend on the type of business you are in and how your procedure was designed.

Term	Description
Procedure	Represents the definition of a business process, which ensures that information flows in a consistent and timely manner through the system. An iProcess procedure is defined using TIBCO Business Studio. An example is shown in the illustration above.
Case	This is a particular instance of an iProcess procedure. A case is created when a procedure is “started,” and remains in existence until that instance of the procedure is purged from the system.
Step	A procedure is made up of a number of steps, which define the activities that take place within the flow of a procedure. Each step defines what must be done, who must do it, and, optionally, a deadline by which it must be done.
Work Queue	This is a list of work items (see below) that are awaiting action. A work queue can belong to an individual user (personal work queue) or to a group of users (group work queue). If it is a group work queue, any user that belongs to that group has access to the work items in that group queue.
Work Item	A work item represents an action item listed in a work queue. It relates to a step in an active case. A user manages the work items in their work queue by performing some sort of action upon them, such as entering data on a form, forwarding the item to another user or group, “keeping” it (placing it back in the work queue for further action at a later time), or “releasing” it (completing the required action and sending it on to the next step in the procedure).