Siebel Business Process Framework: Workflow Guide > Architecture That Siebel Workflow Uses > About the Architecture of a Workflow Process >

Architecture You Use to Develop a Workflow Process

Figure 3 describes a typical approach to developing a workflow process.

Figure 3. Typical Approach to Developing a Workflow Process

Explanation of Callouts

You do the following to develop a workflow process:

1. Define. You use Siebel Tools to define the workflow process. You create an object definition for the workflow process, define the process properties, add steps and connectors, and so on. For more information, see About Siebel Tools.
2. Save. You frequently save the workflow process to the local database. This database includes repository tables. When you edit a workflow process in Siebel Tools, Siebel CRM stores it in the repository tables. When you deploy this workflow process, Siebel CRM adds it to the run-time tables.
3. Test. You use the Siebel client to test the workflow process. You use the Administration-Business Process screen in the client to administer workflow processes and workflow policies. For more information, see Process of Testing a Workflow.
4. Debug. You use Siebel Tools, the Siebel client, and the local master or test database to publish, activate, and debug the workflow process. You check out the workflow process from the repository into the local database, where you can modify and debug it locally before you check it into the master repository. To access server components, such as the Server Request Broker, you must debug and test with a server database or test database instead of debugging locally. You can optionally do the following in Siebel Tools:
   • Check the workflow process into and from your master database.
   • Export the workflow process to an XML file to back it up.
   • Import the workflow process from an XML file to restore it.
5. Verify. To verify that the workflow process works correctly, you can use the Siebel client to run it with the local master or test database.
6. Migrate. You migrate the workflow process from the master database to the staging database or production database. You can use Application Deployment Manager (ADM) to migrate workflow processes from one Siebel environment to another environment. For more information, see Migrating with Application Deployment Manager.

You can use the following types of files to import or export a workflow process:

• XML file. You can export a workflow process as an XML file.
• SIF File. You can export a workflow process as a sif (Siebel archive) file.

For more information, see Backing Up Workflow Processes.

About Siebel Tools

Siebel Tools is an integrated development environment (IDE) that you can use to develop and debug a workflow process. You use the Object List Editor to define the object definition of a workflow process. A workflow process references a project.

You use the Process Designer in Siebel Tools to develop a workflow process. You typically define process properties in the Process Designer but you can also enter configuration information through unbounded drop-down lists. Configuration data is available in the Process Designer but run-time data is not available.

You design and test the workflow process, and then save it to repository tables. Siebel Tools allows you to use a top down development framework to create business logic, beginning with creating a workflow process, and then providing plugable services and data objects that can run the workflow process.

For more information, see Using the Siebel Workflow Development Environment and Using Siebel Tools.