Siebel Advisor Administration Guide > Advanced Modeling for Advisor > Dynamic Defaults in Advisor Applications >
Creating Dynamic Defaults for Advisor Applications
Use the following steps to create dynamic defaults.
- Determine what UI Controls (and the Feature tables that populate them) need to be changed on the new Input UI page to reflect the choices made at the Needs Analysis level.
- In a Configuration table, create an output column to store pageset IDs or URLs of recommended products.
- In the same table, create an output column to store the defaults to change on the recommended Inputs page.
- Create a link target to reference the recommended product column and dynamic default column.
The following procedure is one way to create dynamic defaults.
NOTE: Dynamic Defaults requires the creation of a second pageset. See the LoadPageset and LoadPagesetWithDynDefObj sections in Siebel Interactive Designer API Reference.
To create dynamic defaults
- Navigate to Administration - Product > Advisor Pagesets > Configuration Tables.
- In a Configuration table, create a DYNDEFS column.
In this example, a Pagesetname column is not necessary because the PagesetName will be part of the string in the DYNDEFS column.
- In the DYNDEFS cells, enter the pagesetID and desired Feature table values in the format:
PagesetID','1stFTName=value, 2ndFTName=value, nthFTName=value
- In the Output UI control:
- Select the Control Type LINK.
- In Label, enter the text you want to appear before the link.
- In Table and Column, reference the Configuration table and DYNDEFS column.
- Select Pageset.
- In Anchor Text, enter the text that appears as the link.
Notice the single quote, comma, single quote in-between PagesetID and 1stFTName in Step 3. Because the wrapper puts the outside quotation marks around the string,
NOTE: When used in Feature tables, DYNDEF is reserved and refers to a subconfiguration child's dynamic defaults. In Configuration tables, it is not reserved, but you should not use DYNDEF in more than one Configuration table. The column names in Configuration tables are global, so you only end up with one DYNDEF output even if you have multiple instances of the column. Instead of using DYNDEF in Configuration tables, use more descriptive names, such as UPSELL_DYNDEF.