Siebel Personalization Administration Guide > Tracking Run-Time Events >

Creating Actions for Action Sets

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 Administration - Runtime Events.

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

To create actions for an action set

  1. Navigate to the Administration - Runtime Events screen > Action Sets view.
  2. Select the action set, and in the Actions list, create a new record.
  3. Complete the fields as needed under the More Info tab.

    Some fields are described in the following table.



    Required. Name for conveniently referring to the action.


    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.


    Required. Check to indicate whether you want the action triggered or not. Inactive actions are ignored when the event occurs.

    NOTE:  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.

    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.

      For example, to create an action in which you specify the profile attribute service:

      • Select Attribute Type from the Action Type field.
      • Enter AttributeFooValue in the Profile Attribute field.
      • Enter Set in the Value field.
    • BusService. Invokes a business service method. You can also use this action type 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.

    Profile Attribute

    The user profile attribute to set.

    Set Operator

    One of five choices:

    • Set. Sets a user attribute to an explicit value. For example, Set DidLogin to Yes.
    • Increment. Increments a user attribute by an integer (default value, if Set Expression is blank, is 1). For example, Increment PagesView by 1.
    • Decrement. Decrements a user attribute by an integer (default value, if Set Expression is blank, is 1). For example, Decrement PagesView by 10.
    • Add List. Adds a value to a comma-delimited list. For example, add the name of the current product to the list of products viewed.
    • Remove List. Removes a value from a comma-delimited list.


    The expression to use with the set operator. You can use any expression that evaluates to something the Set Operator can use, usually a business component field.

    Use the Personalization Business Rules Designer 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.

    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".

    Use the following eScript command to retrieve the value from the business service context from a custom build business service:

    var sValue = Inputs.GetProperty("Context")

    Expressions like Today() or [<Field Name>] are not calculated. Only the plain string is sent to the business service and the string must be interpreted within the business service. In business services, like Workflow Process Manager, the name value pairs are used as input arguments. However, in a custom business service you must develop this functionality.

    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