After you create a business object, you can specify the verbs that are valid for the object and the method sequence of a given verb on the object. This section describes how to specify this information, using the ODA with Business Object Designer. For a detailed description of these categories of information and what they mean for business object structure in the COM connector, see Understanding business objects.
In Business Object Designer, the first screen that appears when you finish creating a business object and then open it in a separate window is the BO Properties - Select Verbs for component screen. Figure 15 illustrates this screen for the name business object created in Figure 12 and Figure 13.
Figure 15. Select verb for component screen
On this screen you specify the verbs that the business objects supports. The ODA allows you to specify the four supported verbs (Create, Retrieve, Delete, and Update) and assign as actions of each verb n plus two methods, where n equals the number of methods in the corresponding COM component. The two additional methods are those supported by the connector (LoadFromProxy and WriteToProxy). To specify additional verbs beyond the supported four, or to edit verb information after you create a business object, use Business Object Designer.
For details about business object verbs for the COM connector, see Verb ASI
For each verb selected in Step 1 of Selecting verbs, a separate window appears where you specify the method sequence that must be executed for the verb.
Figure 16 illustrates this screen for the Create verb of the name business object created in Figure 12 and Figure 13.
Figure 16. Setting the verb method sequence
The name method is provided by the Siebel business object component (defined in the type library file). The LoadFromProxy and WriteToProxy methods are provided by the ODA.
By specifying a method sequence for the verb, you are creating the verb ASI that is associated with that verb. If necessary, this verb ASI can be modified later using Business Object Designer.
For a list of the keywords supported by the COM verb ASI, see Table 10.
The Business Object Wizard - Step 6 of 6 - Save business objects screen appears.
Figure 17. Save business objects screen
You can optionally open the new business objects in separate windows within Business Object Designer, or (after specifying a key for the top-level business object) you can save the generated business object definitions to a file.
To open the business objects in separate windows
To save the business objects to a file (only after you specify a key for the parent-level business object, as illustrated in Figure 18):
Business Object Designer saves the files to the specified location.
If you have finished working with the ODA, you can shut it down by checking "Shutdown ODA COM ODA" before clicking Finish.
After you define the verb ASI (by specifying a method sequence that must be executed for each verb), Business Object Designer displays the attributes for the business object. For details about the attribute-level ASI in the COM connector, see Attribute-level ASI.
The attributes are listed on the Attributes tab in the order in which they appear in the business object structure, as defined by the numeric value in the Pos column. Simple COM object attributes are represented as simple attributes and their ASI contains the original COM attribute name and type.
For each attribute, the screen provides the name of the attribute, its type, and the ASI information. Figure 18 illustrates method attribute ASI. The name attribute of the business object has an ASI that maps the attribute to the original COM component method. In this example, the original method is indicated under the App Spec Info column, by the method_name=name ASI.
In addition, name (a child business object) has the following child object attributes:
Figure 18. Setting the attribute ASI
On this screen, you should specify whether or not a parent-level object is a key (which is required by the ODA for saving the business objects to a separate file). You can also use this screen to set child object keys as needed and to specify the following information:
After specifying the attribute-level ASI, you can view and modify the business object-level ASI. For details about business object-level ASI, see Business object-level ASI.
The business object-level ASI is listed on the General tab. The ASI value that appears in the field Business Object Level Application-specific information contains the name of the proxy class that represents this business object. The connector uses this information to map a proxy class to a business object.
This screen also lists all the verbs that are supported by the business object and provides the ASI for each verb, as it was defined in Specifying the verb ASI. If a verb is blank, then a method sequence will not be executed for that verb.
Figure 19 illustrates the business object-level ASI for the name business object. The only verb that will execute a method sequence for this business object is Create, which has a verb ASI with the method sequence illustrated here (it was originally set in Figure 16).
Figure 19. Setting the business object level ASI
On this screen you can modify the ASI of the business object and its supporting verbs.