Configuring Siebel Business Applications > Configuring the Customer Dashboard > Options to Update the Customer Dashboard >

Configuring a Button to Update the Customer Dashboard

The Customer Dashboard includes application programming interfaces (APIs) to pull information from or push information to the Customer Dashboard through Siebel Visual Basic script or Siebel eScript script. The Customer Dashboard resides in a separate frame, so it requires a user interface event to update customer dashboard fields. To create a user event, you must add a button to an applet that uses a script to call the Update Dashboard command.

To configure a button to update the Customer Dashboard

1. In Siebel Tools, in the Object Explorer, click Applet.
2. In the Applets list, locate the applet you must modify.
3. In the Object Explorer, expand the Applet tree, and then click Control.
4. In the Controls list, add a button as an applet control and set properties using values from the following table.

   Property	Value
   Target View Frame	Dashboard

5. Define the script for the new button.

   Your script must do the following:

   • Call the Update Dashboard command. For more information, see Using Siebel Visual Basic or Siebel eScript to Update Information in the Customer Dashboard.
   • Use the InvokeMethod function and send a set of name-value pairs. The following are examples of name-value pairs:
     • Source Name: 'Base View'
     • BusComp Name: 'Contact'
     • RowId: 'srowid'
6. Compile and test your modifications.

   For more information, see Using Siebel Tools.

Updating the Customer Dashboard With Data from a Virtual Business Component

An update to the Customer Dashboard requires a row ID. A virtual business component uses a virtual row ID. To display information from a virtual business component in the customer dashboard, you must script the UpdateDashboard function.

Customer Dashboard Allows Only One Update for Each User Interface Event

The Customer Dashboard allows only one user interface update for each user interface event. For example, if you add a button to a view, then one click of that button is one user interface event. For that event, Siebel CRM can run only one user interface update, such as updating the Customer Dashboard. The code behind a single button cannot include two user interface updates, such as updating the Customer Dashboard, and then displaying a new view in the main frame of the Siebel application.