Siebel Advisor Administration Guide > Referencing Other Siebel Data from Advisor >

Binding Advisor Data to Siebel Business Components

Advisor Feature and Configuration tables are populated with static data or referenced Siebel data. Static data is entered directly into the table, and referenced Siebel data is updated in Advisor when it changes in the Siebel database. When you bind to a business component in a Feature or Configuration Table, you provide a connection back to the Siebel database. Siebel Interactive Selling products share a single data source, or product item master, stored in the Siebel database.

NOTE:  After you publish a project, the published data does not change if the data changes in the Siebel database. You need to deploy your project to refresh the data.

NOTE:  Make sure that all the products referenced within a browser-based model to set up interactions with other Siebel Applications are set to the same organization that the runtime users may belong to. Note that a product can be set to multiple organizations. If products are not set up in this way, runtime users may encounter errors while making the transition from browser-based applications to other Siebel applications, such as Getting Price and Adding to Cart, and not see certain products, both in connected and in disconnected mode.

How the Binding Works

Feature and Configuration Table Designer provide three columns to use to bind to your Siebel data.

• Business Component

  Use the picklist to specify a Siebel business component.

• Field Name

  Use the picklist to specify a field in the Siebel business component you have chosen.

• Shared

  If more than one column shares the same row of data in the business component, use this check box to specify those extra columns.

The binding works by mapping the table column to a Siebel business component. For more information, see Siebel Advisor API Reference.

Configuration Table Designer Example

Figure 16 shows the Configuration Table Designer with two shared columns.

Figure 16. Shared Columns in a Configuration Table

The CONTACT column is mapped to the Key Contact ID field in the Siebel business component named Opportunity. The POSITION column is mapped to the POSITION field in the Siebel business component named OPPORTUNITY. The two columns, CONTACT and POSITION, share the same target, that is, they both get their values from the same row of data in the Opportunity business component.

You pick actual values for the mapped columns in the Table Editor. The cells in each mapped column appear with a pop-up picklist. Choose values from the business component to populate the mapped column.

In the example shown in Figure 17, A.K. Parker was chosen in the CONTACT column. The selected contact's position populated the POSITION column because the CONTACT and POSITION columns are linked with a shared target.

Figure 17. Shared Columns in a Configuration Table