DOES YOUR ORGANIZATION

1. Position your organization
right on the money
2. Enable more
sales calls
3. Enable more effective
sales calls
4. Perform deeper, broader
research and make better
decisions faster
5. Leverage existing
resources
6. Revisit expenditures
7. Turn your vendors
into partners

LISTEN BEAUTIFUL TELUGU SONGS

Hi,

listen beautiful telugu songs from this site

http://www.raaga.com/listen/?5091964

This session explaing about the" APPLET TOGGLE" in the siebel application.

ABSTRACT

As companies work towards optimizing revenue, profitability and providing customer satisfaction, many companies are beginning to look towards Customer Relationship Management (CRM) software, by using SIEBEL application as a strategy to reach these goals. This paper describes the elements related to Toggle Applet when developing a successful CRM solution in SIEBEL application.

INTRODUCTION:-

According to Siebel documentation

‘An applet is a data entry form, composed of controls, that occupies some portion of the Siebel application user interface. An applet can be configured to allow data entry, provide a table of data rows, or display business graphics, or a navigation tree. It provides viewing, entry, modification, and navigation capabilities for data in one business component.’

There are various types of applets in the Siebel application.

DEFINITION:-

Applet toggles allow users to switch back and forth between different applets within the same view. This is useful when you want to display different types of data or present the same data in a different way’.

Toggle applets are not special applets ,these applets are containing special behavior of "DRILL DOWN APPLETS".

To understand Toggle Applets , we have put two applets named Applet S_ORG_EXT and Applet S_OPTY on top of each other and we configure them in such a way that only one we can see in view . let us examine the background ....

TYPES OF APPLETS:-

Generally , there are two types of applets

A) STATIC TOGGLE APPLET

B) DYNAMIC TOGGLE APPLET

STATIC TOGGLE APPLET:- Allow users to toggle between applets by selecting the name of the applet from the Show drop-down list.

DYNAMIC TOGGLE APPLET:- Automatically toggles between applets based on the value of a field in a parent applet.

PURPOSE :-

The main purpose of toggle applet is to provide getting easy to user of the application. For example ,the company offers 4 different products to its customers. Each product has different set of fields that should be filled in order to ascertain the correct price. Now, there are two things we can do. there are two ways to get the solution. First one, Expose all the fields in one applet and let user fill correct fields according to product he has chosen. second configure the application , four different applets with specific fields for each product and create toggle applet ,user should select among the four applets.

USES:-

A) The end user can understand in an easy way .

B) space in a view should be save.

DRABACKS:-

A) The performance should be check in each and every time, in all the applets,when they loaded.

B) it should not have clear at a time .

KEY POINTS TO REMEMBER

While preparing this application every one should take care,

according to siebel documentation

'For applets involved in a toggle cycle the search spec on the form applet in the view will be applied first.Therefore, to apply a search spec on a list applet in a toggle cycle, you also need to add the search spec for the form applet.

■ Dynamic toggle applets must be based on the same business component.

■ Static toggle applets do not have to be based on the same business component.

■ You cannot configure more than one applet toggle in a view.

Conclusion:-

The TOGGLE APPLET is having the behavior of drilldown applet. while configuring this application you should follow above mentioned precautions. The performance of TOGGLE APPLET is very low, you should check each and every time all the applets when you given the values. TOGGLE APPLET , is the user friendly and it useful to easy understanding.

Thank You,

This session explains how to configure a join in Siebel Tools and set up in the application

OBJECTIVES · Introduction about data, table and various types tables · What is meant by Join? · Principle behind the join · What are the various types of Joins · How join is constructed? · Join architecture? How to configure the Join

ABOUT THIS SESSION -

This session explains how to configure a join in Siebel Tools and set up in the application development environment.

OBJECTIVES

• Introduction about data, table and various types tables

• What is meant by Join?

• Principle behind the join

• What are the various types of Joins

• How join is constructed?

• Join architecture?

• How to configure the Join?

INTRODUCTION

