Bookshelf Home | Contents | Index | PDF |
Siebel Content Publishing Guide > Content Center > Setting Up Content Center Approval WorkflowsYou can use Siebel Business Process Designer to manage workflows for the content item approval process. When the Start Project or Request Start Project action is invoked on a content project, the approval workflows associated with each content item in the project are instantiated. Approval workflows allow you to specify the structure for contributing, reviewing, and approving content. The designated contributors and approvers are notified by new records in their Content Inbox at the appropriate step in the content production and approval process. For more information about designating contributors and approvers, see Setting Up Content Types. A state model and some workflows are associated with the approval workflow included in the seed data that is provided in Siebel applications. You can use these processes in your deployment, modify them to meet the needs of your business, or use them as a guide for creating your own approval workflows. For more information on creating or modifying workflows, see Siebel Business Process Designer Administration Guide. NOTE: All Content Center workflows should be placed into the Content Center group. About the Content Item State ModelA state model, called Content Item Status, controls the status changes of a content item. Table 5 describes each of the content item states. About the Content Approval (Single Approver) WorkflowThe Content Approval (Single Approver) workflow is a simple workflow that demonstrates a single approver approval process. You can use this workflow with or without modification. The Content Approval (Single Approver) workflow uses these step types to construct the business logic for content item approval:
You can use these workflow components to create new approval workflows or to modify the Content Approval (Single Approver) workflow for your business. For example, if you require two approval tasks, you can add two Content Task Subprocesses and State Decision Points. About the Content Task SubprocessThe Content Task Subprocess contains the common logic of assigning a content item and waiting for a user action. The parent approval process calls this subprocess each time a content item is assigned to an end user. Calling this task causes the content item to appear in the Content Inboxes for those users associated with the current sequence (TaskSeq). The parent business process must pass in the input arguments shown in Table 6. The Content Task Subprocess performs these actions:
About the Auto Complete WorkflowAn approval workflow must be run for each content item before a content project can be published. (See To start the project approval workflow.) To publish content without routing it through approvers and contributors, use the Auto Complete workflow. The Auto Complete workflow is a simple workflow, provided with the seed data. It sets the status of a content item to Completed immediately so that the project is ready for publication. |
Siebel Content Publishing Guide |