Product Administration Guide > Siebel Configurator in Release 6.x, 7.0 and 7.5 >
Designing Scripts in Release 6.x and 7.x
In release 7.0 and 7.5, the full Siebel API is accessible from within a script. See Siebel API documentation for more information on the Siebel API. Because the Siebel API is available, the number of Siebel Configurator-specific events and functions has been reduced in release 7.0 and 7.5. In addition, the method for associating scripts with parts of a model has changed. In release 7.0 and 7.5, you associate a script with an item by writing the script on an event called for the product root. The event returns a matrix of records, one for each item that has changed in the solution. An item can be any product added to the customizable product from the product table. Events do not return changes to relationship quantities or resources. If a customizable product contains other products with components, another event is provided so you can write scripts on the child customizable product directly. The Script Designer in release 7.0 and 7.5. does not provide a hierarchical tree display of the customizable product. In release 7.0 and 7.5, the Cfg ID of an item can no longer be passed as an argument. Instead, the name of the item as a string is passed. A name syntax is provided to allow you to uniquely specify a product name. Table 49 maps 6.x features to 7.0 and 7.5 for designing scripts.
Table 49. Designing Scripts
|
|
|
Create scripts |
Create scripts in the Script Designer. |
None |
Script inheritance |
Scripts are not associated directly with relationships and are not inherited. |
None |
Copy, edit, and delete scripts |
Copy, edit, and delete scripts. |
None |
Siebel Visual Basic and Siebel eScript languages |
Siebel Visual Basic and Siebel eScript languages. |
None |
Syntax checking |
Syntax checking. |
None |
Declaration area |
Declaration area. |
None |
Scripts can be written on product root |
Scripts can be written on product root. |
None |
Events return changes to categories |
Events return changes only to items added from product table. Events do not return changes to relationship quantities. |
Relationships are a grouping mechanism within a customizable product and are similar to categories. |
Cfg_ItemInitialize |
Use Cfg_InstInitialize. |
Cfg_InstInitialize triggers once when session is started. |
Cfg_ItemPreRequestSubmit |
Not supported. |
Can be simulated in some cases using the User Interface API. |
Cfg_ItemChanged |
Use this event only for child-products with components. Use Cfg_ChildItemChanged for other components. |
None |
Cfg_CategoryChanged |
Not supported. |
None |
Cfg_SessionPostProcess |
Not supported. |
None |
Cfg_ItemPreSynchronize |
Use Cfg_InstPostSynchronize. |
None |
Cfg_ItemPostSynchronize |
Cfg_InstPostSynchronize. |
None |
Cfg_SessionClosed |
Implemented at Instance Broker level. Use Siebel API. |
None |
GetSessionId |
GetInstanceId. |
Returns the row ID of the customizable product in the source object, (quote, order and so on). |
GetCfgId |
Not supported. No longer meaningful. |
None |
GetItemId |
Not supported. |
None |
GetItemQuantity |
GetObjQuantity. |
Returns the quantity of a component within the customizable product. Cannot be used for relationship quantities. |
GetPropertyValue |
Getting attribute value is supported through the Siebel API. |
None |
GetItemState |
Supported through Siebel API |
None |
SubmitRequest |
AddItem, RemoveItem |
None |
|