All the organizations need to collect , process and store data for its human, financial material, insurance, order management ,material management, pharmaceuticals needs. To represents this information one can use DBMS modeling. In a DBMS a group of similar information or data which is of interest to an organization is called an ENTITY. Entity information is stored in an object called TABLE. Table contains rows and columns.

Table

A table object definition is the direct representation of a database table in DBMS. It has a Column and Index child object definitions. SIEBEL is the leading provider of Customer Relationship Management (CRM) software ...In Siebel , a set of standard tables is provided with Siebel applications for installation . these provide data storage for all of the features included in the standard Siebel applications. Standard tables and their table object definitions generally are of the following types. - Standard tables and their table object definitions are -

a) Data table

b) IntersectionTables

c)Extension table

d) interface tables.

Base table Means

It identifies the base table if the table in the object definition is an extension table. If the table in the object definition is a base table, this property is a Blank . An extension table always identifies a base table.

Data table Means

It compraises bulk data of the table object definitions in Siebel applications. The column in this table are provide the data for fields. It may primary source of data for that BC.

1. It compares most of the tables in Siebel applications.

2. They serve as a base table for BC.

3. Their column provide the data for fields.

Data tables are public or private.

JOINS

In some situations , you may find necessary for getting the information from two separate tables. join is one of the method to get the information . In this case i.e in Siebel a join object definition a relationship between a Business component and a table other than its base table. from database background knows, "Cardinality" between two tables can be of four types : a) One to One b) One to Many c) Many to One d) Many to Many.

Join in Siebel is, "When you have "One" on the right side of the cardinality, there you need to implement Join". That means, "One to One" and "Many to One" corresponds to the Join,

o A Join exist between a Business Component & a table

o Via Join system fetches a single record

o While implementing Join, we can use the "Join Constraint" to specify the condition on the child entity.

JOIN=BUSINESS COMPONENT+A TABLE

Principle

Fields in the business component can represents column from the joined table. And a joined field in the business component represents column from a table other than business component ‘s base table. A business component whose base table is a detail table in a master-detail relationship can include columns from the master table as fields. This is the principle behind a join.

WHAT ARE THE VARIOUS TYPES OF JOINS?

There are two type of commonly used joins

>Implicit Join

>Explicit Join

Implicit Join Implicit Join are those which are already define in Siebel and which are internally use by the Siebel to pull the values from the other than base table.

Example

join between base table and extension table like S_OPTY and S_OPTY_X and join between S_PARTY and S_ORG_EXT .

Explicit Joins Explicit Joints are those which are define by the developer to create the relationship between two tables.

Implied Joins

Underlying the one-to-one extension table’s relationships with the base table and business component I s a set of hidden relationships called an implied or implicit join .

The implied join makes the extension table rows available on a one-to-one basis to the business component that uses the extension table.

• Every extension table has an implied join with the business component it extends.

• This join always has the name of the extension table.

• An implied join is different from joins defined as object definitions.

• Data can be updated through an implied join. Data can be displayed only through other joins.

• This update capability is important for extension table functionality.

HOW JOIN IS CONSTRUCTED

Busienss component

The business componeNt is the parent object definition of the join. Because of the join, fields in the business component (called joined fields) can represent columns from the joined table.

Joined field

A joined field in the business component represents a column from a table other than the business component’s base table. Therefore, a joined field must obtain its values through a join. A joined field has the name of the join in its Join property.

NOTE:-When creating a joined field in a business component, you can change the Type property from the default DTYPE_TEXT to a more appropriate type.

Join object type.

Join is a child object type of the Business Component object type. The Join object definition uniquely identifies a join relationship for the parent business component and provides the name of the destination (joined)table. The join object definition identifies the joined table in the Table property.

The name of the base table is already known to the business component. Typically, a join object definition is given the same name as the joined table.

Join Specification object type.

The join specification object definition is a child of the join object definition. It identifies the foreign key field in the business component and the primary key column in the joined table (that the foreign key points to).

Join Constraints.

A join constraint is a constant-valued search spec applied to a column during a join. It is for use with outer joins. Foreign key (source) field and foreign key column. The foreign key field is identified in the Source Field property of the join specification. It represents a foreign key column in the base table, pointing to rows in a particular table used in joins.

For example, in the Contact business component, the foreign key field to the join on accounts data is the Account Id field, which represents the PR_DEPT_OU_ID column in the base table.

Joined table.

The joined table is the master table in the master-detail relationship. It provides columns to the business component through the join. The joined table is identified in the Table property of the Join object definition. Primary key (destination) column. The join specification identifies the primary key column in the joined table (in the Destination Column property).

Every standard table in standard Siebel applications has a ROW_ID column that uniquely identifies rows in the table. ROW_ID is the destination in most joins.

Mapped column.

Columns in the joined table are available for use in fields in the business component.

NOTE:-

1.In rare circumstances, there can be multiple join specifications in a single Join.

2. Set the Outer Join Flag to TRUE if you want to retrieve all the records in the business component even when the joined fields are empty.

3. When configuring a recursive or self join, the Alias name of the joins must be different than the Table Name.

Using the same name will result in the following error message: “Table ‘T1’ requires a unique correlation name.” This error is often due to a faulty recursive or self join definition.

How to configure a join

You have to follow the following five steps to have joined field on UI in Siebel

1.Identify the column to be used as Foreign key.

2. Configure field which will store the primary key of join table.

3. Configure a join.

4. Configure join specification.

5. Add a field which will be used at Applet.

EXAMPLE Suppose we want to have Opportunity Name on the Quote Applet.

Here is a step by step procedure with screen shots explaining how to do that.

1. Identification of Column to act as foreign key.

To configure a Join, first of all we have to find out a column in the base table where we can store primary key say (ROW_ID) of opportunity in quote which will become the basis of join.

If there is no column vacant in the base table we can use extension table for that base table e.g S_DOC_QUOTE_X for the S_DOC_QUOTE. Note: Make sure that the column you choose is not being used by any other BC or any other field of same BC.

2. Configure Field in Business Component

• Go to Business Component > Field

• Create a new record

• Enter the name of the field.

• Enter extension table name in Join field

if the column you identified belongs to extension table otherwise go to step 5

• Select the Column identified in column Field.

Note: The column which you have selected must have physical Type varchar. Our Foreign key is now ready for use.

Now we have to configure a joined Field which will use this foreign key

3. Configure/Create a Join

• Go to Business Component > Join

• Create new record.

• Give name of the table with which you want create join ( S_OPTY in our case)

• Give Name in Alias (New in our case).

• Check the Outer join Flag (Very Important).

Go to Object List Explorer (OBLE) on the left hand side and click + sign beside join there will be two options Join Specification and Join Constraints

4. Configure Join Specification

• Create New Record.

• Give Name in the Name field.

• Destination Column is given by default when insert a new record. You can change it if you want to.

• In the Source field give the name of the source field (OptyID) which you have configured earlier to be used as Foreign Key.

5. Configure the field (Opportunity Name) which you want to display on the User Interface.

• Go to Business Component > Field

• Insert New Record

• Give Name in the Name Field

• Enter the Join Alias which you have given for the join you created.

• Select the Name (for Opportunity Name) in the column field.

Column name here represent the data that you want to pull from opportunity.

6. Configure the Control in the Applet (UI).

• Go to Applet > Control (if Form Applet)

• Go to Applet > List > List Column (if List Applet)

• Create New Record.

• Enter the Name

• Enter the name you want to display on UI in Caption Override Field

• Enter the Name of the field you created in Field column

Don’t forget to map this field in Applet.

Right Click on the corresponding Applet and map it.

Now compile the entire project which you have made the changes and you will be able to see this joined field in the Quote Applet

When you see this field in User Interface it will be read only because when the data is pull from the join table it is only read only,

