Bookshelf Home | Contents | Index | PDF |
Siebel Order Management Guide > Creating and Managing Catalogs > About Dynamic Product Catalogs > About Configuring Dynamic Product Catalog AppletsNOTE: This topic does not apply if you are using Siebel Open UI, which does not support dynamic product catalogs. All Dynamic Catalog applets belongs to special classes, This specialization is needed because the dynamic catalog view render Standard Interactivity (SI) catalog applets in High Interactivity (HI) views. These specialized classes all use same technique to display SI applets in HI views. All these classes are declared as HI enabled, but the applets are configured as SI applets with one specialized ActiveX control added: the control ProdSelectionCC of type CustomControl. This control must be added to a web template item of the applet definition as well as to a control type item. This specialized ActiveX control is used to create a place holder HI applet with one single hidden ActiveX control on it. When the Siebel Web Engine renders the SI applet for the view, this custom control is instantiated and the SI layout is generated. This layout then is inserted into the empty HI applet placeholder space. Special code is needed both on the server side and on the client side to provide HI user experience, to render SI controls as HI, and to take user input from the controls. Each class used for Dynamic Catalog applets addresses specific needs and customizations, but most of the classes can be reused by customers who want to extend or customize existing catalog applets. All new implementations using these applet classes must follow base guidelines for developing SI applets. In addition, they must limit types of the controls and layouts to ones shipped with the product. Dynamic Catalog applets belong to the following specialized classes:
|
Siebel Order Management Guide | Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |