Bookshelf Home | Contents | Index | PDF |
Siebel Business Process Framework: Workflow Guide > Options for Configuring a Workflow Process > Configuring Events > Configuring Run-Time EventsA workflow process can use run-time events to do the following: A workflow process can use the following types of events: A run-time event allows Siebel CRM to reply in real time to a user interaction. To start or resume a workflow process, you can define a run-time event on a connector that emanates from a start step, wait step, or user interact step. To define a run-time event, you can use the following properties of the WF Step Branch: For more information, see Starting a Workflow Process, and Siebel Personalization Administration Guide. Using Run-Time Events with a Long-Running Workflow ProcessIt is recommended that you do not configure Siebel CRM to use a run-time event to start a long-running workflow process because a run-time event is specifically related to a single user and a single session. It originates from Personalization functionality. Instead, it is recommended that you use an interactive workflow process or a service workflow process to handle a run-time event. After this workflow process finishes, Siebel CRM can create a user event that notifies a long-running workflow process. Using Run-Time Events with a User Interact StepIf the Immediate Post Changes property of a business component field is TRUE, then Siebel CRM supports using the SetFieldValue event with a user interact step. If the field value changes, and if Immediate Post Changes is TRUE, then Siebel CRM does an immediate roundtrip to the Siebel Server, and then immediately recalculates the field or refreshes the view. It bypasses the PreSetFieldValue event in the browser script. Siebel CRM does not support the following events with a user interact step:
For more information, see Configuring Siebel Business Applications. Using Run-Time Events in a Business Object ContextSiebel CRM starts a workflow process that references a run-time event only if it detects the run-time event in the same business object context that the workflow process references. For example, assume the WriteRecord event starts a workflow process, and that the Business Object property for this workflow process is set to Service Request. To update the record, the user clicks the Service Requests List screen tab, updates the Status field, and then steps off the record. Siebel CRM writes the record in the context of the Service Request business object, and then starts the run-time event that is defined on the workflow process. If the user updates the Status field in a context other than the service request business object context, then Siebel CRM does not start the run-time event. For example, assume the user drills down on a Contact, clicks the Service Requests view tab, updates the Status field, and then steps off the record. In this situation, Siebel CRM writes the service request record in the context of the Contact business object and it does not start the run-time event. Defining a Run-Time Event in a Many-to-One RelationshipThe example in this topic defines a run-time event in a many-to-one relationship. If you define a run-time event to start a workflow process in reply to a change that a user makes in a record that contains a many-to-one relationship with a parent, then you must configure Siebel CRM to start the workflow process according to the child ROW_ID. For example, assume you require Siebel CRM to start a workflow process if the user updates a field in the activity of a service request. A service request can contain one or many activities, so Siebel CRM must start the workflow process according to the activity ROW_ID and not according to the service request. If you start the workflow process according to the service request ROW_ID, then the following occurs:
To define a run-time event in a many-to-one relationship
Using a Run-Time Event with the Updated By FieldIf a workflow process step includes a run-time event that uses a processing mode that runs locally to start or resume a workflow process, then the value in the Updated By field identifies the user who is currently logged into Siebel CRM. Run-Time Events That You Cannot Use to Start a Workflow ProcessTo start a workflow process, Siebel CRM cannot use a run-time event that might not return a result. It can start a workflow process only in the record context of a business component. If business component record context does not exist, then Siebel CRM cannot start the workflow process and attempting to use the BusComp Query event to start it will fail. Using a Run-Time Event More Than One TimeYou cannot use the same run-time event more than one time in a given workflow process. |
Siebel Business Process Framework: Workflow Guide | Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |