Bookshelf Home | Contents | Index | Search | PDF |
Siebel Forecasting Guide > Forecasting Setup >
Changing the Configuration of Spreadsheet Applets for New Views (Administrator)
The following procedure explains how to change the configuration of a spreadsheet applet so that end users can use spreadsheets in views other than Revenues, Forecasts, or Time Sheets.
To change the configuration of a spreadsheet applet
- Identify the business component that includes the static information of the spreadsheet. This is the primary business component.
- Identify the business component that includes the dynamic information of the spreadsheet. This is the data business component.
NOTE: In some cases, the primary business component already exists in Siebel Sales, while the data business component has to be created or modified so that it includes the columns that you want displayed in a repeating fashion.
- The primary and data business components may sit on the same table. If they do, the property DC Data SameAsPrimary must be set to Y. The primary business component must include the subclass CSSBCDynCol. The Data Business component must include a subclass CSSBusiness component.
- Configure the display applet to include the static columns and a required control called eDynamicColumns. This control acts as a placeholder for the data business component columns. Make sure that the primary business component is based on a subclass of CSSBCDynCol.
- For the primary business component, configure a Web applet based on CSSSWEFrameDynCol (or subclass of CSSSWEFrameDynCol). Include controls for the static fields, followed by the eDynamicColumns control.
- Configure the business components.
The following table gives instructions for configuring the user properties on the primary business component.
NOTE: To configure static columns in the spreadsheet so that they make universal changes to each record in Group ID, modify the user properties in business component Revenue DynCol using Siebel Tools. Find user properties like DC 1 Data Field Default #, [FieldName], Primary.[FieldName]. Remove fields you do not want and add other fields as desired. For example, the request for Revenue Type is added as DC 1 Data Field Default 9, Revenue Type, Primary.Revenue Type. Also, you need to modify the same user properties in the business component Revenue Plan Item DynCol to maintain the same Dynamic Column grouping behavior.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Forecasting Guide Published: 18 April 2003 |