SIEBEL QUESTION AND ANSWERS

1)Whats the difference between constrained pick map and copy pick map ?

The type of pick map is determined by the value in the Constrain property. If a pick map is a copy pick map, then the value of the field in the picklist business component specified by the Pick List Field property will be copied into the field of the parent business component specified by the Field property. If the pick map is a constraint pick map, then the value from the field in the parent business component specified by the Field property will be applied as a search specification on the field in the picklist business component specified by the Pick List Field property.

2)Can we create applet without attaching it to Business component?.

Yes Business component is an Optional property 

3) Given that the application is not performing well what steps you will take to check the performance of the application

a) Configuring Active Fields

All fields on an applet are automatically activated. Siebel performs queries for active fields only. This means that if the underlying business component has fields that are active, but not displayed, Siebel will generate the necessary SQL for them. If you prevent Siebel from generating the SQL for fields that are not displayed, this could yield fewer joins on queries. To prevent Siebel from generating SQL for fields that are not displayed Do one of the following at the business component level: Select which fields are automatically activated. Remove fields from the applet, so long as they are not marked as active.

b) Siebel Docking Transaction Logging at Runtime

One way to improve response time is to turn off Siebel Docking Transaction logging if it is not being used. To turn off Siebel Docking Transaction Logging 1 From the Siebel client, choose Application Administration_ System Preferences from the Screens menu.2 Find Docking: Transaction Logging in the System Preference Name field,  and change the System Preference Value to FALSE.

c) Configuring Antivirus Software

Configuration information for the Siebel dedicated clients (Sales, Service, and Tools) is stored in a Siebel Repository file (.srf) on each client workstation. As this file is read extensively during start-up and throughout client operation, monitoring of this file by virus scanning software may significantly degrade Siebel client performance. If you have virus scanning software installed on your client workstations, you

should configure it to skip .srf files. These are binary data files that, to Siebel’s knowledge, cannot be infected, so the risk of this exclusion is very low.

In Siebel 6 for HTML thin client performance can be increased by

_ In Siebel Tools, create a separate application definition for the Web application instead of using an existing dedicated-client application. For example, create Sales HTML Thin Client instead of using Siebel Sales. _ In your HTML Thin Client application definition, follow these guidelines:

_ Reduce the number of objects—particularly the number of applets in a view and the number of fields in each applet. Specifically, do not include fields (and applets) that users don’t often need or that don’t apply to the Web. _ Do not define any view to have a list and a form accessing the same business

component. _ In your templates themselves, avoid duplicating information on the same page.

For example, do not place a list and a form referring to the same business component on one page. Avoid this even if you have a view with a list and a form accessing the same business component.

_ In your templates and other Web pages, minimise the use of multimedia objects (such as graphics, audio's, and videos).

Performance at Server side

you should ensure that the Maximum MT Servers and Minimum MT Servers parameters be set

correctly to support the anticipated number of Thin Client users. Each MT Server process can support up to 20 users before it becomes unavailable. Since the default number is 1, you should increase the number of MT servers according to your system requirements. Once you have determined the optimal setting, restart the Siebel Server to automatically register the Application Object Manager services.

4)whats the difference between Cfg file and Srf file and in which folder they are stored?

This file is used by siebel.exe to decide exactly which application to run from numbers of available applications in srf. Cfg file is configuration file used to locate srf, database, application to run. It also contains several parameters that can be used to set application behaviour like ScriptingDLL, ShowMessageBar, ApplicationTitle, font settings and so on. Srf file contains compiled versions of all object definitions that have been created/changed at the time of development. Master copy of all object definition is stored on backend database.

    

5)Can we link two business objects ?

no we can not link BO. But we can always link BC using Link object.

6)whats is MVG,MVL,associated applet and whats the relation between them and in which situation you use associated applet?

MVG : - Some fields contain multiple values; for example, an Account Team field contains records for all organisation members assigned to an account. A multi-value group (MVG) dialog box is an applet that displays all the records that make up the value of the selected field. An MVG dialog box also enables you to add or delete records.

MVL :- Multi-valued Link retrieves the records displayed through a multi-value field. The multi-value link object definition is a child of the originating business component. It identifies the link that provides the field values from the multi-value group business component.

MVF :- Displays the child records of a parent record. When the button of a multi-value field is clicked, Siebel applications will display all the child records of the parent record. The data displayed in a multi-value field is that of the actively selected parent record.

Associated applet :- The name of an applet that displays the data that can be associated with the data currently displayed. This is the mechanism used to relate data from two separate entities (that is, a many-to-many relationship). Data from entity A is displayed while data from entity B is displayed in the association applet; when one or more records are selected from the association applet, the many-to-many relationship is implicitly created by the application.

For example, association applets are provided for assigning Team Members to an Account, Contacts to an Opportunity, and Products to a Price List.

The association applet lists the records from a business component. The user selects one or more records with the aid of the Find and Starting With controls, if needed, and clicks the Add button to associate the selected record to the active master record.

Association applets are used only with pairs of business components that have a many-to-many relationship. A many-to-many relationship in Siebel applications is implemented by means of an intersection table and a pair of links.

7)How will you set the responsibility ?

A user’s responsibility or responsibilities identify the views that he or she can navigate to in Siebel Applications. Data access is typically granted to a specific user or group for specific database tables. Changes in a user’s job assignment may require adjustments to that user’s data access privileges. For example, a sales representative who is promoted to management may need access to information for multiple territories. Traditional data security measures often require that the database administrator change a user’s access privileges at the database level whenever that user’s responsibilities

change. Application Administration Responsibilities view,

You should define responsibilities that correspond to the major job functions in your sales and marketing organization. For example, you might create responsibilities for the marketing administrator, the sales manager, and sales representatives. The sales representative responsibility might have access to all screens except those reserved for sales management, marketing administration, and applications administration. The sales manager responsibility might have access to the same screens as the sales

representative, plus the Sales Manager screens, and so on.

8)how will you set the responsibility for mobile client and how will you configure mobile client?

The mobile client is designed to operate without a real-time connection to any server. This is achieved by downloading a portion of the Siebel database and the Siebel File System to the laptop so that users can access the data locally without being connected directly to the Database Server, Siebel Server, or File System. The mobile client then periodically accesses the Siebel Server through a dial-up, WAN, or LAN connection to synchronise data changes with the Database Server and File System.

Ensure that mobile users have the Siebel Remote Client Status view in their responsibilities in order to synchronise.

Local Access In the Views applet in the Responsibility Administration view are three list columns: View Name, Description and Local Access. View Name and Description list columns of Siebel applications are automatically entered when you add a view record and select a view from the picklist. The Local Access list column has a special purpose, however, and can be turned on or off for each view assignment by the administrator (by clicking the check box to add or remove the check mark).

The Local Access list column, when set to TRUE (checked) for a view assignment to a responsibility, indicates that users with this responsibility can access the view from either the Local or Server database. When set to FALSE, the view is only available to these users when directly connected to the Server database. The Local Access list column is a mechanism for controlling which views mobile users can work in offline, by controlling which ones they can see when not connected to the server. When mobile users work offline, they rely on synchronization and routing to supply some subset of the available records.

9) Why do we use assignment manager?

Siebel Assignment Manager allows sales and service organisations to effectively assign the most qualified people to specific tasks. Assignment Manager accomplishes this function by matching candidates to predefined and user-configurable assignment objects. To assign the most qualified candidate to each object, Assignment Manager applies assignment rules that you define.

Siebel Assignment Manager determines which candidates will be assigned to objects by applying scores to potential candidates. Assignment Manager then ranks the candidates based on their scores and selects assignees based on the Assignees from Rule type.

For example, in a sales organization, you may create an assignment rule that scores positions based on territory definitions for an opportunity. In a service organization, you may create an assignment rule that scores employees based on product expertise for a service request. Using the sum of scores for each assignment rule, Assignment Manager assigns the best candidate for each object. You use Assignment Manager for routing and assignment of work. After work is assigned to a user, it shows up in their personal queue.

10) What is workflow policy?

A policy consists of one or more policy conditions and one or more policy actions that result when the conditions are met.

