AutoQuery Mode (Applet) / Prefetch Size (BC)

1. Recently I have a requirement to open an applet in Query mode by default.

Use Applet property: AutoQuery Mode = 'True' , it is working properly.Mode on view level as Query is not working.

2.If you have to fetch more then 10,000 record then you need to set BC property Pre fetch size = -1,If you are using SIA BC Utilities and it is fetching more then 10000 records and you don't set prefetch size =-1 , then it raises exception.

3.Avoid using TheApplication().RaiseErrorText() in BS , try to use raise exception instead and try to handle raised exception on more higher level.

Immediate Post Change

When This set to 'Y', Browser script PreSetFieldValue event is bypassed.

PreSetField Event does not work for Contact BC in Siebel 8.0.To make it work you need to set immediate post change true.

Wait Step- siebel Workflow

We can't use wait step in long running workflow.

Config : Link ???

Link : For creating relationship between Two BC.(1:m / m:1)
for Maintaining M:M relationship , two links require.
Property :
1.cascade Delete :
None : no action
Clear : Clear foreign Key
Delete : Delete
2.No Delete :
3.No insert:
4.No associate :
5.Visibility Rule Applied (Never Always) : Visibility rule of child bc will not applied.
6.Visibility type :

Config: Example of M:M ???

1.Opportunity : Contact
S_Opty_Con(Opty_Id/Person_Id)


2.Account : Account Team

3.Service: Solution

4.Account : contact

5.UserList : User

6.Access Control : member

7.employess : Position

8.user : responsibility
*Two links are required to maintain M:M relationship

Config : Join???

Implied Join :

one to one relationship with table and BC is maintained by hidden relationship called implied join.
*Data can be updated through implied join.

Config : Table??

Table_ATT : Attachment table
Table_XM : 1:M extension table.
Compbination of (Name , Type , PAR_ROW_ID)should be unique.
Table_X : 1:1 extension table.
CX_Table : custom table
S_Table : Siebel Base Table

Type:
-----
1. Data(Public) : can be extended
2.Data(Private):Can not be extended
3.Data(Intersection) : used to maintain m:m relationship.
4.Extension : for extension table(i:i or 1:m)
5.Extension(Siebel) : extended from S_Party

*In one to one extension , Row_id is same as Par_row_id
*Siebel provides std extension table for several data table.

Config : Data Object layer???

Data Object Type :

1. Table & Child Object
2. EIM object

Table :
1.Column
2.Index
3.user Key

Table represent physical DB table in RDBMS.

Base Table :
1.BC base table
2.Extension base table.

Config : Organization ??

Administration -> Group

1.Organization
can have multiple division.
2.Division
can have multiple sub division.
3.Sub division
can have multiple position.
4.Position

Config : data control / View control

Data control :

1.Personal Data
2.Positional Data
3.Organizational Data

View Control:

1.Responsibility
2.Views

A position can have multiple employee and vice versa.Responsibilty also can have multiple views and result would be union of all Views.

Config : User Property

Q : where do you use User Property ?
Ans :
Basically User Property is for implementing specialized behaviours of Object.
we can use User Property with following Objects. As per my knowledge , frequently objects that uses User property :
Applet
View
BC
BS
IC
IO
VBC

Config : GENBScripting ??

It is a utility to generate browser script in webmaster folder.It stands for "Generate Browser Script".If you are on local and set debugging parameter properly in tool then no need to run this utility.tools automatically take care.But if you are changing SRF then it requires .

Server
genbscript.exe /uagent.cfg /webmaster/enu enu

Local
genbscript.exe /uagent.cfg /Public/enu enu

config : Scripting ??

Q : Objects , where we can do scripting?

Ans : Applet
BC
BS
Application

Config : Application Method

Q : Application Method???

Ans :

TheApplication().GetBusObject()
TheApplication().newPropertySet()
TheApplication().LoginName()

Workflow :Mode of invoking work flow process?

Q : Mode of invoking work flow process?

Ans : 1.Local Synchronous
2.Remote Synchronous
3.Remote Asynchronous

There are two BS to invoke a work flow process
1. Work flow process manager
2.Server Request

you can use both Business services in Scripting / RunTime.

if you are using Workflow Process manager then it will be local Synchronous.

if you are using "Server Request" then you can pass parameter (Syncroous or async)
.Server Request in sync mode wait for responce from SR Broker while aSync never waith for any response from SR Broker.

Config Question

Q : Which table has repository information ?

Ans : S_Repository

Config Question

Q: If you are not part of Account Team then make that record Read Only.

Answer : 1. create a Calculated field CAL = iif(Exist[Account Team] = GetProfAtt("LoginName")
2. User Property : BC Read Only Field = CAL

Note : Account Team is a MVF.