Control User Properties:

1: When we click on a button in an applet, another applet should pop up.

Control User Property:

Method Invoke for the control: ShowPopup

Name Value

Popup Applet Name

Popup Dimension 300 X 550

SWEMode Edit

------------------------------------------------------------

Applet Level User Properties:

2: DisableNewRecord

Name ValueDisableNewRecord "Application Name"

If the specified application name is the same as the current running application name, NewRecord is disabled on this applet. For example, a value of Siebel Sales Enterprise will disable NewRecord on the applet when running within Siebel Sales Enterprise application.

3: Named Method n:

Name ValueNamed Method 1 “INVOKE”, “Button Name”

For Enabling the Button without scripting

BC User Properties:

4: Always Enable Child [BusComp name]

In Service Request BC:User Property:

Name ValueAlways Enable Child: Action TRUE

Example:

In Service Request BC, if the status is ‘Closed’ , all the child entities will become read only. But, if we want to make Activies related to that Service Request enabled, then use the above user property.

Used in freezing Service Requests. Closing a service request does not prevent updates to the Customer Satisfaction business component, so you can survey your customers even if a service request has been resolved. The user property for the Service Request business component, named Always Enable Child: Customer Survey, allows you to enable and disable this behavior. You can disable

the freeze behavior for other business components by adding user properties to the Service Request business component and substituting the business component name for the appropriate component. Unfreezing Service Requests - To unfreeze a closed service request and make the service request and its child business components accessible for additions and edits, change the status to Open.

5: Always Enable Field

In Service Request BC:User Property:

Name ValueAlways Enable Field Sub-Status

Example:

In Service Request BC, if the status is ‘Closed’ , The record is going to become read only.But, if we want to make the changes in Sub-Status Field, then use above user property.

6: Deep Copy n

In Account BC:

Name ValueDeep Copy 1 Action (Child BusComp Name)

Deep Copy 2 Quote

Deep Copy 3 Service Request

Example: If we copy Account, the associated activities should be copied

Allows child business components and respective child business components to be copied automatically when selecting the Copy option. Normally, Copy option only copies one level. This feature allows multiple levels to be copied like a cascade copy.

7: Deep Delete n

Name ValueDeep Delete 1 Action (Child BusComp Name)

Deep Delete 2 Quote

Deep Delete 3 Service Request

Example: If we Delete Account, the associated activities should be deleted

Normally, the Delete option only deletes one level. Deep Delete allows child business components and their respective child business components to be deleted automatically when selecting the Delete option. This feature allows multiple levels to be deleted like a cascade delete.

8: Field Real Only Field

9: BC Read Only Field

10: Parent Read Only Field

11: NoDelete Field

Name ValueNoDelete Field Flag

You can inactivate or modify the values for this user property. You can also create new instances of this user property as needed.

12: On Field Update Set n

Name ValueOn Field Update Set 1 [FieldToCheck], "[FieldToSet]", "[Value]"

Example: "Account Status", "Type", "IIF ( [Account Status] = 'Active', ""Customer"", """" )"

You can create additional instances of this user property as needed. If you have more than one instance of this user property for a business component, they are executed sequentially by number (for example, On Field Update Set 1, then On Field Update Set 2, and so on). If there is only one such user property, then no number is required.

13: On Condition Set Field Value:

Name Value

On Condition Set Field Value “Condition”, “Field Name”, “Field Value”

If Account Status = ‘Active, Then Flag should become ‘Y’

“[Account Status] = ‘Active’”, “Flag”, “Y”

14: All Mode Sort

Name ValueAll Mode Sort Normal/True/False

Standard Siebel application behavior is to override the sort specification on views with certain visibility types to force it to ORDER BY the standard user key. The All Mode Sort user property determines whether or not the Siebel application overrides the sort specification and, if so, determines the sort (if any) that is applied to the business component for the affected views.

Field Level User Properties:

15: Text Length Override

Name ValueText Length Override 100

Use the fields Text Length property to define the maximum field length instead of� the database column size. Use only for Text type fields.