Posted by: Ashish Kumar | April 16, 2009

Siebel WorkFlow process : Asynchronous and synchronous mode


  Asynchronous Mode  Synchronous  Mode
1 User does not have to wait for process to complete. User have to wait for process to complete.
2 User gets back the control immediately and the workflow is submitted to workflow process manager (WPM) as a job to be executed. WPM then executes the job later. User gets control back only when the Work Flow finished its execution.
3 This is helpful in functionality where large amount of processing needs to be done on an object and user is not going to use the effect or access just after  
4 2 way to execute a workflow asynchronously .                      1.Workflow Policy
2. Runtime Event
Business Service (BS) Combination

5 WorkFlow can be invoked                   Run Process on the Server Administration – Server Management > Jobs                        • Run process using business service   Workflow Process Manager (Server Request) WorkFlow can be invoked       Run process in application object manager using business service BS “Workflow Process Manager” 
6 In case an error occurs while running the asynchronous process user will not get any error message and workflow will go in Exited state In case of error in Synchronous mode, error message is displayed to the user (unless it is explicitly suppressed through error handling)


  1. […]  Siebel WorkFlow process : Asynchronous and synchronous mode […]

  2. Hi, interesting post. I have been wondering about this issue,so thanks for sharing. I will probably be coming back to your posts. Keep up the good posts

  3. Hi, good post. I have been pondering this topic,so thanks for posting. I will certainly be coming back to your blog.

  4. Ugh, I liked! So clear and positively.

  5. Business Service Workflow Process Manager for Synchronous

    var svc = TheApplication().GetService(“Workflow Process Manager”);
    var Input = TheApplication().NewPropertySet();
    var Output = TheApplication().NewPropertySet();
    var rowId = this.BusComp().GetFieldValue(“Id”);
    Input.SetProperty(“ProcessName”, “———-“);
    Input.SetProperty(“Object Id”, rowId);
    svc.InvokeMethod(“RunProcess”, Input, Output);
    return (CancelOperation);

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: