Field
names
for
a
simple
attributes
application-specific
information
for
simple
business
objects
attributes
must
specify
the
name
of
the
corresponding
field
in
the
Siebel
business
component.
The
application-specific
information
for
this
is:
FN=fieldname
For
example,
in
the
Siebel_BCAccount
business
object
the
application-specific
information
for
the
Main
Phone
attribute
specifies
that
Main
Phone
Number
is
the
corresponding
field
in
the
Siebel
Account
business
component.
The
application-specific
information
in
the
business
object
attribute
is
shown
below.
Name
=
Main
Phone
Type
=
String
IsKey
=
false
AppSpecificInfo
=
FN=Main
Phone
Number
Foreign
key
relationship
using
a
pickList
In
Siebel,
a
foreign
key
relationship
between
two
business
components
is
defined
by
a
PickList.
If
a
field
has
an
associated
PickList,
the
field’s
PickList
property
and
PickList
correspondence
define
the
relationship
between
the
two
business
components.
One
of
the
attributes
in
the
PickList
correspondence
is
usually
an
Id,
such
as
Account
Id
or
Product
Id.
On
a
simple
attribute
in
a
business
object,
if
a
Siebel
business
component
field
has
an
associated
PickList,
the
attribute
application-specific
information
in
the
business
object
should
be
coded
to
provide
the
connector
with
this
information
so
that
the
connector
can
use
the
attribute
as
a
foreign
key.
To
specify
a
PickList
for
an
attribute,
you
need
to
include
two
attributes
in
the
business
object.
The
first
attribute
identifies
the
foreign
key
field
of
the
related
business
component,
and
the
second
attribute
corresponds
to
the
field
in
the
business
component
that
has
the
PickList
as
a
field
property.
Two
attributes
are
required
because
the
PickList
relationship
is
based
on
the
object
name
rather
than
the
object
Id.
In
the
application-specific
information
for
the
PickList
attribute,
specify
that
this
attribute
is
a
PickList
using
the
text
PLK.
Then,
to
identify
which
record
in
the
PickList
should
be
selected,
use
the
text
PLK=...;Restrict=<field
name>:<Siebel
GUI
Name>,<field
name>:Siebel
GUI
Name>.
For
example,
suppose
that
you
are
creating
a
Siebel_BCAsset
business
object,
and
you
want
to
add
an
attribute
in
the
business
object
as
a
foreign
key
to
the
Siebel_BCInternalProduct
business
object.
The
Product
Name
field
in
the
Siebel
Asset
Mgmt
business
component
is
a
PickList
to
the
Internal
Product
business
component,
so
you
add
an
attribute
for
the
key
and
another
attribute
for
the
PickList.
The
attributes
might
be
defined
in
the
business
object
as
shown
below.
[Key
Attribute]
Name
=
Id
Type
=
String
Cardinality
=
1
IsForeignKey
=
true
AppSpecificInfo
=
Product
Id
[PickList
Attribute]
Name
=
ProductName
Type
=
string
Cardinality
=
n
AppSpecificInfo
=
FN=ProductName;PLK=Id
Chapter
4.
Understanding
business
objects
41