Bookshelf Home | Contents | Index | PDF |
Siebel Product Administration Guide > Products with Attributes > Creating a Configuration Session Specific Computed AttributeYou can define an attribute that is specific to the configuration session. The attribute value is computed during the start of the configuration session, but it is not synchronized to the line items or the database. The attribute is treated as a virtual attribute for a product and is accessible within the Siebel Configurator user interface, constraints, scripts and properties. One example is when you want to capture an attribute value whose sole purpose is to trigger a product's constraints. For example, you create an attribute called Additional Fee with a domain value of Yes and No, where the default value is set to No. You then write a requires rule that selects products Late Fee and Finance Charge when Additional Fee = Yes. When the user launches Siebel Configurator, and sets the Additional Fee = Yes, the constraints are triggered and Additional Fee products are selected. Note that when you exit from Siebel Configurator, you will not be able to see the Additional Fee attribute displayed in the line item attribute applets. Thus reducing the number of attributes that are captured in the database primarily for computational purposes. NOTE: It is recommended that you do not reference these attributes within Eligibility & Compatibility and pricing rules. You also cannot set the Required field to Y within the attribute definition of the class or product. To create a configuration session specific computed attribute
|
Siebel Product Administration Guide | Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |