Siebel Business Process Implementation Guide > Siebel Business Process Components and Categories > Business Process Component Descriptions >

Subprocess Diagram


A subprocess is a repeatable component of a business process. A subprocess diagram shows a greater level of detail for one step than is shown within a business process diagram. A subprocess diagram depicts the detailed steps performed by one role or multiple roles within a department, such as a sales representative and a sales manager. Figure 16 provides an example of a subprocess diagram.

Figure 18.  Sample Subprocess Diagram: Check Order Status

Click for full size image

Symbols Used in Subprocess Diagrams

Table 2 shows symbols used in both business process diagrams and subprocess diagrams. The symbols described in Table 3 are used exclusively in the subprocess diagrams.

Table 3.  Symbols Used in Siebel Subprocess Diagrams
Symbol
Description
Click for full size image
Integration Application Process
An Integration Application Process (IAP) symbol shows the interaction between Siebel applications and a third-party application delivered through UAN. An integration is represented with two arrows, one going into the symbol and the other going out, indicating a request for information and a reply with the information requested.
Click for full size image
Third-Party System
A third-party system database symbol indicates a step performed by a system outside of Siebel applications. The integration between these applications may or may not be available through UAN. If the third-party system is connected directly to a Siebel-supported step (indicated by a Siebel View icon and a blue-bordered box) without first connecting to an IAP symbol, then UAN does not support this integration. If the third-party system is connected through an IAP symbol, UAN supports this integration.

Representing Integration in Subprocess Diagrams

While Integration Application Processes are recommended integration solutions, IAPs are not the only way to integrate to Siebel applications, nor does Siebel Systems provide IAPs for every integration scenario. In some cases, a direct integration (also known as a point-to-point integration) makes more sense than integration using an IAP. For example, when another application such as a tax calculation utility simply acts on or supplements data in the Siebel application, a direct integration should be used rather than an IAP. In the subprocess diagrams, these direct integrations are shown as Siebel-supported steps that connect directly to a third-party data source.


 Siebel Business Process Implementation Guide 
 Published: 18 April 2003