Processes

There are the following types of process in TIBCO Business Studio, the business process, the pageflow process and the service process.

  • A business process models actual and future processes in your organization that usually involve more than one person. Business processes are short or long-lived.
  • A pageflow process is a short-lived process (always executed in a single sitting) designed to implement a user interface dialog. It is always executed by one person (the person that initiates the process instance).
  • A business service is a set of actions that accomplishes some sort of business function. For example, a business service could be designed to handle an incoming insurance claim. It is used to start a business process (from a start message event) or trigger any incoming message activity from a pageflow process.
  • A case action process is a special type of business service, associated with a case class, that defines an action a user can perform that is related to a case. You can either create a new case action or generate one directly from a case class.
  • A service process is a stateless, non-persistant process that is not audited. Service processes should be of short duration and have a single function. For example, retrieving information from a database.

The Process Editor provides tools on a palette that use Business Process Modeling Notation (BPMN). By creating your process this way, you can fully prepare it for implementation by a specialist in your organization.

Some objects such as business assets can be shared at the project level. Others such as data fields and participants can be created at either the package level (where they can be shared amongst processes in that package), or at the individual process level (where they can only be used by that process).

Note: If the Participants folder is empty, it will be hidden by default. This is because the preferred usage is to define Participants at the Package level.