to make it editable you have configure Pick Applet on this field.

How To Create a Join to a Table

Through Another Table Lets say that you want to create a join field "Country" on the Service Request business component (based on the S_SRV_REQ table) where the "Country" field exists on table S_ADDR_ORG

but there is no direct foreign key relationship between S_SRV_REQ and S_ADDR_ORG to create the join.

The relationship is as such: (Service Request BC) S_SRV_REQ.REQUESTOR_ID -> S_ORG_EXT.ROW_ID -> S_ADDR_ORG.OU_ID (Address table with Country column) Therefore the Service Request is joined to S_ORG_EXT directly through foreign key REQUESTOR_ID and then the "Requestor" (S_ORG_EXT) is joined to the Address (S_ADDR_ORG).

It is straight forward to create business component joined fields that involve more than one tables as in the above case.

You need to create the joined fields one by one.

For the above example if you wanted to create a joined field for S_ADDR_ORG.COUNTRY on the Service Request BC you would firstly need to create a joined field to S_ORG_EXT.ROW_ID.

Then you would create a joined field using the joined field (S_ORG_EXT.ROW_ID) as the source field for the S_ADDR_ORG.COUNTRY joined field.

1. In Siebel Tools, Service Request BC > Join > Create a new record with:

Table: S_ORG_EXT

Alias: Requestor

Outer Join Flag: Y

Then in Join Specification for that Join:

Name: Requestor

Destination Column: ROW_ID

Source Field: Requestor Id

2. Service Request BC > Field > Create a new field with:

Name: Requestor Joined Id

Join: Requestor

Column: ROW_ID

3. Service Request BC > Join > Create a new record with:

Table: S_ADDR_ORG

Alias: Requestor Address

Outer Join Flag: Y

Then in Join Specification for that Join:

Name: Requestor Address

Destination Column: OU_ID

Source Field: Requestor Joined Id 4.

Now create the joined field for Country.

Service Request BC > Field > Create a new field with:

Name: Requestor Country J

oin: Requestor Address

Column: COUNTRY

You may now be aware that I did not need to create two joins I could have joined S_SRV_REQ.REQUESTOR_ID to S_ADDR_ORG.OU_ID

however I wanted to show the fact that you could join through multiple tables as an example.

NEXT

What is complex join?

Complex joins can have conditional mappings like >,=,NOT,AND,etc

Difference with Foreign key Primary Key join?

Complex joins are joins which have following diffrences from a PK-FK joins.

# Complex joins can have conditional mappings like >,=,NOT, AND, etc apart from '=' whereas the PK-FK joins are always '='.

# PK-FK joins are always (1-N), whereas complex joins can have (1 - 0,1) and (0,1 - N) kind of relationships.

Remember

Join field can be updated by configuring either dynamic pick list or MVG Applet on the field.

Generally join fields are read only. can be edited by dynamic picklist. Explicitly joined fields cannot be edited.

They are read only. In case of dynmaic picklist ;

it is the Foreign key id used in Join Definition gets edited and accordingly we see joined value.

This is about join.

Thank You,

Suggestions are most welcome:

Reference::

1) Siebel tools reference

2) From the various Siebel websites.

INTRODUCTION TO SIEBEL PART 1

This session briefly explains to
1) WHAT IS MEANT BY SIEBEL TOOLS
2) ABOUT THE OBJECT LAYERS
3) ABOUT THE SIEBEL WEB ENGINE
4) OBJECT MANAGER AND OBJECT TYPES AND PROPERTIES

hat is meant by Siebel tools:-

Siebel Tools is an integrated environment for configuring all aspects of a Siebel application so that a single configuration can be

(1) Deployed across HTML clients ,

(2) Used to support multiple Siebel applications and languages,

(3) Easily maintained

(4) Automatically upgraded to future Siebel product releases

Siebel Tools is a powerful object-oriented, Web application development environment designed to meet the customization needs of sales, marketing and customer service information system Deployments.