In theory, businesses are managed according to policies and procedures that ensure efficiency, quality service, adherence to contractual agreements, and profitability. These policies enforce business processes such as:

_ ensuring that response time objectives are met for customer callbacks and open service requests

_ Specifying review policies for important processes like contracts, quotes, or product shipments

_ Monitoring service requests or opportunities over time

11)where do we run assignment manager .Do we need to have separate component to run assignment manager or it run within workflow ?

12)what are the types of assignment manager do we have?

Before running Assignment Manager, you must first complete preparation tasks. These include:

_ Checking the Assignment Manager and Server Request Manager components (so there is no w/f required)

_ Configuring the Assignment Manager component

_ Configuring Assignment Manager event logs

Assignment manager can be run in four different mode

Interactive Assignment

Running Assignment Manager in interactive mode allows users to make real-time assignments. NOTE: Mobile users running Assignment Manager in interactive mode will not make real-time assignments, since interactive assignments made by mobile users will not be applied to the server until they resynchronise. By clicking the Assign button on any selected object, Interactive Assignment allows

you to view the list of assignees generated by Assignment Manager. You can then override the assignment and select another assignee from the list in real time.

Dynamic Assignment

Dynamic Assignment enables users to create assignments as other users and server programs change assignment object attributes. For example, if a user changes the revenue amount or address of an Opportunity, Dynamic Assignment detects the change and automatically invokes Assignment Manager to reassign the Opportunity to a different territory or sales team as necessary. For each change that requires assignment, Dynamic Assignment submits a request to the Server Request Manager to assign the object. The Server Request Manager then invokes Assignment Manager to assign the object. By default, Dynamic Assignment runs Assignment Manager in Contact Denormalization mode. For more information on Contact Denormalization, 

Workflow Monitor To run Dynamic Assignment, a Workflow Monitor Agent needs to be active. A Workflow Monitor Agent detects when a user changes data related to objects.

Generate Triggers The Generate Triggers server component generates the database triggers used by

Workflow Manager to detect changes. Generate Triggers reads the Workflow Object and Assignment Object definitions in the Siebel repository and generates the appropriate database triggers to monitor changes.

Batch Assignment

You can use Batch Assignment to assign multiple records of an object in a single batch. For example, after changing assignment rule definitions, you can use Batch Assignment to reassign all objects using the new assignment rules. Batch Assignment is optimised to process a large number of items efficiently. You should monitor the performance of Batch Assignment and increase or decrease the number

of running tasks to obtain the optimal performance. You can set up Batch Assignment to run Assignment Manager in Contact Denormalization mode. For more information on Contact Denormalization, see

Mobile Assignment

Mobile Assignment allows mobile users to make interactive and dynamic assignments. Changes to the mobile client’s database are queued and will be applied to the server the next time the client synchronises. Assignment Manager automatically performs all interactive assignments made by the mobile user after synchronisation. Changes to assignment rules and objects will be updated, and affected objects will be reassigned dynamically.

13) What server process needs to be run for export of repository as well as applying  database    

scheme changes?

Archive files contain object definitions exported from a repository; they are available for importing into other repositories. They have an .sif extension, by default.

(check this I think not any specific server process is required )

14) how do you copy specified fields only in a record ?  -set no copy field porperty

15) what are the required fields for EIM ?

Siebel Enterprise Integration Manager (EIM) manages the exchange of data between Siebel database tables and other corporate databases. Use EIM to perform bulk imports, exports, merges, and deletes.

Siebel interface tables are intermediate database tables that act as a staging area between the Siebel application database and other databases. Before EIM can be used, you or a database administrator need to populate the interface tables with data to be processed by EIM. You then invoke EIM to process this data. EIM will make multiple passes through the tables to complete the specified process.

S_ type interface tables are interface tables that are used in releases prior to 6.x, and can be identified by the S_ prefix and IF suffix (such as S_ACCOUNT_IF). S_ type interface tables do not support organisations, so they can only be used to import data using EIM.

