Reusability of business logic is a key success factor for any software project, including Siebel CRM projects. The Sub Process step ensures that we can invoke often needed process flows from within another workflow process easily.

Subprocesses can not only help to increase the level of reusability but are also needed when more than one business object is involved in the process. As we have learned in the previous chapter, a workflow process can only be associated with one business object, which provides the context, and links, to the business component data.

If we need to operate on more than one business object, we must implement a subprocess. The Account - New Quote workflow process, associated with the Account business object, is a simple but very explanatory example of this. The following screenshot shows the Account - New Quote workflow process:

The Goto Quote View step is a Sub Process step. The main property of a Sub Process step is Subprocess Name, which is set to the name...