Siebel Tools is not a programming environment—it is a declarative application configuration tool.

Standard Siebel applications provide a core set of object definitions that one can use as a basis for their tailored application. Using Siebel Tools and other configuration tools that are part of a Siebel solution, Siebel application developers, system administrators, and database administrators can customize a standard Siebel application without modifying source code or SQL. Some of the configuration tools are accessed through the Siebel applications. Siebel Tools, however, is a separate product with its own user interface.

Navigation in Siebel Tools is done mainly in two windows:

-View-Site map-Group administration-Call center application.

(1) Object Explorer window.

(2) Object List Editor window

(1) Object Explorer window:-. A hierarchical tree-structure user interface (similar to that of the Microsoft Windows Explorer) to Allow you to browse the object types that are stored in the Siebel Repository.

(2) Object List Editor window:- Shows the detail about individual objects in the Siebel repository.Now We Know what is meant by

a) Object definition

b) Object Properties

c) Object type

Object Definition:- a user interface, an abstract data representation, or a direct database representation or construct.

An Object definition is what is on the Object list (top right).

"Account List Applet is an Object definition of Object type Applet"

When you define an Applet Object definition,

it means that you create a new applet on the Object list applet.

Object Properties:- An object definition consists of properties . For example:- the properties of a database column include its name,

data type, length, and so on.

Object type:- It is a named structure from which object definitions of that type can be created .

For example:- the account, opportunity and contact business components are implemented

as object definitions of the business component object type. "Account List Applet is an

Object definition of Object type Applet" Relation ship between object types is parent and child.

Object Layers and Hierarchy:(architecture layers of object definitions)

DBMS : It is complete third party data base vendor.

DATA OBJECT LAYER:- it consists of data object definitions that directly map the data structures from the underlying relational database into Siebel applications, providing access to those structures by object definitions in the Business Object layer. In the data object layer we can define table ,column etc.

BUSINESS OBJECT LAYER:- Business object definitions that are built on data object definitions and selectively combines and associate data object definitions into logical data constructs that are useful for application design. In this we can B.C , B.O.

USER INTERFACE OBJECT LAYER:-it consists of user interface object definitions that define the visual interface that the user sees and interacts with in a web browser. In the logical user interface object layer consists of applets, views , screens . We can see the data and validating the data , editing the data by means of user interface object definitions.

PHYSICAL USER INTERFACE LAYER:- it consists of the physical filed, templates, stylesheets, and other file based metadata(repository objects) In this templates ,files, style sheets, other files such as repository objects. Step Type Definition What it reprasents

1. DBMS It is complete third party data base vendor Third party data base vendor

2. DATA OBJECT LAYER We can define table ,column and Index. Siebel Application

3. BUSINESS OBJECT LAYER We can Define B.C , B.O. Siebel Application

4. LOGICAL USER INTERFACE OBJECT LAYER We can Define applets, views , screens. We can see the data and validating the data , editing the data by means of user interface object definitions Siebel Application

5. PHYSICAL USER INTERFACE LAYER Templates ,files, style sheets, other files such as repository objects Siebel Application (This the Siebel tools architecture)

DATA OBJECT LAYER

Data Object Layer:- it is a logical representation of the underlying physical database and are independent of the installed DBMS.

Data Object Types:- a) Table b) Column c) Index

Table:- A table object definition is the direct representation of a database table in DBMS. It has a Column and Index child object definitions.

Column:- A column object definition represents one column in the database table. And It is child object definition of the Table object definition.

Note:- Each column in the table has a corresponding column object definition.

Index:- Each index object definition Identifies a physical index file in the DBMS.

Table:- Standard tables and their table object definitions are -

a) Data table

b) IntersectionTables

c)Extension table

d) interface tables

Data Table:- the data tables comprise the bulk of the table object definitions in the Siebel applications. Columns in the data tables provide the data for fields. It is a base table to the Business Component.

Intersection Table:- It is happens Between two data tables and should have Many –to-Many Relationship or one-to-many relation ship.

