IBM 4.6.x Network Card User Manual


 
Cardinality
=
n
IsKey
=
false
IsForeignKey
=
false
AppSpecificInfo
=
MVL=Active;LFN=Street
Address
Another
example
for
the
child
business
object
Siebel_BCOpportunity
is
shown
here
which
has
a
many-to-many
relationship
to
Siebel_BCContact
or
Association.
In
this
case,
on
a
Create
operation,
the
connector
searches
for
the
business
component
using
the
populated
fields
of
the
business
object
in
the
container.
If
the
connector
finds
a
matching
object,
it
associates
it
with
the
parent
business
component.
If
the
object
is
not
found,
an
error
is
logged,
and
the
business
object
request
fails.
Name
=
Siebel_BCContact
Version
=
1.0.0
AppSpecificInfo
=
ON=Contact;CN=Contact
Name
=
ContactId
Type
=
String
Cardinality
=
1
MaxLength
=
10
IsKey
=
true
IsForeignKey
=
false
IsRequired
=
false
AppSpecificInfo
=
FN=Id
Name
=
...
Name
=
...
Name
=
Siebel_BCOpportunity
Type
=
Siebel_BCOpportunity
ContainedObjectVersion
=
1.0.0
Relationship
=
Containment
Cardinality
=
N
MaxLength
=
0
IsKey
=
false
IsForeignKey
=
false
IsRequired
=
false
AppSpecificInfo
=LFN=Opportunity;Assoc=true
This
example
is
for
a
simple
link
relationship.
In
this
case,
there
is
a
simple
link
between
Quote
and
Order
Entry:
Name
=
Siebel_BCQuote
Version
=
1.0.0
AppSpecificInfo
=
ON=Quote;CN=Quote
Name
=
QuoteId
Type
=
String
Cardinality
=
1
MaxLength
=
10
IsKey
=
true
IsFireignKey
=
false
IsRequired
-
false
AppspecificInfo
=
FN=Id
Name
=
...
Name
=
...
Name
=
Siebel_BCOrderEntry
Type
=
Siebel_BCOrderEntry
ContainedObjectVersion
=
1.0.0
Relationship
=
Containment
Cardinality
=
N
MaxLength
=
0
Chapter
4.
Understanding
business
objects
45