Refreshing Properties for Attributes with Business Component Domain Do Not Work (Doc ID 2208826.1)

Last updated on DECEMBER 06, 2016

Applies to:

Siebel CRM - Version 8.1.1.11.12 [IP2013] and later
Information in this document applies to any platform.

Symptoms

Attributes with Business Component Domains do not refresh correctly for a default Product or for a Product added with constraints.

The behavior can be reproduced by following the below steps:

Steps to specify the Product Model:
1. Navigate to Administration - Product > Product Classes and create a class "Account Service Class" with attributes:
   "Account Name" of type Text
   "Account Location" of type Text
   "Account ID" of type Text

2. Release the Class

3. Navigate to Administration - Product > Product Definition and create a product "Account Service Package" of class "Account Service Class"
    Define 3 Com as default attribute for Account Name

4. Specify the following properties on the Account Name attribute:
    PickList = PickList Account
    PickApplet = Account Pick Applet
    PickMap01 = <PickMap Field="Account Name" PickField="Name">
    PickMap02 = <PickMap Field="Account Location" PickField="Location">
    PickMap03 = <PickMap Field="Account ID" PickField="Id">

5. Specify the following properties on the Account ID attribute:
    Hide = Y
    RefreshBO = Account
    RefreshBC = Account
    RefreshKey = Id
    RefreshMap01 = <RefreshMap Field="Account Name" RefreshField="Name"/>
    RefreshMap02 = <RefreshMap Field="Account Location" RefreshField="Location"/>

6. Release the product and refresh cache

Alternately Validate the Product

Account Name attribute is populated with 3 Com.
However Account Location is not populated
Pick another Account or again pick the 3 Com Account
Notice that when you pick the account, the Account Location is populated.

The value for the Location is picked correctly using Pickmaps if the Account is picked.
However when the Siebel Administrator sets the default value in Administration - Product Screens for the Attribute or define a Constraint, upon opening the eConfigurator the primary Attribute value is set correctly, but the other Attributes in Pick Map whose values depends on the primary Attribute are not automatically selected as expected.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms