Excluded

Y

Can only be defined on a relationship or on the product root. Cannot be defined on products within a relationship

When defined on a relationship, prevents all excluded items in the relationship from displaying.

If an item in a relationship is a product with components, does not prevent display of excluded products within that product with components.

When defined on the product root, prevents excluded items from displaying throughout the product.

Hide

Y or N

When set to Y, causes item to be omitted from selection pages. Can be defined on any part of a customizable product that displays in the Properties view. Acts at the UI level, so adding this UI property to hide values that are selected in existing quotes will not remove these values, just change the display.

Description

Enter a text string.

Define on relationships only.

Enter the text exactly as it will display to the user.

Image

Images/<filename>

Define on relationships only.

The image displays on the right side of relationship header. The image is displayed full size.

LearnMore

Enter the full URL to the desired location

Use with relationships only. Do not use with component products, resources, attributes, or links.

The words "Learn More" are displayed adjacent to the item and are a hyperlink to the URL you enter.

ProductHeader Image

Images/<filename>

Define on product root only.

Displays an image of the root product on every selection page. Image displays beneath item header, to the left of item labels. The default image area is 120x120 pixels square. Can only be defined on product root.

FullComputation

Y

When set to Y (Yes) and user makes an attribute selection, the Siebel Configurator engine updates the selection state of all the attribute values so that only selectable values are displayed. For example, if one of the values is excluded, it displays unavailable. Can cause performance reduction. This is the default.

When set to N (No), the Siebel Configurator engine does not update the selection state of the other attribute values and displays all the values as selectable. For example, if one of the values is excluded, it does not display unavailable. If users select an excluded value, they receive a conflict message.

Use this UI property when display of the selection state of attribute values is required.

Define on attributes with LOV domains only.

Resource

Y

Define on attributes only. When this property is set, the attribute value will be treated as engine picked, which works similar to a resource. This property is commonly used when an attribute is used as a counter that will not be changed directly by a user and that will be recalculated every time regardless what previous value or state is.

Default Group

The name of a valid group

This property specifies the default group loaded in the grandchild display.

Grandchild Enabled

Y

Define this property at the appropriate attribute group item level in order to show attributes in line with products in the grandchild display.

Grandchild Type

combo, text, radio

Define this property at the appropriate attribute group item level in order to show attribute in line with products in the grandchild display. This property specifies the type of attribute user-interface control to load.

MultiChildrenPort[N]

This property is used by the CP UI service. It lets the UI service know that before presenting a given group or the CP itself, the UI service needs to fetch more details about the user property value and relationship.

You can define this at the root level or at each group level for multiple relationships (Name: MultiChildrenPort, Value: Intrastate, Name: MultiChildrenPort1, Value: USA, Name: MultiChildrenPort2, Value: Canada, Name: MultiChildrenPort3, Value: Extended and so on, where Intrastate, USA, Canada, Extended are relationship names within the CP.

You would need to define this for each CP UI definitions. If you customize the OOTB template and add .swt template code to access child component information (attribute or relationship products) then you should define the root item as a multi children port. This is needed because the UICache used, may not contain the complete information needed for the UI (obsolete or not cached UI information such as accessing all attribute values of all products in the group item).

The disadvantage of using this is that there will be performance penalty if the total relationship domains affected by these user properties are large. If you have multiple of these remember to name these like MultiChildrenPort0, MultiChildrenPort1, and so on, for example from 0 to n. in any of 0 you have an option to just say MultiChildrenPort.