Chapter
business
v
“Modifying
business
object
samples”
v
“Overview
of
Siebel
ODA”
on
page
52
v
“Installing
and
using
Siebel
ODA”
on
page
52
v
“Using
SiebelODA
in
Business
Object
Designer”
on
page
56
v
“Reviewing
the
generated
definition”
on
page
68
v
“Adding
information
to
the
business
object
definition”
on
page
70
Modifying
business
object
samples
Business
object
samples
are
provided
with
the
connector
component
of
the
adapter.
All
objects
must
have
Siebel
triggers
on
them
for
polling.
In
some
cases,
you
may
need
to
customize
the
object
in
Siebel
Tools.
This
section
describes
sample
objects
and
provides
examples
of
how
to
customize
them.
v
“Siebel_BCAccount”
on
page
49
v
“Siebel_BCQuote”
on
page
50
v
“Siebel_BCContact”
on
page
50
v
“Siebel_BCInternalProduct”
on
page
51
v
“Siebel_BCAsset”
on
page
51
Siebel_BCAccount
1.
Locate
the
following
Siebel
VB
files:
Siebel
6
Account_Write.svb,
Account_PreDelete.svb,
Business_Address_PreDelete.sbv,
and
Business_Address_Write.svb.
Siebel
7
Account.sbl
or
Account.js
The
Siebel
VB
files
are
located
in
the
Common/Siebel/Dependencies/Siebel_VB
directory.
2.
Save
the
files
in
a
temporary
directory.
For
example,
use
Temp
as
the
directory
name.
3.
Give
the
CWCONN
account
the
System
Administrator
responsibility
within
Siebel.
4.
In
your
Siebel
Tools
environment,
check
out
and
lock
the
Account
and
Contact
projects.
5.
Add
the
VB
script
to
the
Account
business
component
as
follows:
a.
Right-click
on
the
Account
business
component,
and
select
Edit
Basic
Scripts
from
the
menu.
This
launches
the
script
editor.
b.
Import
the
VB
code
by
selecting
Import
from
the
File
menu,
choosing
the
Temp
directory,
and
picking
Account_Write.svb
for
import
into
the
Bus
Comp
object
and
BusComp_WriteRecord
procedure.
c.
Import
the
second
VB
code
by
selecting
Import
from
the
File
menu,
choosing
the
Temp
directory,
and
picking
Account_PreDelete.svb
for
import
into
the
Bus
Comp
object
and
BusComp_PreDeleteRecord
procedure.
d.
Save
changes
to
the
object.
6.
Add
the
script
to
the
Business
Address
business
component
as
follows:
©
Copyright
IBM
Corp.
1997,
2004
49