BusComp

name

Name of the business component, for example, name="Service Request Attachment"

Yes

ui-name

This is the string that will be displayed in the user interface, for example, ui-name="SR Attachments"

Yes

on-name

This attribute is not supported.

No

url

This attribute is defined as follows:

url="http://%webserver%/%objmgr%_%lang%/start.swe?SWECmd=GotoView&SWEView=#VIEWNAME#&SWERF=1&SWEHo=%hostName%&SWEBU=1&SWEApplet0=#APPLETNAME#&SWERowId0=#ROWID#"

Yes

parent

This attribute is used to specify the parent of a child business component, for example, parent="Service Request"

No

fkey-field

This attribute is used to define a foreign key field, for example, fkey-field="Activity Id"

No

field

bc-name

Name of the business component field, for example, bc-name="Attachment List"

The value displays in the Field Name column of the Available Fields list applet.

Yes

in-name

This is the index field for the business component field, for example, in-name="listing01"

See Table 11 for a list of required, recommended and optional in-name definitions.

Yes

ui-name

This is the string that will be displayed in the user interface, for example, ui-name="Attachments"

The field name is displayed on the application UI if the Searchable flag is checked in the Available Fields list applet.

This field attribute is optional. A value must be provided if the field is to be added to the body field teaser of the result set. This populates the Available Fields list applet on the Siebel Search administration UI.

No

on-name

This attribute is not supported.

No

nv-name

This attribute is not supported.

No

is-id

This attribute is not supported.

No

id-rank

This attribute is not supported.

No

on-name

This attribute is not supported.

No

one2many

This attribute is used for passing the business component child category information. This attribute is mandatory for one-to-many mappings and must conform with to the following format:

<Child Business Component Name>:<Child Fields><Child Reference Field>, for example, Service Request Attachment:ActivityFileSrcPath,ActivityFileName,ActivityFileExt,Activity Id.

In the above example the constituent parts are as follows:

Child Business Component Name. This must be the exact name defined in Siebel Tools. Child Business Component Name takes just one value, for example, Service Request Attachment.

Child Fields. Comma separated list of child business component fields to be indexed, for example, ActivityFileSrcPath,ActivityFileName. One or more values can be entered for Child Fields, each value must be separated by a comma.

Child Reference Field. Child Reference Field is the foreign key equivalent of the parent Business Component linked to PAR_ROW_ID of the child table, for example Activity Id. Child Reference Field takes just one value.

type

Used to define the file type represented by the field. Valid values are as follows:

• type="path"
• type="filename"
• type="ext"
• type="na"