EIM type  interface tables are interface tables available in release 6.x, and can be identified by the EIM_ prefix (such as EIM_ACCOUNT). EIM_ type interface tables support organisations, so they can be used for all EIM processes. You should use EIM_ type interface tables if this is your first Siebel implementation, or if you plan to use any of the following features: Add organisations to your implementation, Export, delete, or merge data using EIM,  Set explicit primaries

The EIM configuration file  (the default file is default.ifb) is an ASCII text file of extension type .ifb that resides in the admin subdirectory under the Siebel Server directory. Before you can run an EIM process, you must edit the contents of the EIM configuration file to define the processes that EIM will perform.

To run an EIM process using the GUI

1 Choose Screens-Server Administration -Servers-Server Tasks.

2 In the Server Tasks list applet, click New.

3 Click the down-arrow button in the Component field.

4 In the Picked Assigned Component pick applet, select Enterprise Integration Mgr and click Pick.

5 Click Parameters.

6 In the Parameters Overrides view, modify parameter settings for the EIM process.

7 Click Close to save the parameter settings.

8 Click Start to execute the task.

16) What process is responsible for putting data in outbox? -router and processor

Transaction process (TxnProc) component runs in background which prepares the transaction log for the Transaction Router.

Transaction router (TxnRoute) component runs in background which Routes visible transactions to Siebel Remote and Replication Manager clients. The Transaction Router performs visibility checking and routing of transactions from the .dx files created in the txnproc directory by the Transaction Processor. You must run at least one transaction router on each Siebel Remote server. However, you can run multiple transaction routers on the same Siebel Remote server, or multiple Siebel Remote servers with multiple transaction routers on each.

Siebel Remote enables mobile or remote clients (typically laptop computers) to connect to a Siebel Server and exchange updated data and files, a process known as synchronization. Siebel Remote supports true mobile computing by allowing field personnel to share current information across virtual teams of other mobile and connected users across the enterprise.

The Transaction Processor and Transaction Router components of Siebel Remote, which run on the Siebel Remote server, route the transactions from the master transaction log to the outbox directories of mobile clients.

Outbox directory :- The directory on the machine of the parent node to which you write the extract files. The default is Siebel_Home\DOCKING.

17) dynamic drill down for a default value ? 

Dynamic drilldown enables hyperlink navigation to multiple views from the same hyperlink field, depending on the value of a field in the applet’s current record.

This is useful in the situation where special processing is desired for various types of contacts, opportunities, accounts, and so on. The business component may have a field that indicates a classification, such as the Lead Quality for an opportunity or the primary Industry for an account. The drilldown behaviour can be to check this field in the current record, and navigate to different views for different values found there. Dynamic drilldown behaviour for a hyperlink field (and the corresponding list column or control) is configured with one or more Dynamic Drilldown Destination child object definitions of the Drilldown Object.

As in a static drilldown configuration, the Drilldown Object definition identifies a hyperlink field and a view. These property settings continue to have the same purpose in dynamic drilldown, namely to specify the list column or control that has hyperlink capabilities, and the destination view when the hyperlink is clicked. However, in dynamic drilldown, the Drilldown Object also has Dynamic Drilldown Destination object definitions, each of which points to the type field in the business component, and specifies a value to look for there. When the value in a Dynamic Drilldown Destination is matched, the logic routes to a different Drilldown Object (with typically a different destination view).

18) how do you make a record read only based on field ?

One way of configuring is using BC user property "Field Read only",

19) difference between siebel6 and siebel7 ?

Functional difference

Technical difference

20) what is EAI?

Enterprise Application Integration, or EAI, is the combination of processes, software, standards, and hardware resulting in the seamless integration of two or more enterprise systems allowing them to operate as one. Although EAI is often associated with integrating systems within a business entity, EAI may also refer to the integration of enterprise systems of disparate corporate entities (B2Bi) when the goal is to permit a single business transaction to occur across multiple systems.

EAI involves integration at the following levels:

Business Process Integration (BPI): When integrating business processes, a corporation must define, enable and manage the processes for the exchange of enterprise information among diverse business systems. This allows organizations to streamline operations, reduce costs and improve responsiveness to customer demands.

