Siebel Business Process Framework: Task UI Guide > Configuring Task UI > Editing Task Flows >

Configuring Task Event Handlers


The configuration of event handlers for Task UI employs the use of two object types: Task Event and Task Event IO Argument. The process of defining task event handlers is described in the following topics:

Event Handlers cannot be associated with subtasks. Therefore, you cannot add Task Event objects to a Task object if the Is Subtask property of the Task object is set to TRUE.

For a description of the Task Event and Task Event IO Argument objects and their properties, see the Siebel Object Types Reference.

Defining Task Event Handlers

The Task Event object (a child of the Task object) defines event handlers for certain Task UI events (such as Cancel, Delete, Pause, and Resume). This is where you specify the actions to take when such events occur.

To define a task event handler

  1. In the Object Explorer (in Siebel Tools), click the Task object type.
  2. In the Tasks OBLE, select the task that you want to define an event handler for.
  3. In the Object Explorer, click the Task Event object type.
  4. Right-click the Task Events OBLE, and choose New Record from the pop-up menu.
  5. Select a Name for the event handler.

    The drop-down list allows you to select from the available types of events to handle (Delete, Pause, Pre-Cancel or Resume). This is the name for the event handler.

  6. Specify the type of event handler using one of the following sets of properties:
    • Workflow Process. To use a Workflow process to handle the event, select the name of the workflow process for the Workflow Process property.

      NOTE:  If you select Workflow Process to handle the event, you can not define input and output arguments. However, you can run the Workflow process as a business service handler. To do this, select Workflow Process Manager for the Business Service Name property and RunProcess for the Business Service Method property.

    • Business Service. To use a business service to handle the event, select the Business Service Name and Business Service Method to handle the event.

      NOTE:  If the Workflow Process property contains a value, the Business Service Name and Business Service Method properties are ignored. The specified workflow process is the event handler.

  7. (Optional) You can now provide input and output arguments for the event handler (see Defining Task Event IO Arguments).

Defining Task Event IO Arguments

The Task Event IO Argument object (a child of the Task Event object) defines the input and output arguments to the event handlers.

NOTE:  If you have entered a Workflow process name in the parent task event object, you can not define input and output arguments. However, you can run the Workflow process as a business service handler. For details, see the procedure for Defining Task Event Handlers.

When the Input/Output property is set to Input, an input argument name of the event handler, whichever type being configured in the parent Task Event object, should be entered into the Argument property. When the Input/Output flag is set to Output, an output argument name of the event handler should be entered into the Argument property.

To define an input argument for a business service method

  1. In the Object Explorer (in Siebel Tools), click the Task object type.
  2. In the Tasks OBLE, select the appropriate task.
  3. In the Object Explorer, click the Task Event object type, and select the appropriate task event in the Task Events OBLE.
  4. In the Object Explorer, click the Task Event IO Argument object type.
  5. Right-click the Task Event IO Arguments OBLE, and choose New Record from the pop-up menu.
  6. Select Input from the drop-down list for the Input/Output property.

    NOTE:  Leave the Name property blank for now, it is a system-defined property.

  7. For the Argument property, select the name of an argument.

    The picklist shows the input arguments available for the business service method specified in the parent Task object. After you select an Argument, the Name property is populated.

  8. For the Type property, select a source type (Business Component, Expression, Literal, or Task Property). This is the source of the value for your input argument.
  9. Specify the remaining properties, based on the Type selected in the previous step. Fields not applicable to the destination type are disabled:
    • Business Component. When the source Type is set to Business Component, you can select a business component and one of its fields in the Business Component and Business Component Field properties.
    • Expression. When the source Type is set to Expression, the Value property is used to specify an expression, which is evaluated at run time to determine the input argument value.
    • Literal. When the source Type is set to Literal, the Value property of the input argument is used to specify a literal value for the input argument.
    • Task Property. When the source Type is set to Task Property, you can select a task property in the Property Name property.

To define an output argument for a business service method

  1. In the Object Explorer (in Siebel Tools), click the Task object type.
  2. In the Tasks OBLE, select the appropriate task.
  3. In the Object Explorer, click the Task Event object type, and select the appropriate task event in the Task Events OBLE.
  4. In the Object Explorer, click the Task Event IO Argument object type.
  5. Right-click the Task Event IO Arguments OBLE, and choose New Record from the pop-up menu.
  6. Select Output from the drop-down list for the Input/Output property.

    NOTE:  Leave the Name property blank for now, it is a system-defined property.

  7. For the Type property, select a destination type (Business Component, Expression, Literal, or Output Argument). This is the type of destination for the value of your output argument.
  8. Specify the remaining properties, based on the Type selected in the previous step. Fields not applicable to the source type are disabled.
    • Business Component. When the output argument Type is set to Business Component, you can select a business component and one of its fields in the Business Component and Business Component Field properties.
    • Expression. When the output argument Type is set to Expression, the Value property is used to specify an expression, which is evaluated at run time to determine the output argument value.
    • Literal. When the output argument Type is set to Literal, the Value property of the output argument is used to specify a literal value for the output argument.
    • Output Argument. When the output argument Type is set to Output Argument, you can select a task property in the Argument property. The picklist shows the output arguments available for the business service method specified in the parent task object.
  9. For the Property Name property, select the name of a task property.

    This is the destination of your output argument. For example, if you want to populate the value of the output argument into the Object Id task property, then select Object Id.

Siebel Business Process Framework: Task UI Guide Copyright © 2006, Oracle. All rights reserved.