Siebel Personalization Administration Guide > Run-time Events > About Creating Action Sets >

Creating Actions


You define actions to be triggered when an event occurs. Actions can modify content or user profile attributes, which in turn can modify the content displayed to the user.

Actions are created in the Action Sets view under Runtime Events Administration.

NOTE:  After modifying personalization actions, you must refresh the object manager for the actions to take effect immediately. See Clearing and Reloading Siebel Personalization.

To create actions for an action set

  1. Navigate to Site Map > Runtime Events Administration > Action Sets.
  2. Select the action set for which you are creating actions.
  3. Add a new record to the Actions list below the Action Sets list.
  4. The Actions form appears under the More Info tab below the Actions list.

  5. Fill in the necessary fields under the More Info tab.
  6. Field
    Comments
    Name
    Required. Name for conveniently referring to the action.
    Sequence
    Required. Number describing the order in which the action occurs. Execution begins with the action with the lowest sequence number (such as 1). Actions with the same sequence number are executed in random order. Actions occur in sequence until all actions are completed.
    Active
    Required. Check the box to indicate whether the action will be triggered or not. Inactive actions are ignored when the event occurs.
    This is a quick way to turn off an action without changing the start and end dates.
    Conditional Expression
    If the conditional expression evaluates to TRUE, the action is triggered when the event occurs.
    Start Date
    The date on which the action starts occurring.
    End Date
    The date on which the action stops occurring.
    Action Type
    Required. Select the type of action from the drop-down menu:
    • Attribute Set. Sets a user profile attribute. The most common action type. For example, "ProdName" is set to a product in the user's Shopping Cart.

      Attribute Set uses the Profile Attribute, Set Operator, Value, Set Minimum, and Set Maximum fields.
    • BusService. Invokes a business service method. Can also be used to trigger a workflow process or to get profile attributes. The input argument is a property set.

      BusService uses the Business Service Name, Business Service Method, and Business Service Context fields.
    • InvokeMethod. Invokes a method on the object (applet, business object, or application) that caused the event to occur.

      InvokeMethod uses the Method Name and Method Argument fields.
    Description
    Optional. More detailed information about the action.
    Profile Attribute
    The user profile attribute to set.
    Set Operator
    One of five choices:
    • Set: sets a user attribute to an explicit value.
      Example: Set DidLogin to "Yes".
    • Increment: increments a user attribute by an integer (default value, if Set Expression is blank, is 1).
      Example: Increment PagesView by 1.
    • Decrement: decrements a user attribute by an integer (default value, if Set Expression is blank, is 1).
      Example: Decrement PagesView by 10.
    • Add List: adds a value to a comma-delimited list.
      Example: add the name of the current product to the list of products viewed.
    • Remove List: removes a value from a comma-delimited list.
    Value
    The expression to use with the set operator. This can be any expression that evaluates to something the Set Operator can use, usually a business component field.
    The Personalization Business Rules Designer is used to pick the business component field.
    Set, Add List, and Remove List must evaluate to a single value. Increment and Decrement must evaluate to an integer.
    Set Minimum
    For attributes that are numbers this creates a minimum value under which the attribute cannot fall.
    Set Maximum
    For attributes that are numbers this creates a maximum value over which the attribute cannot rise.
    Business Service Name
    Name of the business service to invoke, if the conditional expression evaluates to TRUE and the type is BusService.
    Business Service Method
    Method to invoke on the business service.
    Business Service Context
    Parameter to pass to the business service method. While a business service can take many name/value pair parameters, you can only pass one parameter—called Context—in Siebel Personalization.
    An example of a business service context is:
    Action Type: BusService
    Business Service Name: Workflow Process Manager
    Business Service Method: RunProcess
    Business Service Context: "ProcessName", "My Workflow".
    Method Name
    Method to invoke on the business component, if the conditional expression evaluates to TRUE and the action type is Invoke Method.
    Method Argument
    Parameter to pass the business component. You can only pass one argument.


 Siebel Personalization Administration Guide 
 Published: 18 April 2003