| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Interactive Designer Administration Guide > Advanced Modeling > Working with Subconfiguration >
About Setting Defaults
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 Interactive Designer
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 3 for sample values.
DYNDEF, like CHILD, is a reserved column name for Feature tables. In this column, you can specify which defaults will load into the CHILD. A CHILD pageset will only get 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 will retain the user's selection, and therefore not re-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 4 and Table 5:
| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Interactive Designer Administration Guide Published: 18 April 2003 |