Extension Table:- It means adding an additional to the data table . It cannot be directly added to a data table.

NOTE:- once it is populated with data extension column will not be possible.

It allows you to provide additional columns for use as field in a business component with out violating DBMS.

interface Table:- it is intermediate database tables between the Siebel application database and other databases.

The columns in standard tables are of the

a) Data column

b) Extension Column

c) System Column

Data Column:- the data columns are part of the original set of columns implemented in the standard Siebel applications.

Extension column:- it is a column that is not used by standard Siebel applications.

It is used for reconfigured applications.

There are three kinds of extension columns:-

i) standard Extension columns

ii) Customs Extension Columns in an Extension or intersection table.

iii) Customs Extension Columns in a Base Table.

i) standard Extension columns:- standard extension columns included in the standard extension tables .they named ATTRIB_nn (where ‘ nn ‘ is a value between 01 and 47)

ii) Customs Extension Columns in an Extension or intersection table:-these are the columns added to an extension or intersection table.

iii) Customs Extension Columns in a Base Table:-these are the columns added to a base table of an extension table.

Their name have the X_prefix.

System Column:- in every table some standard system columns are ROW_ID, CREATED, and CREATED_BY. It is useful for the construction of joins. Certain system of the systems columns in interface tables.

BUSINESS OBJECT LAYER

The major object types in the Business Objects layer are:

a) Business Component

b) Business Object.

a) Business Component :- it means One main table (Data object layer) + Fields (Business component) maps to column (Main table)

It also include data from related tables.

Note: grouping of data can be achieved by

1) referencing an extension table

2) Explicit join of two tables

3) link

b) Business Object :- it is a collection of related business components.

Object Types:

1) B.C:- it is a logical entity that associates columns from one or more tables into a single structure. BC provide a layer of wrapping over tables, causing applets to reference BC rather than the underlying tables.

2) Field:- it defines associates a column to a BC and we can modify column names with meaningful names.

3) BO:- It is a set of interrelated business components using links. the links provide the one-to-many relationships.

4) BO Component:- it is used to include a BC and ,a Link in Business object.

5) LINK:- It is implements a one-to-many relationship between business components.

6) Multi-value Link:-it is a user maintainable list of detail records associated with a master record.

7) Join:- it defines creates a relationship between a business component and a table(it is not a business component base table.

8) Join specification:- it is a child object type of join that provides details about how the join is implemented with in the BC.

9) Business Service:- it is a reusable module containing a set of methods.

LOGICAL USER INTERFACE OBJECT LAYER

The user interface object layer is insulated from the data object layer and the underlying database by the business object layer.

It consists of user interface object definitions that determine the visual interface that the user

1) sees and interacts with in a web browser.

2) Viewing and modification by means of user interface object definitions.

3) The applet user interface object type implements application units consisting of Controls, etc.

4) other user interface object types control toolbar and menu implementation and the visual grouping of applets on screen.

The user interface defines the visuals elements with which users interact-

a) lay-out of applets and views

b) Navigation

c) Buttons and check boxes i.e user interface controls.

Applets :- It allows access to the data of a single BC for viewing ,editing and modifying in the BC.

Note: all data in an applet must be part of the BC that calls it.

Views:- It presents one or more applets together at one time in a predefined visual arrangement and logical data relationship.

Note:- a specific view is selected by name from a combination of menus or tab symbols.

Each applet in a view must map to a BC in that BO.

The BC that are required to be included in each view are………

a) based on BO ,all BC. to which applets in that view are mapped.

b) Any BC whose data is exported in a report from a view based on the BO.

Screens:- it is a collection of related view.

Note:- all views in a screen map to the same BO-

Application:- it is collection of screens.

Object Types

a) application:-it is collection of screens.

b) page tab:- it is associates a screen to the page tab’s parent application object definition and includes

c) Screen Menu item it define associates a screen to the application and includes the screen as a menu item .

d) screen it is a logical collection views.

