Siebel Advisor Administration Guide > Advanced Modeling for Advisor > Working with Subconfiguration in Advisor >

About Setting Defaults in Subconfigured Data Models

In a Subconfiguration data model, defaults are defined in the following places:

• An external pageset
• The DYNDEF column of a Feature table that instantiates a CHILD
• The Feature tables within Advisor

In an External Pageset

Each of the Feature tables that need to get defaulted in the Subconfiguration data model must be explicitly referenced (including the TOP items). Using the example above with RACK, SERVER1, and SOFTWARE, the syntax would be as follows:

FTN = FEATURE_TABLE_NAME

CV = CODE VALUE

TOP:FTN=CV,TOP:SERVER1:FTN=CV,TOP:SERVER1:SOFTWARE:FTN=CV

In the DYNDEF Column

You can set defaults in the DYNDEF column of a Feature table that instantiates a CHILD. See Table 4 for sample values.

DYNDEF, like CHILD, is a reserved column name for Feature tables. In this column, you can specify which defaults load into the CHILD. A CHILD pageset only gets defaulted once. The use case is when the user selects the Ethernet Card, opens the PCI-1 pageset and changes SPEED from 4 to 3. Now the user changes the PCI_CARD UI control to SCSI Card, then back to Ethernet Card. Which value should SPEED have? The engine retains the user's selection, and therefore does not default the pageset in any way.

The same pageset can get defaulted different ways depending on how you instantiate the CHILD. If the computer example had two PCI Card slots, you could use the data as shown in Table 5 and Table 6: