| Siebel CRM Advisor Administration Guide Siebel Innovation Pack 2015 E24718-01 |
|
 Previous |
 Next |
View PDF |
| Siebel CRM Advisor Administration Guide Siebel Innovation Pack 2015 E24718-01 |
|
Previous |
Next |
View PDF |
A Need Advice button that links to an Advisor application is provided from Siebel Quotes, eSales Shopping Cart, and eSales Home Page. Click the Need Advice button to launch a placeholder contents list. Develop the contents list in Advisor. The Need Advice button can also link to a specified contents list.
|
Note: Make sure that all the products referenced from Siebel data 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. 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. |
To call your application from other Siebel applications, use one of the following methods:
Associate a pageset with a customizable product.
Create a button that links to a browser-based project contents list.
See the following sections for a description of how to use these methods:
Customizable Products can be configured at runtime by the server-based Configurator and Advisor. To open Advisor for a product, you need to associate a pageset with the product in the Administration - Product screen. After you make this association, when a user clicks the Customize button for a product, the associated pageset opens in Advisor.
To create a customizable product and associate it with a pageset
Create a customizable product and define its structure in the server-based Product Designer.
Do not create any rules and leave all the cardinalities without any values.
For information on creating customizable products, see Siebel Product Administration Guide.
Release the customizable product.
In Advisor, create a pageset.
For more information, see "To create an Advisor pageset"."
Associate the pageset to the product.
For more information, see "To associate an Advisor pageset with a product".
Use the following procedure to invoke the ShowCDA method from a button.
To call your Advisor application from another Siebel application
In Siebel Tools, create a button control on your applet.
See Using Siebel Tools for information.
For the Method property of the button, invoke the ShowCDA method.
Use the syntax:
ShowCDA(’ProjectDirectory|Pageset ID')
|
Note: This step works only if your applet class inherits from CSSFrame Base. |
The contents list of the default project appears when the button is clicked in your applet at runtime, unless you specified a different project.
For more information about the ShowCDA function, see Siebel Advisor API Reference.
You can also invoke the ShowCDA method to display an application at the applet level rather than the project level. For more information, see the following section.
In Siebel Tools, when you create an applet, you can specify additional information be passed along to the ShowCDA method when a button is clicked, including:
Project, Pageset, and Dynamic Defaults
Configuration Properties
When you pass these parameters into the applet's user properties, these parameters apply to all buttons defined in that applet. If you want to give a button different parameters, you need to do so in a different applet.
To pass project, pageset, and dynamic default information to the ShowCDA function through Siebel Tools, use the syntax in the following examples to create entries in the applet's user properties. This allows you to specify what pageset and dynamic defaults are displayed when a user clicks a button.
Example 11-1 Creating Three Buttons that Display Different Applets
This example assumes you want to create three buttons that each have different projects, pagesets, and dynamic defaults.
To create three buttons that display different applets
In Siebel Tools, create three buttons in the applets.
For example:
| Name | MethodInvoke |
|---|---|
| Button1 | ShowCDA |
| Button2 | ShowCDA1 |
| Button3 | ShowCDA2 |
Create an applet user property for each method.
Button 1
| Name | Value |
|---|---|
| Method|ShowCDA|Parameter 1 | QuoteId|Field|Id |
| Method|ShowCDA|Parameter 2 | Projectlocation|Value|project1 |
| Method|ShowCDA|Parameter 3 | Pageset|Value|pageset1 |
| Method|ShowCDA|Parameter 4 | Dyndefs|Value|dyndefs1 |
| Method|ShowCDA|Parameter 5 | End |
Button 2
| Name | Value |
|---|---|
| Method|ShowCDA1|Parameter 1 | QuoteId|Field|Id |
| Method|ShowCDA1|Parameter 2 | Projectlocation|Value|project2 |
| Method|ShowCDA1|Parameter 3 | Pageset|Value|pageset2 |
| Method|ShowCDA1|Parameter 4 | Dyndefs|Value|dyndefs2 |
| Method|ShowCDA1|Parameter 5 | End |
Button 3
| Name | Value |
|---|---|
| Method|ShowCDA2|Parameter 1 | QuoteId|Field|Id |
| Method|ShowCDA2|Parameter 2 | Projectlocation|Value|project3 |
| Method|ShowCDA2|Parameter 3 | Pageset|Value|pageset3 |
| Method|ShowCDA2|Parameter 4 | Dyndefs|Value|dyndefs3 |
| Method|ShowCDA2|Parameter 5 | End |
In this example, project1, project2, and project3 are the values passed to Advisor. The syntax is:
Method|ShowCDAxx|Parameter x = parameterName|ParameterType|ParameterValue
ParameterType can be either Field or Value. If parameterType is Field, ParameterValue is the field name, and the parameter value is pulled from that field in the business component.
While you can set variables in the application CFG file as explained in the File Reference chapter of Siebel Advisor API Reference, you can also set and pass these values in Siebel Tools. This method allows you to customize the runtime behavior for each applet. For example, you can specify that one applet navigates to a product detail view named Product List view and that another applet navigates to a different view named Product Detail View - Feature View (eSales).
To pass CFG properties to the ShowCDA function through Siebel Tools, use the syntax in Table 11-1 to create entries in the applet's user properties. Create buttons and entries in the applet's user properties just as you did in the previous example.