Application Integration: At this level of integration, the goal is to bring data or a function from one application together with that of another application that together provide near real-time integration. Application Integration is used for, to name a few, B2B integration, implementing customer relationship management (CRM) systems that are integrated with a company's backend applications, web integration, and building Web sites that leverage multiple business systems. Custom integration development may also be necessary, particularly when integrating a legacy application with a newly implemented ERP application.

Data Integration: In order for both Application Integration and Business Process Integration to succeed, the integration of data and database systems must be tackled. Prior to integration, data must be identified (where it is located), cataloged, and a metadata model must be built (a master guide for various data stores). Once these three steps are finished, data can then be shared/distributed across database systems.

Standards of Integration: In order to achieve full Data Integration, standard formats for the data must be selected. Standards of Integration are those that promote the sharing and distribution of information and business data – standards that are at the core of Enterprise Application Integration. These include COM+/DCOM, CORBA, EDI, JavaRMI, and XML.

Platform Integration: To complete the system integration, the underlying architecture, software and hardware, the separate needs of the heterogeneous network must be integrated. Platform Integration deals with the processes and tools that are required to allow these systems to communicate, both optimally and securely, so data can be passed through different applications without difficulty. For example, figuring out a way for an NT machine to pass information reliably to a UNIX machine is a large task for integrating an entire corporate system.

Siebel EAI  is a development environment as well as a framework for building integration between Siebel applications and external applications and technologies. You can use Siebel EAI to build integration between Siebel applications and any

other application in your environment, including:

_ Back office applications

_ E-commerce applications

_ Legacy applications on mainframes or other platforms

_ Middleware technologies on which you have standardised

Siebel also provides predefined connectors to some back-office packaged applications like SAP R/3.

21) Order Processing functionality. How order is processed?

22) How to write a business Service. On which event u use to write a code.

Defines reusable business logic that can be executed within the Object Manager. There are two types of business services: built-in services that are defined in Siebel Tools, and run-time services that are defined in the Siebel client application by administrators. Built-in business services can be based on the CSSService Class (standard business service) or specialised classes (specialised business service). Specialised business services are for Siebel Engineering use only.

BS supports two events

Service_InvokeMethod(methodName) Called when a business service is accessed;

Service_PreInvokeMethod(methodName, Inputs, Outputs) Called before a specialised method is invoked on a

business service. :- developer has more control, can work on input and output arguments.

The InvokeMethod event is called after a specialized or user-defined method called by Service_PreInvokeMethod has completed. This event is generally used less often than Service_PreInvokeMethod, because it is called after any built-in Siebel code may have executed, whereas the PreInvokeMethod is called before the built-in code, and may supplant it if Service_PreInvokeMethod returns CancelOperation.

23) What is Workflow Monitoring Agent? What processes need to start on the server to run the workflow.

Workflow Monitor Agent performs several server processes for monitoring the Siebel database. Workflow Monitor Agent:

--Checks the Escalation Requests table to see when the conditions of a policy are met.

--Monitors all policies within a single group.

--Generates requests for Workflow Action Agent in the action request table (S_ESCL_ACTN_REQ).

--Purges requests from the S_ESCL_REQ table after processing. When a database trigger is activated because a workflow policy condition is met, a record is inserted into the Escalation Request table, S_ESCL_REQ.  Workflow Monitor Agent (Workmon) evaluates the request against the rules set up by the policies in the workflow policy group.

In order for the workflow process to be executed successfully on the server, the following server components must be running:

--Workflow Process Manager

--Server Request Manager

To verify that these processes are running, navigate to Server Administration--Servers--Server Components.

24) What is SRF file? Difference between  exe file & srf file.

siebel.exe :- This is a general-purpose instantiation engine that instantiated and runs objects whose definitions are stored in the repository. The run-time engine reads object definitions at run time and generates “on-the-fly” optimised SQL statements to

the database. Therefore, customers do not need to write SQL code.

SRF file :-  The repository file is a compressed, binary, read-only file that contains the configuration definitions of the objects you create or modify during the configuration process, and that reside in the repository. A single repository file can contain definitions for multiple applications. The definitions (that is, the metadata) that specify a Siebel application reside in the system database. Siebel Tools extracts them from the database in a compilation process and stores them in a compressed format in a binary file for