e) screen view it is associates a view with the screen view’s parent screen object definition.

f) view it is a collection of applets which appear screen at the same time.

g) applet an applet is a form ,composed of controls, that occupies a portion of the Siebel application window.

h)control a control usually either exposes data from one field in the BC or invokes programming logic .

i)List a list object definition specifies property values that pertain ot the entire scrolling list table and provides a parent object definition for a set of list columns.

j) list column a list column object definition corresponds to one column in the scrolling list table in a list applet, and to onefield in the BC k)webtemplate,

applet web template,

view web template.

It identify external HTML files that define the layout and Siebel web engine interactions for an applet or view.

Applet web emplate item

it defines a control, list item, or special web control in the web implementation of an applet.

View web Template item

it defines the inclusion of an applet in the web implementation of a view.

PHYSICAL USER INTERFACE LAYER

It consists of the physical files, templates, Siebel tags , style sheets and other file based metadata that control of user interface.

Applet web template ,

applet web template item--

View web template,

view web template item These are the part of the UI layer.

Template files :- it defines the layout and formatting of elements of the user interface.

Tags:- these are special tags you insert into template files. It specify how Siebel objects defined in the repository.

(NOTE:-we can use siebel tags to map objects into a HTML physical layout.)

CSS:- these are external style sheet documents to define how HTML or XML elements and their contents should appear in a web document.

(NOTE:- CSS provide rules for resolving conflicts in HTMLOR XML)

these rules consists of two main parts …..

a) selector

b) declaration Declaration has two parts

a) property

b) value.

Siebel applications are implemented on one or more servers using three major components:-

The object manager,

the siebel web engine,

and the data manager:

Object manager:- object definitions at all three levels of the object layer hierarchy

- web interface definitions

- business object definitions

- data object definitions these are processed in the object manager.

During the run time objects

- business object layer objects are instantiated there directly.

- Web interface objects are instantiated in the Siebel web engine,

- Data objects are instantiated in the data manager.

Siebel Web Engine:- this is also called SWE.

1)The user interface in Siebel application is fenerated as HTML pages on the server And is passed to an unmodified web browser through HTTP.

The Siebel web engine makes possible the deployment of these applications.

2)for the user wants to editing and viewing the data the object manager providing this facility through SWE.

Data Manager:- it is a facility inside the object manager that issues SQL queries in response to object manager requests and passes back database result sets to the object manager.

Important Note:- the data manager is composed of one connector DLL for each type of data base connection supported by the system.

The object manager dynamically loads the appropriate DLL Based upon the required data source.

Important note:- a Siebel plug-in runs on the web server, and interfaces with the Siebel web engine service in the object manager. Most of the work takes place in the Siebel web engine(SWE);

the web server plug-in mostly maintains the session and functions as a communication intermediary.

Network communication between the web server plug-in and the object manager is through SISNAPI. a TCP/IP

–based Siebel communication protocol that provides a security and compression mechanism.

High Interactivity

:- It allows application developers to use scripting to simulate windows client behavior in the web environment.

High interactivity is automatically switched on when the high inter activity attribute in the Siebel application configuration(.cfg) file is set TRUE.

To perform this operation ,the browser used to access the application must support a certain set of capabilities, including support for javascript and java applets or Active X.

Note:-Employee applications use high interactivity by default.

Note:- the high interacitivity attribute should be set to TRUEFor all employees applications.Siebel sales, Siebel call center application, Siebel service, Siebel marketing.—also.

High interactivity is not supported in customer applications.

High interactivity is enabled through two methods ;-

a) updating the application configuration(.cfg) file.

b) applet class definitions

a) updating the application configuration(.cfg) file:- in the SWE section in the .cfg, add the parameter High interactivity with value= TRUE: (SWE) High interactivity=TRUE.

View lay out caching

the view cache is implemented as an LRU cache. The cache contains the layouts of views that you have visited . when the view cache is full, the first view you visited is removed from the cache.

