Bookshelf v7.5: Creating a Subprocess Diagram

Siebel Business Process Implementation Guide > Siebel Business Process Components and Categories > Building Your Own Business Process Diagrams >

Creating a Subprocess Diagram

In designing subprocesses, it is important to show how the Siebel application will interact with other systems. For example, Siebel Systems has recently introduced the Universal Application Network to deliver integration between Siebel applications and third-party applications using an integration server. Integration can be point-to-point, with a line in a diagram directly connecting a Siebel application step to a third-party application. Integration can also be achieved through an integration application process, represented by an IAP symbol as shown in Table 3.

To create a subprocess diagram

For every subprocess symbol used in the business process diagrams you build, create a subprocess diagram.

Complete the subprocess diagram in the same manner as the business process diagram, as described in To create a business process diagram.

NOTE: As you create the necessary swimlanes for each role, it is helpful to remember that in subprocesses, the roles are typically systems or individuals rather than organizational groups. However, do not use a separate swimlane to represent the Siebel application. Instead, use the Siebel View icon to represent that the Siebel application is supported in a particular step, performed by the user for the particular swimlane's role. You can input the view name by double-clicking on the symbol. On the General tab of the Properties dialog box, enter the view name in the Name field.

Make sure to represent the Integration Application Processes (IAPs) that are supported through Siebel UAN.

Represent the IAPs by adding an Integration Server swimlane and third-party application swimlane at the bottom of the diagram.

Create a vertical arrow extending down from a step within the other swimlanes. The line should connect to an IAP symbol within the Integration Server swimlane and then extend to the third-party system symbol placed in the third-party system swimlane. The line that extends from the IAP to the third-party system should be dashed to indicate that the step takes place outside the company.

If there is a synchronous response from the third-party application, indicate this by drawing a return-arrow line that moves back into the Siebel application through the same IAP symbol. If there is an asynchronous response, indicate the delay by showing the arrow returning to the Siebel application through a different IAP symbol.