Faster access by the Siebel executable, which reads them from the repository file, as needed.

25) What is Link & MVL. Difference between Link & MVL

26) How to link Opportunity & Contacts are linked using Link or MVL

A link implements a one-to-many (or master-detail) relationship between business components based on their base tables. It is used to "link" many child records with a single parent record. For example, one Opportunity can have many Contacts linked to it. A link is used to display child records in a separate applet on the Master-Detail view. The child records store the row-id of the parent record in their foreign-key column. That's how the relationship is established.
Whereas, a MVL is a special kind of implementation of a Link. An MVL is used to display and maintain multiple records of data associated with one control or list column in the originating applet. The group of attached detail records is called a multi-value group. The applet displaying such a MVG is called a Multi-Value Group Applet. For example, the Account Form applet has a MVG on Street Address field. When the ellipsis (...) button is clicked the Address MVG applet pops-up. A MVL has a normal link underlying it.

27) Which link is used to connect the Siebel server

28) Why & how Join is used

A Join object definition creates a relationship between a business component and a table other than its base table. The join allows the business component to use columns from that table. The join uses a foreign key in the business component to obtain rows on a one-to-one basis from the joined table, even though the two do not necessarily have a one-to-one relationship.

29) What are the table used to store workflow variables

30) What are the CMM Level Processes

The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.

31) what are Difference types of repository

32) What is diff betn object repository and Repository

The complete set of object definitions defining a Siebel application or suite of applications (such as the Siebel Service or Siebel Applications). It is part of the Siebel client, compiled into the Siebel repository file (the .srf file). The master copy of the repository resides on a server database where multiple developers can access it to make changes and additions. A local

copy resides on a developer’s client machine for development and testing.

33) Explain Siebel server architecture

The Siebel Gateway Server:

--Serves as a single entry point for accessing Siebel Servers

--Provides enhanced scalability, load balancing, and high availability across the Enterprise Server Two primary services that coordinate the Enterprise Server and Siebel Servers operate within the Gateway Server: Name Server and Connection Brokering.

The Name Server provides the persistent backing of Siebel Server configuration information, including:

--Definitions and assignments of component groups and components

--Operational parameters

--Connectivity information

Connection Brokering directs client connection requests to the least-laden Siebel Server operating the desired component, which provides greater scalability and higher availability. Connection Brokering is an optional service of the Gateway Server that uses the Resonate Central Dispatch product to distribute client connection requests across multiple Siebel Servers. Only client connections to the Siebel Object Manager (for thin clients), request processor, and request agent components (for Interactive Assignment) will be distributed by Resonate Central Dispatch.s

Siebel Enterprise Server

The Siebel Enterprise Server is a logical grouping of all Siebel Servers that support the same group of users accessing a common database server. The Enterprise Server can be configured, managed, and monitored as a single logical group, allowing the

Siebel administrator to start, stop, monitor, or set parameters for all Siebel Servers within an enterprise.

Siebel Server

The Siebel Server is the middle-tier platform that supports both back-end and interactive processes for all Siebel application clients. These processes are components within the Siebel Server architecture, and support functions such as:

--Mobile client synchronization

--Operation of business logic for Siebel Thin Clients, as well as connectivity and access to the database server and file system

--Integration with legacy or third-party data

--Automatic assignment of new accounts, opportunities, service requests, and other records

--Workflow management

34) How to create MVG ? what is MVL

see above

35) How to make field read only during run time?

36) How to configure 1:M relationship during EIM load process?

37) What are business components user properties ?

These provides initial values for the properties of the business service. This can be used to communicate a property value to C++ code or scripts that implement the business service behaviour. The values of these properties can be changed at configuration time or run time. Run-time access is via the GetProperty and SetProperty functions. Business Service User Prop properties are listed As follows

Name:- Required :-Name of the business service user prop.

Value:- Required:- Value of user property specified by the Name attribute.

38) What are the different events for Business component?

BusComp_Associate() Event