The size of the view cache is controlled by a user preference, described in the following procedure.

To set the size of the view cache

1 from the application-level menu, choose view>site map>user preference>Behaviour.

2 in the view cache size field, select a value from the drop-down list.

NOTE:-The default value for this field is 10. setting this field to 1 will turn off view caching.

Setting this field to greater than 10 can cause some degradation in performance. Setting this field to 20 will produce times which are approximately the same as when there no view caching. In order for a view to be available for caching, all of the applets in the view must have class objects with values of 2 or 4.( available for caching). Only applets that support high interactivity are available for view layout caching.

Disabling view layout caching:-

we can disable view layout caching for an application by changing the parameter “ enable view cache” to FALSE under the Siebel web engine (SWE) section in the configuration (.cfg) file used by the application. (SWE) Enable view cache=FALSE.

Remaining in part-2

white paper on CRM

This session briefly explains about the CRM.
A) INTRODUCTION
B) WHAT IS MEANT BY CUSTOMER RELATION SHIP MANAGEMENT
C) WHY PRESENT BUSINESS SYSTEM NEEDS CRM
D) BRIEFLY EXPLAINATION ABOUT HOW 'CRM'TECHNOLOGY HELPFUL
E) USES
F) CONCLUSION

INTRODUCTION:-

Today, Massive development in the technology and transformation producers changed from traditional marketing to modern marketing. Modern trends in the marketing calls for more than developing a product, pricing it, promoting it and making it accessible to target customers.

a) Now a days every producer building trust, it contains value added relationship with the customers to win their needs and wants.

b) Now a days, The new age marketing aims at winning customers for ever, where companies greet the customers, create products to suit their needs, work hard to develop life time customers through the principles of customer delight, approval and enthusiasm.

MEANING:- Customer relationship management means, The process of developing a cooperative and collaborative relationship between the buyers and sellers is called customer relationship management shortly called CRM. It aims mainly.

CRM is a new technique in the marketing process where the marketer tries to develop long term relationship with the customers and create loyalty to the manufacturers. Now a days, the customers are becoming demanding, dominant and selective. In fact, rapid change is taking place in the perceptions and the expectations of the customers. with the availability of Insurance services to the customers at their door steps through the help of technology.

HOW TECHNOLOGY HELPFUL "Change" is a continuous process in any business is no exception to this natural law. This is inevitable due to the implementation of the financial sector reforms and policies in the country. The main objective of any business sector reforms is to promote an efficient, competitive and diversified system is required . Past decade onwards The changes have forced the in any business is to adjust the product mix to effect the rapid changes in their process to remain competitive environment. The advent of technology both in terms of computers and communications has drastically altered the methodology of business. In the business sector, the technology has opened new vistas and in turn has brought new possibilities for doing the same work differently and in a most cost-effective manner. Technology helps to provide information round the clock

USES

CRM software provides user friendly methods especially for sales and marketing people that enables the maintains the customers records and products information.

Records Maintenance :- One of the most important aspects of any business is its customers and keeping detailed and accessible records on all customer activity is essential to the survival of any business, especially small to midsized businesses.

A small to midsized business is looking for any kind of an edge over the larger competition then that edge can be detailed records of customer activity that allow the small to midsized business to know their customers that much better and add a personal touch to the sales process.

To a larger company customer management software is a way to keep the names and companies of thousands of customers organised in a database.

To the small to midsized company CRM software can be a detailed record of not only the business interaction between your company and your customer personal information that can help you add that personal touch to the relationship.

In the end people will always buy from people and an extra personal touch can help cement any business relationship.

The benefits of customer relationship management are as diverse as the businesses using the process and the software. Depending on the type of business, you will need software or CRM that can handle massive data and sort this according to how you want it.

when CRM information is used to analyze trends and shared with the people who directly or indirectly have to do with CRM.

conclusion:-

An organization that runs smooth and efficiently is much more profitable than a business that slows production and progress due to a lack of proper process management, CRM software ruins will solve all the problems.