could u plz explain that more

thanks in advance..

This is not true . Actually BC search specification will be replaced by Applet Search specification(NOT appended) and finally you will get the data queried using Applet search spec.

Cheers !!!

-DJ

Its true....the search spec of applet will be APPENDED to that of the BC and will be executed.

Its true...the search spec of applet will be appended to that of the BC.

suppose you have a hierarchy like

1. automobiles

2. cars bikes

3. maruthi TATA Honda and Bajaj Honda LML

you are storing all the automobiles infromation in some Product table.

you will have different BC's for cars and bikes with their SearchSpec as Type 'Car' and Type 'Bike'

you are using three applets for cars which have Maruthi TATA Ford. for these applet SearchSpec will be some Make 'Honda'

then this applet will get the Honda records from its BC (it'll contain all cars records).

**if this applet Search Spec overrides the BC Search Spec then it will fetch all the Honda make automobiles they will include both cars and bikes. **

See Siebel configuration Planning is Top to Bottom layer but Implementation / execution is bottom to top .ok

B.c search over-rides with Applet search spec..

By

Anand

Why not reference Siebel Tools Ref in the bookshelf ? Shouldn't be any argument on this since it states clearly on page 487 :

An applet search specification cannot be used to override the search specification of the underlying business component if the business component has one. Rather than overriding the business component s search specification the applet s search specification is appended to that of the business component. Search specifications should appear in the business component or the applets that use it but not both.

It goes further to explain that the data manager converts the applet search spec to a WHERE clause while forming the SQL at runtime.

Xeon

hi

it's true

bc search spec appended with applet search spec