The Associate() event is called after a record is added to a business component to

create an association. For details, see the Siebel Object Interfaces Reference.

BusComp_ChangeRecord() Event

The ChangeRecord() event is called after a record becomes the current row in the

business component. For details, see the Siebel Object Interfaces Reference.

BusComp_CopyRecord() Event

The CopyRecord() event is called after a row has been copied in the business

component and that row has been made active. For details, see the Siebel Object

Interfaces Reference.

BusComp_DeleteRecord() Event

The DeleteRecord() event is called after a row is deleted. The current context is a

different row (the Fields of the just-deleted row are no longer available). For details,

see the Siebel Object Interfaces Reference.

BusComp_InvokeMethodii() Event

The InvokeMethod() event is called when the InvokeMethod method is called on a

business component. For details, see the Siebel Object Interfaces Reference.

BusComp_NewRecord() Event

The NewiRecordi() event is called after a new row has been created in the business

component and that row has been made active. The event may be used to set up

default values for Fields. For details, see the Siebel Object Interfaces Reference.

BusComp_PreAssociate() Event

The PreAssociate() event is called before a record is added to a business component

to create an association. The semantics are the same as BusComp_PreNewRecord.

For details, see the Siebel Object Interfaces Reference.

BusComp_PreCopyRecord() Event

The PreCopyRecord() event is called before a new row is copied in the business

component. The event may be used to perform precopy validation. For details, see

the Siebel Object Interfaces Reference.

BusComp_PreDeleteRecordii() Event

The PreDeleteRecord event is called before a row is deleted in the business

component. The event may be used to prevent the deletion or to perform any

actions in which you need access to the record that is to be deleted. For details, see

the Siebel Object Interfaces Reference.

BusComp_PreGetFieldValue() Event

The PreGetFieldValue() event is called when the value of a business component

field is accessed. For details, see the Siebel Object Interfaces Reference.

BusComp_PreInvokeMethod() Event

The PreInvokeMethod() event is called before a specialized method is invoked on

the business component. For details, see the Siebel Object Interfaces Reference.

BusComp_PreNewRecord() Event

The PreNewRecord event is called before a new row is created in the business

component. The event may be used to perform pre insert validation. For details, see

the Siebel Object Interfaces Reference.

BusComp_PreQueryi() Event

The PreQuery() event is called before query execution. For details, see the Siebel

Object Interfaces Reference.

BusComp_PreSetFieldValue() Event

The PreSetFieldValue() event is called before a value is pushed down into the

business component from the user interface or through a call to SetFieldValue. For

details, see the Siebel Object Interfaces Reference.

BusComp_PreWriteRecordi() Event

The PreWriteRecord() event is called before a row is written out to the database.

The event may perform any final validation necessary before the actual save occurs.

For details, see the Siebel Object Interfaces Reference.

BusComp_Query() Event

The Query event is called just after the query is complete and all the rows have

been retrieved, but before the rows are actually displayed. For details, see the Siebel

Object Interfaces Reference.

BusComp_SetFieldValue() Event

The SetFieldValue() event is called when a value is pushed down into the business

component from the user interface or through a call to SetFieldValue. For details,

see the Siebel Object Interfaces Reference.

BusComp_WriteRecord() Event

The WriteRecord event is called after a row is written out to the database. For

details, see the Siebel Object Interfaces Reference.

39) What is difference between setFieldValue & preSetFieldValue

setFieldValue() is a method  (is also an event) assigns the new value to the named field for the current row of the business component. The preSetFieldValue() event is called before a value is pushed down into the business component from the user interface or through a call to setFieldValue.

40) How to make a field read only of BC.

41) How to set primary record in MVG

Primary records are identified by the primary field which is specified in the Primary Field Id property in the multi-value link. The multi-value link object definition is a child of the originating business component. It identifies the link that provides the field values from the multi-value group business component. The multi-value link in the originating or joined (in the case of an indirect multi-value link) business component has the following important properties:

Primary Id Field property. Identifies the foreign key field in the originating, or joined, business component. The foreign key field identifies the primary record in the set of records for one multi-value group (in the multi-value group business component). The primary record is the one that displays in the originating or employing business component.

