Siebel Developer's Reference > Business Component User Properties > Doing Other Work >

Using Aspects to Control Read Only, Insert, and Other Behavior

An aspect determines how Siebel CRM displays data from a business component. You can use one of the aspect user properties to configure business component behavior according to the applet that Siebel CRM uses to display data from this business component. For example, the applets that reference the Action business component might contain different predefault values for the Type field. An aspect user property is optional.

Aspect User Properties for the CSSBCBase Class

If Siebel CRM sets an aspect for an applet that references the CSSBCBase class, then it modifies the behavior of this class according to the following user property setting. These settings assume the current aspect is Aspect and the value of Field Name is Y:

• Aspect BC ReadOnly: Aspect. The current record becomes read-only.
• Aspect Child BC ReadOnly: Aspect. The child business components of the current record become read-only.
• Aspect BC NoInsert: Aspect. The user cannot insert a new record. You must make sure that Siebel CRM does not modify the [Field Name] value if the user steps off the record. If it does modify this value, then the behavior in the client might confuse the user. An incorrect configuration makes an insert that depends on the state of the current record. This configuration is probably not what your implementation requires.
• Aspect Default Value: Aspect. If you define Aspect Default Value: Aspect for a business component field, and if the current aspect is Aspect, then the predefault value for this field becomes the expression that the value of the user property defines. For example, the Action business component handles activities. If it includes a Planned field, and if you define the Aspect Default Value: Planned field user property for this field, and if the value of this user property is Timestamp(), then the predefault value for the planned start date and time of the activity becomes Timestamp().

  You cannot use Aspect Default Value with a multivalue field because a multivalue field does not use a predefault value.

Table 30 lists the aspect user properties that you can use with a business component.

Table 31 lists the aspect user properties that you can use with a field.

Aspect User Properties for the CSSSWEFrameBase or CSSSWEFrameListBase Class

You must configure Siebel CRM to set and send the aspect name to the business component that the view references in the following situations. This business component uses the CSSSWEFrameBase or CSSSWEFrameListBase class:

• You define a View Aspect* user property for the current view.
• You do not define View Aspect* for the current view but you do define the Default Aspect.

Table 32 lists the aspect user properties that you can use with a view.