Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Siebel Business Process Framework: Workflow Guide > Building a Workflow Process > Process of Building a Workflow Process > Defining a Workflow Process Object DefinitionThis task is a step in Process of Building a Workflow Process. The first part of building a workflow process is to define the top-level workflow process object definition. This topic describes several possible options. For more information about how objects discussed in this topic are represented in Tools, see About the Workflow Process Object Hierarchy. Reviewing Workflow ProcessesReview your existing workflow processes to see if the process you need is already available or if a similar process exists that you can copy and modify to meet your requirements. The Workflow Processes Object List Editor (OBLE) provides a list of the current process definitions. You can access the Workflow Processes OBLE in Siebel Tools. To review existing workflow process definitions
Copying a Workflow ProcessIf your intent is to create a different workflow, with a different name and a different purpose, then you can copy an existing workflow. The copied workflow does not replace the original workflow. In contrast to revising a workflow, when you copy a workflow, you create a new workflow process that is identical to the original one, except that a unique name, such as 04-K88GQ, is generated for it. The version of a new, copied workflow process is 0. When you revise a workflow process, however, the version is the next integer that is subsequent to the version number of the original workflow being revised.
Modifying a Workflow ProcessYou can modify an existing workflow process without restarting the Workflow Process Manager. A workflow process definition is refreshed in the process memory as soon as it is activated. When a new definition is deployed, the cache is refreshed, so a new instance picks up the newly deployed definition. To modify a workflow process, you must make it editable. For more information, see Making a Workflow Process Editable. About Workflow Process Definition Cache RefreshThe timing of when a workflow process definition is activated impacts the process cache:
For mobile clients and development clients, the server parameter called Workflow Version Checking Interval (VerCheckTime) controls how often the server component checks for new active versions of each workflow process definition. When a new workflow process definition is activated, an incoming workflow process instance created during the interval determined by Workflow Version Checking Interval uses the new definition. A workflow process instance initiated before the interval continues using the previous workflow process definition. Scenarios to consider include:
Reloading Run-Time EventsRefreshing the process definition cache is necessary but not sufficient for running the updated workflow process correctly. If the workflow process contains run-time events, the run-time event cache must also be refreshed:
Revising a Workflow ProcessTo revise a workflow you modify an existing workflow process definition. When you revise a workflow, the new workflow record created is the same as the original, with the same name, except that the workflow's version is incremented by one, the Status is In Progress rather than Completed, and the workflow is editable. The revised workflow replaces the original workflow.
If necessary, you can use the Expire button to set a workflow's status to Not In Use. For more information, see Expiring a Workflow Process Instance.
Defining a New Workflow ProcessIf you cannot locate an existing workflow process that meets your needs, you can define a new one. To view an example, see Creating a New Workflow Process Object Definition. Naming A Workflow ProcessWhen naming a workflow process, the combination of workflow process name and version must be unique. That is, you can have two workflow processes of the same name as long as their version numbers are different. Externalizing Workflow PropertiesWhen developing a workflow process, it is recommended you define properties for the workflow that are externalized and not hard coded. Having properties hard coded in a workflow means that you must change the definitions when the workflow is deployed between environments. For example, if a workflow is sending emails to a list of customers and the property is hard coded with the customer list, the workflow will not execute correctly in the production environment. You must make sure such input arguments are read dynamically. For an example of how to externalize properties used by a workflow process, see Example of Externalizing Properties Used by Siebel Workflow. Making a Workflow Process EditableThe background color in the workflow editor indicates whether the workflow process is editable:
When a workflow is editable, you can modify the workflow in a variety of ways, such as adding and removing steps and connectors, or changing step and connector properties. Several conditions must exist to make a workflow editable. Deleting a Workflow ProcessYou can delete a workflow process in the Object List Editor in Siebel Tools.
|
![]() |
![]() ![]() |
Siebel Business Process Framework: Workflow Guide | Copyright © 2008, Oracle. All rights reserved. | |