|
Configuring Siebel Business Applications > Configuring Special-Purpose Applets > Configuring a File Attachment Applet >
Configuring an Attachment Business Component
The Business Component property of the attachment list applet identifies the business component that the Siebel File System uses to store the attachment list data. For example, this business component for the Account Attachment Applet is named Account Attachment. To configure an attachment business component
- In Siebel Tools, in the Object Explorer, click Business Component.
- In the Business Components list, locate the attachment business component you must modify.
- Make sure the value in the Class property is CSSBCFile or a subclass of CSSBCFile, such as CSSBCSalesTool or CSSBCEventFile.
- Make sure the Table property references an attachment table.
For example, the attachment table is S_ACCNT_ATT in the Account Attachment Applet. For more information, see Configuring an Attachment Table.
- In Siebel Tools, in the Object Explorer, expand the Business Component tree, and then click Business Component User Prop.
- In the Business Component User Props list, create a new business component user property using values from the following table.
- In the Business Component User Props list, create a new business component user property using values from the following table.
|
|
FileMustExist |
Use one of the following values:
- TRUE. If the file does not exist, then the user cannot enter the name of the file. TRUE is the typical value.
- FALSE. If the file does not exist, then the user can enter the name of the file.
|
- Make sure the Predefault property of the FileDockReqFlg business component field is N.
The FileDockReqFlg references the required FILE_DOCK_REQ_FLG column in the attachment table.
- Add the required business component fields.
For more information, see Fields in an Attachment Business Component.
Fields in an Attachment Business Component
Table 53 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.
Table 53. Fields in an Attachment Business Component
|
|
|
|
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 |
Table 54 describes a field that the file engine does not supply. This field is typically present but is not required.
Table 54. Field in an Attachment Business Component That the File Engine Does Not Supply
|
|
|
|
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.
|
