Fields in an Attachment Business Component

The following table describes each field name that the file engine supplies. These names must use a special format and reference a column name in the attachment table. The name includes the prefix followed by a required suffix. The DefaultPrefix user property defines the prefix.

Name	Column	Type	Text Length
prefix FileAutoUpdFlg	FILE_AUTO_UPD_FLG	DTYPE_BOOL	1
prefix FileDate	FILE_DATE	DTYPE_DATETIME	7
prefix FileDeferFlg	FILE_DEFER_FLG	DTYPE_TEXT	1
prefix FileDockReqFlg	FILE_DOCK_REQ_FLG	DTYPE_TEXT	1
prefix FileDockStatFlg	FILE_DOCK_STAT_FLG	DTYPE_TEXT	1
prefix FileExt	FILE_EXT	DTYPE_TEXT	10
prefix FileName	FILE_NAME	DTYPE_TEXT	200
prefix FileRev	FILE_REV_NUM	DTYPE_ID	15
prefix FileSize	FILE_SIZE	DTYPE_NUMBER	22
prefix FileSrcPath	FILE_SRC_PATH	DTYPE_TEXT	220
prefix FileSrcType	FILE_SRC_TYPE	DTYPE_TEXT	30

The following table describes a field that the file engine does not supply. This field is typically present but is not required.

Name	Column	Type	Calculation
Dock Status	(calculated)	DTYPE_BOOL	IIf ([AccntFileDockStatFlg] = "N" OR [AccntFileDockStatFlg] IS NULL,"N","Y")

You can include more fields. For a special use of an attachment, such as an image control, the file engine fields can be present in addition to the fields from a predefined business component. Siebel CRM typically gets the fields from the predefined business component through a join. For example, a Product or Literature business component can contain file engine fields to support how Siebel CRM displays a product picture or a brochure picture from a bitmap image.

You can include multiple sets of file engine fields from different tables in the same business component. For example, a literature attachment can include subattachments where Siebel CRM gets the subattachments from an intersection table or an extension table. Make sure the prefix for the field name is different for each table.