Workflow Types

Home >> Siebel Tools >> Workflow Process >>
About Workflow Process WF/Task Editor Toolbar Workflow Properties Workflow Process Properties Workflow Designer Window Property Window Multi Value Property Window Workflow Step

Workflow Types in Siebel CRM...
  • Workflow type/mode is a mandatory property in creating a new Workflow process
  • Workflow execution/run time will change depending on the functionality which the workflow delivers
  • We can determine the type of a workflow by analyzing run-time behavior of the workflow process
  • Types are
    1. Service Flow
    2. Interactive Flow
    3. Long-Running Flow
    4. 7.0 Flow


1. About the Service Workflow Process

  • from Siebel version 8.1, Service Flow is the default Workflow Mode for newly created workflows
  • service flow workflow includes no special behavior
  • executes a set of operations to complete a unit of work from start to end step in a short amount of time
  • service flow workflow doesn't stop or pause the execution in-between for an event or activity
  • means, whenever a user executes service workflow, then the control has been taken from user and returned back only if the workflow completes the process or terminates by an unhandled exception
  • hence we can say the limitations of service flow workflows are not pause for a run-time event or pause for time and not include a user interact step
  • we can call this service flow workflow as subprocess from another service workflow / interactive workflow / long-running workflow (but not from 7.0 workflow)
for example...
Let us consider a workflow has three steps namely Start > Create Entity > Stop, takes all the required values in the input parameter and creates an entity for an account. Here, the workflow having a particular task as create an entity under an account and not required to execute for long time as well as not required to interact with user in-between the workflow. So these execution behavior workflows are identified as Service Flow Workflows


2. About the Interactive Workflow Process

  • assists and controls navigation for a user across Siebel views and screens
  • includes one or more user interaction steps and typically includes a run-time event
  • since it holds inteact steps, this type workflows are run only in a user session context and cannot be executed in the Workflow Process Manager server component
  • run workflow in a user session context means the workflow process must run in an Application like Siebel Call Center / Siebel Service / Siebel eChannel, that contains a user session
for example...
Let us consider a scenario that a user logged in to Siebel eChannel applicatoin and tries to assign/re-assign/cancel a service request and that leads to navigate to different views on the basis of user input. In such scenarios, Interactive Flow workflow provides access to interact with user and supports to navigate a view, whenever user clicks assign/re-assign/cancel buttons


3. About the Long-Running Workflow Process

  • is a type of workflow process that is persistent and can run for hours, days, or months
  • we can use a long running workflow process that handles an entire business process transaction to coordinate between multiple subprocesses
  • it is not allowed to add interact step inside long-running workflow processes, but we can use an interactive workflow process as a sub process step
  • we must use a user event and not a run-time even to start or resume the long-running workflow process
for example...
Let us consider a scenario that requires to interact with external system and needs to wait for reply from that system, and this process may take an hour or a day, in such scenarios, Long-Running workflows are used to implement this functionality in Siebel CRM


4. About the 7.0 Workflow Process

  • provides backward compatibility for an existing workflow process that was defined in Siebel CRM version 7.7 or earlier
  • while upgarding Siebel CRM version from older to version 7.7 or higher then the existing workflow's Workflow Mode value has been automatically updated as 7.0 Flow
  • while upgrading from pre 7.7 version to 8.0 version, it is storngly recommended to upgrade pre 7.7 workflow processes to version 7.7 and proceed to upgrade version 8.0
  • it is strongly recommended that we should not use the 7.0 Flow workflow mode in newly created workflows

at

Comments

Post a Comment