42) What are static and dynamic picklist?

Static pick list values are populated from LOV administrative view while dynamic picklist values are populated from Business component

45)errors in workflow and how do you invoke workflow?

Stop Item :-Represents an end to a process and the presentation of an error to the user. A process can have one or more stop steps. Exceptions Item :-Represents a deviation from normal processing. An exception can be a system error or a user-defined error. A process can have one or more exception branches. Process Properties, Error Code and Error Message are automatically populated when an error occurs. Siebel Operation Object Id is automatically populated when a Siebel Operation step is executed.

Following are the way to run  Workflow Process

Invoking from a Workflow Policy, Invoking from a Script , Running a Workflow Process on the Server, Running a Workflow Process on the Object Manger, Running a Workflow Process in Batch

46)how will you make applet read only?(not sure)

Set properties no delete, no insert, no merge, no update to true

47)can you modify applet?

Yes is possible to change the layout and object settings of applet.

48)can we do sorting on calculated field?

Sort Ascending and Sort Descending icon buttons are not displayed at the top of every list applet column. The behaviour that controls which list column will have sort icon buttons is hard coded into the Siebel Web Engine and will depend on the  configuration of fields that are being displayed. Calculated fields, or fields mapped to columns with Physical Type property of "Long" cannot be sorted. In addition, it is not possible to sort multi-value fields that do not use a primary join; that is when the Use Primary Join property of the multi-value link is set to "FALSE". In order for the user to be able to sort multi-value fields it is necessary for the multi-value link to use a primary join and the Primary ID Field and Auto Primary properties should be correctly populated. Such a configuration will result in the Row_ID of the primary child record to be stored in the parent business component record.

49) Can we make calculated how the conditions are applied? How to enable calculated field ?

50) WHAT IS the relationship between position and responsibility?

Both are use to restrict unauthorised data access. One of the access control mechanism, Visibility, controls user access to records within specific views based on record ownership by teams or individuals.

User access control is based on the user’s responsibilities and positions, which are both obtained using the user’s logon ID. Typically users have one of each, although they may have multiple responsibilities or multiple positions. A responsibility is a

class of users who require access to the same set of application features, specifically views. A position is a job title within the organization, a box in the organisation's hierarchy chart with a reporting relationship to a supervisory position. Positions provide most of the basis for control of record access. Records are assigned to positions, or teams of positions, rather than to individuals through their logon ID’s. This is because the position in the organization is typically more stable than the individual’s assignment to that position.

51) How will you create virtual business component?

Virtual business components enable you to: Represent external data (for example, data in an SAP R/3 database) as a virtual

business component within a Siebel application—the business component configuration specifies the DLL to use to access the data. Also it allows to use business services to transfer data.

Additional information about virtual business components:

_ Insert, delete, query, and update operations are supported.

_ Applets can be based on virtual business components.

_ You can access virtual business components via object interfaces.

_ All business component events are available for scripting.

_ Virtual business components cannot be docked.

_ Virtual business components can be used as stand-alone or children business components in a business object.

To create a new virtual business component

1 Create a new record in the Business Component list applet in Siebel Tools. 2 Name the business component.

3 Choose a locked project. 4 Set the Class to the CSSBCVExtern class. This class provides the virtual business component functionality.

52)can we create BC with view(oracle)?

53) What client u use in your project?

Thick/Thin/Mobile

54) what is the diff betn thin client & dedicated client

Siebel thin client is different from Siebel dedicated client, which is the default Siebel client for Siebel eBusiness Applications. In Siebel dedicated and mobile clients  all layers of the Siebel eBusiness Applications architecture, except for the database, reside on the user’s personal computer. For mobile client users, a local database is stored on each mobile machine.

With two exceptions, thin clients run inside a standard Web browser from the client PC and do not store data locally. Thin client connects directly to the Gateway Server only, not to any other server. The Siebel Server executes all business logic for thin clients. There are three types of thin clients: Siebel Java Thin Client, Siebel Thin Client for Windows, and Siebel HTML Thin Client.