Table of Contents
Advertisement
Table 6. Child object attributes (continued)
Name
Relationship
IsKey
IsForeignKey
IsRequired
Cardinality
Business object application-specific information
Application-specific information in business object definitions provides the
connector with application-dependent instructions on how to process business
objects. Because a meta-data-driven connector makes assumptions about how its
supported business objects are designed, modifications to business objects must
match the connector's rules for the connector to process modified business objects
correctly. Therefore, if you modify or create Siebel application-specific business
objects, you must be sure that the application-specific information in the business
object definition matches the syntax that the connector expects.
This section describes the application-specific information for the Siebel business
object, attributes, and verbs.
Business object application-specific information
The application-specific information at the top level of a business object specifies
the name of the Siebel business object. For example, the object application-specific
information for the parent business object Siebel_BCAccount specifies the Siebel
Account object, as shown below.
[BusinessObjectDefinition]
Name = Siebel_BCAccount
Version = 1.0.0
AppSpecificInfo = ON=Account;CN=Account
Example of multiple unrelated business components:
[BusinessObjectDefinition]
Name = Siebel_BCInternalProduct
Version = 1.0.0
AppSpecificInfo = CN=InternalProduct
[BusinessObjectDefinition]
Name = Siebel_BCProductDefect
Version = 1.0.0
AppSpecificInfo = CN=ProductDefect
[BusinessObjectDefinition]
Name of the child object
If the child is a container attribute, this is set
to Containment.
This attribute has to be set on the primary
business component.
Not used.
If set to True, the child is expected to have a
representation in the parent business object.
During Create verb processing, the primary
business component is required to be
present. A check is made to see if this
component is present in the inbound
business object. If found, the create proceeds
unless an error is thrown indicating that the
required object was not found in the inbound
business object.
1 or N depending on the number of child
records that can be chosen for a parent
record.
Chapter 4. Understanding business objects
39
Advertisement
Table of Contents
