Configuration Basics

8/3/2019 Configuration Basics

1/84

Siebel Competency

2006 IBM Corporation

Configuration Basics

Uddalok Basu


2/84

Siebel GDC property

2006 IBM Corporation2Page 1

Level of Configuration

Applet Level

BC Level

View Level

Screen Level


3/84


4/84

Siebel GDC property


Applet Level

Applet Properties

Applet Web Templates

Controls

Drilldown Objects

List Column Properties

Applet User Properties.

Applet Toggle.


5/84


6/84

Siebel GDC property


Applet Properties

How to increase or decrease the number of rows to beshown for a list applet.

By the HTML No.Of Rows of the applet.

IfHTML No.Of Rows is left blank then Number of rows to beshown in the list applet are set from the NumberOfListRows in SWEsection of the cfg file. If both are left blank then default value of 10is taken.


7/84


8/84

Siebel GDC property


Applet Properties

Class of the applet

Special classes do not support certain functionalities which are otherwisesupported by other ordinary classes.

For example, popup for Text Areas and Continuous Scrolling might notfunction properly if the applet is based on a special class.

Note:

Changing the class is a resolution which is not permissible since it mightimpair the functionality which necessitated the use of the specializedclass. Hence a workaround has to be devised.


9/84

Siebel GDC property


Applet Properties -Search Spec

Search specification

Restricts the set of records to be displayed.

When do search specifications fail?

Search specifications on child applets are not executed.

Applet Visibility Type property of the view might cause search specs to beignored.

An applet search specification is appended to that of the BC.

Performance

Search specifications impact performance negatively if fields based on

joins are included in the search specification.

Search specs with NOT or OR can also adversely affect performance byforcing the database to execute a full table scan.

Always Use Indexed Column in Search Spec.


10/84

Siebel GDC property


Applet Web Templates

An applet can be displayed in five modes.

Base(Read-only).

Edit

New

Query

Edit List

A list applet usually has 3 web templates

Base,Edit,Edit List

A form applet usually has 2 web templates

Base,Edit


11/84

Siebel GDC property


Applet Controls

For a list applet,the List control is mandatory for displaying columns ofdata from the underlying BC.

Text Controls

*Found in form applets

*Usually a select icon is attached with it.

*Display Format property can be used to specify format ofdata for numeric,date,currency and similar non-text data

types.

E.g.,For DTYPE_DATETIME data,this can be given as

Date,Date Time, DateTimeNoSec, TimeNoSec.


12/84

Siebel GDC property


AppletControls

*Initiate an action when clicked.

*Found in list and form applets.

*Method Invoked property defines the method invoked when

button control is cliicked.

E.g., NewRecord, EditRecord, ExecuteQuery etc.

Note: Customized methods written in server or browserscripts can also be invoked in a similar method on a button-

click event.

Button controls


13/84

Siebel GDC property


AppletControls

Special type of controls How to display the Show More button in a list applet.

The ToggleListRowCount controlis configured:

Control = ToggleListRowCount.

HTML BitMap = BTTNS_MORE

HTML Display Mode =EncodeData

HTML Type =Link

Method Invoked = ToggleListRowCount

Sort = TRUE


14/84

Siebel GDC property


Applet Controls

Special type of controls How to display the Next and Previous buttons in a form applet.

For Previous control,

HTML Bitmap = RECNAV_PREVSET_ON

HTML Disabled BitMap = RECNAV_PREVSET_OFF

HTML Type =RecNavPrv

Method Invoked = GotoPreviousSet

For Next control,

HTML Bitmap = RECNAV_NEXTSET_ON

HTML Disabled BitMap = RECNAV_NEXTSET_OFF

HTML Type =RecNavNxt

Method Invoked = GotoNextSet


15/84

Siebel GDC property


Applet Drilldown

Static Drilldown.

-A specific view isreferenced for each

hyperlink list column.If the source and destination

view are on the same Business

Component then to maintain

the correct reference of the

record the Source field andDestination field for the

Drilldown Object should be

given as Id.


16/84

Siebel GDC property


Applet Drilldown

Dynamic Drilldown.

Enables navigation to multiple

views from the same hyperlink

field,depending on the value of

the field.Drilldown objects for each

candidate view are defined

and that with the lowest

sequence numbercontains

child Dynamic DrilldownDestination objects.These

define the conditions under

which each of the drilldown

objects should be activated.


17/84

Siebel GDC property


Applet List Column Properties

Each list column corresponds to one field in the Business Component.

HTML List Edit Property

Is TRUE by default for all list columns of a applet in Edit List mode.

If a field is marked as Read-only=True,then this property should bemarked as False.Otherwise the icons like calculator,calendar etc may

be shown even when the field is not editable.

Also for editable fields with HTML Type=Checkbox it is often seen that

the checkbox sign appears only after making this property=True.

Best Practice: For all editable fields,make this property True and for

non editable ones,make this False.


18/84

Siebel GDC property



HTML Type

Specifies the style of the control.

Formsection is a custom controlthat helps to group related fields in

an applet.

In Siebel 6,this used to be done

using controls of type Group.

In Siebel 7,this has to be replaced

by formsections.

Each list column corresponds to one field in the Business Component.


19/84

Siebel GDC property



If a calendar or calculator needs to appear for the column,the Runtime

Property is to be set to True.

If a pop-up editor needs to be appear,the Show Popup property is to be

set to True.

If a list column is to be made unavailable in the user interface,the

Available Property is to be set to False.

If a list column is to hidden by default but the user should be able to select

it from the Columns Displayed dialog box then the Show in List property

is to be set to False.Total Required is a True/False Property indicating whether the list column

is to be totaled.


20/84

Siebel GDC property


Miscellaneous

Problem: A message that should appear while performing a New Record

or a Copy Record operation on a list applet appears every time while

scrolling on records.

Reason: The script written in the Browser Script of the applet was

erroneous.

The equality operator was given as =.So each time the condition was

evaluated.

Solution:The correct equality operator = = was specified.


21/84

Siebel GDC property


Business Component Level

BC properties

BC Field Properties

Join

Multi Value Fields

Multi Value Links

BC User Property

BC View Mode


22/84

Siebel GDC property


BC Properties

Class of the BC

The C ++ class that implements the functionality of thebusiness component.

CSSBusComp is the class normally used.

Force Active

If set to TRUE,all fields of the BC are automatically retrievedfrom the database server. This substantially degrades theperformance of the business component and is notrecommended.

Si b l GDC t


23/84

Siebel GDC property


BCProperties

Owner Delete

A TRUE or FALSE value that establishes the deletion rights ofthe user to the business component.

TRUE = Only the owner (under personal or team visibility) candelete the record.

FALSE = Anyone can delete the record. Note:When a view is designated for Admin mode, the Owner

Delete protection is disabled, and anyone having access to theview can delete any record.

Si b l GDC t


24/84

Siebel GDC property


BCProperties

Popup Visibility Auto All

If TRUE then if user has access to any All views,then pop-upvisibility is All; otherwise pop-up visibility is determined byPopup Visibility Type property.

Popup Visibility Type

Values are All, Personal, Sales Rep, Manager, Organization,Sub-Organization, Group, and Catalog.

Si b l GDC t


25/84

Siebel GDC property


BCProperties

Sort Specification

A sort expression is used to order the records returned in aview. But this may be ignored in some cases.

Use of a specialized business component class, other thanCSSBusComp may disable a sort specification.

Siebel applications ignore the sort specification in the BCshaving All and Manager view modes.

Sort specifications on calculated fields do not work.

But this behavior can be overwritten by the BC User PropertyAll Mode Sort.

Use the Business Component User Property "All Mode Sort" andgive the Value as "Normal". This will allow to use thecustomized sort specification.

Si b l GDC t


26/84

Siebel GDC property


BCProperties

All Mode Sort user property will allow the developer tomanipulate sort behavior.

Providing a value 'TRUE' will allow Siebel applications tooverride the sort specification for All views with the standard

user key.

Providing a value 'FALSE' will remove all sort specifications.

Providing a value 'Normal' will allow the use of custom sortspecifications for all views.

So to use the Custom Sort Specification set the value of All ModeSort user property to Normal.

Siebel GDC property


27/84

Siebel GDC property


BC Field Properties

Calculated

Can have a True or False value. If value is set to True The fields value is calculated by the

business

component rather than retrieved from the database server.

Calculated Value The expression used to calculate the fields value if Calculated is

TRUE.

Siebel GDC property


28/84

Siebel GDC property


BC Field Properties

Dest Field

If the Multi Valued property is TRUE, the field in the destinationbusiness component defined in the Multi Value Linkfield. If MultiValued is FALSE, this property is ignored.

Validation

The expression used to ensure data correctness when data isentered.

Also, the validation is evaluated only for the field for which it isadded.Note: Should beused only with

single valuefields,not MVFs.

Siebel GDC property


29/84

Siebel GDC property


BC Field Properties

Immediate Post Changes

Can have a True or False value. If value is set to True Field data is posted to the server

immediately after the focus moves off of the field.

Case Study:The requirement is to fire the validation of the field immediately

after the user moves the focus off the field e.g. the Start Datefield.

Solution:

In Siebel6 the validation property gets fired in the

PresetFieldValue event of a field but in Siebel7 it gets fired in thePrewriteRecord event. So to make the validation immediately afterchanging the value of the Start Date field you have to set itsImmediate Post Changes property value to True.

Siebel GDC property


30/84

Siebel GDC property


BC Field Properties

Force Active

Default value of this property is False.

When the value is set to True, the field is queried eachtime the business component is instantiated, even when thefield is not exposed on the user interface.

Force Active should only be set to TRUE when there is aneed to put script on a field in the active businesscomponent and the field is not exposed on the activeapplet.

Setting this property to TRUE may reduce performance.

Siebel GDC property


31/84

Siebel GDC property


BC Field Properties

Link Specification

Can have a True or False value. If value is set to True then the fields value can be

passed as a default value to a field in the child businesscomponent.

Case Study:

The requirement is to predefault the Account field in theAMGN SFA Account Professional Affiliation BC with the valueof the Name field of the Account BC.

Solution:

Set the Link Specification property of the Name field in theAccount to True.

Siebel GDC property


32/84

Siebel GDC property


BC Field Properties

Predefault Value

The value used for an empty field when a new record is created

The pre-default value for the field is used even when the field isnot exposed in the user interface.

Postdefault Value

The value used for an empty field when the record is initiallywritten to the database.

Note:

One can only pre-default system columns in the table level andthe values for others should be pre-defaulted in the BC level.

These properties are not validated for a calculated field.

If both predefault and postdefault values are given for a fieldthen the predefault is stamped.

Siebel GDC property


33/84

Siebel GDC property


Thejoin 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).

Source Field property identifies the foreign key field in the

business component.

Destination Column property identifies the primary key column inthe joined table.

NOTE: In rare circumstances, there can be multiple joinspecifications in a single join.For example, the Sub Campaign business component has a jointo theS_LANG table with two join specifications. In such cases thesource fields in the join specifications should be based upon the

same table.

Join

Siebel GDC property


34/84

Siebel GDC property


Thejoin constraint is a constant-valued search specification applied to acolumn during a join.

Join

Siebel GDC property


35/84

Siebel GDC property


Some special properties and restrictions of MVFs arediscussed below.

1)In Siebel 7 we can not make a MVF as required throughconfiguration.

This has to be done through scripting.

Case Study: The requirement is to set the MVF Role inthe XX BC as required.

Solution 1: Write the following piece of code in theBusComp_PreWriteRecord" of the

XX BC.

Solution 2: Through Configuration.

MVFProperties


36/84

Siebel GDC property


37/84

Siebel GDC property


MVF Required through Configuration

Create a Calculated field and in calculated value enter

the [MVF field name].

Example: To make MVF field Street Address Required

Create a new field with any name: CPC Street Address

Calculated value True

Value [Street Address]

Required True

Siebel GDC property


38/84

p p y


MVF Properties

2) In general as MVF's can not be predefaulted using the 'Predefault'property on the field object, the workaround is normally a scriptingsolution.

Case Study:

The requirement is to predefault the Role MVF in the child BC withthe value of the Prof Role field in the parent BC.

Solution:

Dim sRole As String

Dim oParentBO As BusObjectDim oParentBC As BusComp

Dim RoleMVG As BusComp

Siebel GDC property


39/84

p p y


MVF Properties

Set oParentBO = me.BusObject

Set oParentBC = oParentBO.GetBusComp("Contact")

sRole = oParentBC.GetFieldValue("Prof Role")

Set RoleMVG = me.GetMVGBusComp("Role")

With RoleMVG

.NewRecord NewBefore

.SetFieldValue "Role",sRole

.WriteRecord

End With

Set RoleMVG = Nothing

Set oParentBC = Nothing

Set oParentBO = Nothing

Siebel GDC property


40/84

p p y


MVF Properties

3) Multi value fields should be updated only by selecting the

records from the MVG Applet and for this PopUp Update

property of the MVL is usually set as TRUE.

But if these fields are made as editable in the Applet level,error isthrown while updating these.

The standard is to make these fields as read only in the Applet

level.

E.g.,The City,State,Zip,Country,Phone,Fax fields should be

populated from the MVG applet ofAddress.

Siebel GDC property


41/84

p p y


MVF Properties

4)A multi value field cannot be used as a source field in a join

specification of a join.

Practical Example:

Problem faced : Deletion on Accounts list applet throwing following

error-

Join in business component definition 'AMGN Action Team - CE' has

source fields that come from tables 'Employee' and 'S_EVT_ACT'

(SBL-DAT-00452)

Solution:For the Business Component 'AMGN Action Team - CE', thejoin specification 'Owner' of the join 'S_CONTACT' used the source

field 'Owned By Id which was a MVF populated through a MVL

Employee.This join specificationwas inactivated.

Siebel GDC property


42/84


MVL Properties

No Associate

A TRUE or FALSE value.TRUE = Specifies that no associations can be created throughthe link.New detail records may be added.

This property is ignored if the current view is in Admin Mode.

Popup Update Only

A TRUE or FALSE value.TRUE = Requires that the multivalue group window bepopped up for any of the MVG values to be updated.

Siebel GDC property


43/84


What are User Properties ?

User properties are object definitions that areadded as children to an applet,businesscomponent,control,field or list column to

configure specialized behavior beyond what isconfigured in the parent object definitionsproperties.

Siebel GDC property


44/84


BC User Properties

1. All Mode Sort.2. DB2 Optimization Level.

3. Deep Delete.

4. Manager List Mode.

5. Named Method n.

6. On Field Update invoke.

7. On Field Update set.

8. BC Read Only Field.

9. Field Read Only Field.

10. Parent Read Only Field.

11. Sort Field Map n.

12. State Model.

13. Picklist Pre Default Field n

Siebel GDC property


45/84


1. All Mode Sort

This user property determines whether or not the Siebelapplication overrides the sort specification and if so,determinesthe sort(if any) that is applied to the business component forAll or Manager views.

The values are the following:

Normal Uses the BC defined sort specifications.Also allows the user to

run a PDQ.

TRUE

Overrides the BC sort specifications and uses the standard user

key. FALSE

Removes all sorting.

Siebel GDC property


46/84


2. DB2 Optimization Level

Currently the DB2 connector uses an optimization level of 0 foroptimizing client SQL statements.In some cases,certain SQLstatements may perform suboptimally using optimization level0.This user property allows an implementor to change theoptimization level of all the SQL statements produced by thegiven business components.

As this setting affects the whole BC,changing it may adverselyaffect the performance of other SQL statements produced bythe same BC.

This user property canonly be used in expertmode.

Siebel GDC property


47/84


3.Deep Delete

Normally the Delete option only deletes one level.

Deep Delete allows child business components and their respective childbusiness components to be deleted automatically when selecting theDelete option.

How to configure?

1 Create a user property for each child BC to be included in the DeepDelete. The child business component user

properties are:

Name: Deep Delete 1

Value: [Child BusComp Name]

Name: Deep Delete 2

Value: [Child BusComp Name]

Siebel GDC property


48/84


3.Deep Delete

2 Add a multivalue link in the parent BC for each child BC.

3 Set the No Delete attribute in the MVL to TRUE.

TRUE: allows deep delete for child business component

FALSE: does not allow deep delete for child business component

4 Create a multivalue field in the parent business component from eachchild BC, using the multivalue link. This field is usually not displayed onthe screen but needs to be present on the business component.


49/84

Siebel GDC property


50/84


5. Named Method n

This user property allows to invoke a method from a BC or a businessservice,or set a field value.

For setting a field value,the syntax is:

[Name], SET, [Field], [Expression]

When [Name] is called,the value of [Field] is set using [Expression].

Siebel GDC property


51/84


5. Named Method n

For invoking a business component method,the syntax is: [Name], [Action], [BusComp], [Method]

When [Name] is called, [Method] is invoked on the [BusComp] businesscomponent on the defined [Action].

Siebel GDC property


52/84


6. On Field Update Invoke

This user property allows a business component method to be invokedwhen the specified field is updated.

The value consists of 3 quoted parameters:

[FieldToCheck], [BusCompName], [MethodName]

[MethodName] is invoked on the [BusCompName] business componentwhen [FieldToCheck] is updated.If [FieldToCheck] is not defined,themethod is invoked when the user saves the record.

A fourth parameter can be used to define a condition.Then the method isinvoked if the condition evaluates to TRUE.

Siebel GDC property


53/84


6. On Field Update Invoke

In the example below, the method UpdateStatusis invoked when the Status field of Contact BCis updated.

Siebel GDC property


54/84


7. On Field Update Set

This user property allows to set the value of a field in the businesscomponent when another field is updated.

The value consists of 3 quoted parameters:

[FieldToCheck], [FieldToSet], [Value]

[FieldToSet] is set to [Value] when [FieldToCheck] is updated.If the Valueparameter is not defined, [FieldToSet] is set to the value of[FieldToCheck] .

An expression can also be used for the Value parameter.

Siebel GDC property


55/84


7. On Field Update Set

In the example below, the Partnership ContactFlag is set using the expression when thePartnership Key Contact Flag field is updated.

Siebel GDC property


56/84


Specifies a TRUE or FALSE field in the record that, when TRUE, causes the current record tobecome read-only.

This user property specifies a Boolean field that, when TRUE, causes all fields in the currentrecord to become read-only. This also prevents the user from updating or deleting therecord, but does not prevent the addition of new records to the business component.

Name:Contains the literal text BC Read Only Field.

Value:Contains the name of a field in the same business component as the parentobject definition of the user property. This field must be a TRUE or FALSE field.

Example:

situation in which you need to prevent users from updating inactive accounts. The InactiveAccount field in an account record is a TRUE or FALSE field that, when TRUE, indicates thatthe account is inactive.

Following are the property settings:

Name:BC Read Only Field

Value:Inactive Account

8. BC Read Only Field

Siebel GDC property


57/84


This user property is similar to BC Read Only Field,however, unlike BC Read OnlyField, the Field Read Only Field user property restricts one field in the samebusiness component,rather than the entire business component record.

NameContains an expression in the following format:

Field Read Only Field: fieldnameNote: only a single space between the colon and the field name.

ValueContains the name of the test field. This must be a TRUE or FALSE field.

Example:

If an account record has been included because that account is acompetitor, you do not want users to be specifying that accountscompetitors.

Cont..

9. Field Read Only Field

Siebel GDC property


58/84


To restrict the Competitor field in an account based on theaccounts type

1 Navigate to the Business Component object type in the Object Explorer, andthento the Account object definition in the Object List Editor.2 Create a calculated Boolean field in this business component that will havea value of TRUE when the Type field has a value of Competitor.For purposes of the example, the name of this test field can be CompetitorCalc,although the name is unimportant as long as it is referenced correctly inthe userproperty.3 In the calculation property of the Competitor Calc field, enter the followingvalue:IIf([Type] = "Competitor", "Y", "N")4 Expand the Business Component object type in the Object Explorer, andselect the Business Component User Prop object type. Click the Object List

Editor to make it active, and choose Edit > New Record.5 Set the following values in the new Business Component User Prop objectDefinition

Name :Field Read Only Field: CompetitorValue :

Competitor Calc


Siebel GDC property


59/84



Siebel GDC property


60/84


This read-only restriction on an entire business component, rather than a singletarget field. This restriction occurs when a TRUE or FALSE test field has a TRUEvalue.

This user property is used to place a restriction on a childor grandchild (and so on)business component of the business component containing the test field.

Parent Read Only Field is used primarily to restrict the detail records in a multi-

value group. It could also be used to restrict the detail records in a master-detailview, but in that case you need to make sure that the restricted businesscomponent is not also used in the context of some other business object than theintended one.

NameContains the literal text Parent Read-Only Field.

ValueContains an expression in the following format:buscompname.fieldname

where fieldname is the name of the test field, that is, the TRUE or FALSE field tobe evaluated, and buscompname is the name of the business component in whichthe test field is located.

10. Parent Read Only Field

Siebel GDC property


61/84


Example: situation where you want to disable the update of the Account Address

multi-value group when the account record has a Type of Competitor.

To accomplish this, you add the same calculated field as in the Field Read OnlyField

user property to the Business Address business component with the followingvalues:

Name:Parent Read Only Field

ValueAccount.Competitor Calc

This causes the Account Address multi-value group to be read-only when the

account record is for a competitor.

NOTE:When using the Parent Read Only Field user property, the test field musthave its Link Specification property set to TRUE. Otherwise the dynamic read-onlyfunctionality does not work. However, if the child record is displayed in themultivalue field in the parent business component, it is not necessary to have theLink Specification property of the field set to TRUE.

10. Parent Read Only Field

Siebel GDC property


62/84


11. Sort Field Map n

Several opportunity-related business components, such as Opportunity and

Global Account Opportunity, have a one-to-many relationship with theRevenue business component. These relationships enable master/detail

views that display the revenue records associated with an opportunity.

Opportunities typically have several multivalue fields that reference fields in

the Revenue business component. For example, the Revenue and Close

Date fields on the Opportunity business component reference the Revenue

and Date fields on the Revenue business component, respectively.

Value: "field", "redirect field

field is the name of a multivalue field on the current opportunity-related businesscomponent, such as Close Date or Revenue, that maps to a field on the Revenue

business component.

redirect field is the name of the single-value field on the current opportunity-relatedbusiness component that maps to the same revenue field on the primary revenue

record for the opportunityfor example, Primary Revenue Close Date or Primary

Revenue Amount.

Siebel GDC property


63/84


11. Sort Field Map nIn the example below, the Close Date is a multivalue field and thePrimary Revenue Close Date is a single value field stored in Opportunity

BC.

Functional Area : Predefined queries on opportunity-related business components

Siebel GDC property


64/84


12. State Model

This user property allows you to make additional business components

accessible to the State Model business component Multi-Value Group

applet

Siebel GDC property


65/84


13. Picklist Pre Default Field n

Within a view based on a parent business component, such as Action, the

user may be able to create a new record of a child business component,such as Opportunity, through a picklist for the child business component.

The Picklist Pre Default Field user property is used to default fields on the

new record of the child business component to field values from the parent

business component record.

Value : "field", "'buscomp1.field1','buscomp2.field2',' . . .'"

where

field is a field on the current business component

buscompn.fieldn is a field name on a parent business component

Siebel GDC property


66/84


13. Picklist Pre Default Field nWhen a new opportunity is created from the picklist in either context, the

opportunity's Account and Account Id fields can be defaulted to the corresponding

field values on the parent record by adding the following user properties to theOpportunity business component:

Siebel GDC property


67/84


Miscellaneous

Remember!

If there is an option between creating a Business Object and a

Business Component,then we should always create the Business

Object as BO is easily configurable than BC with less overheads

regarding maintenance.

NOTE:-These user properties do not function when used in an applet in aview where the view's Admin Mode property is set to TRUE.

Siebel GDC property


68/84


View Level

View properties

View Web Templates

Siebel GDC property


69/84


ViewProperties

Admin Mode Flag

If set to TRUE,designates the view as a Admin mode view.

Admin mode disables all visibility rules. i.e.,user can see every record.

The No Insert,No Merge,No Update restrictions of the Bc are ignored but

not of the applet.

If this flag is set to True,and if pop-up visibility is also set for the BC,then

pop up visibility will still take effect.

For an Admin mode view,the Bc visibility type is ignored unless set to

Organization.

BC user properties are overridden but properties like Read-only still hold

good.

Siebel GDC property


70/84


ViewProperties

Explicit Login

If set to TRUE,it requires that the user has explicitly logged on through

the logon web page to see this view.

Screen menu

If set to TRUE,the view should be included in the screen menu of the

application.

Secure

If set to True,the Siebel web engine will verify that the current request

used the HTTPS protocol.This prevents the client from obtaining accessto a secure view by typing HTTP instead of HTTPS.

Siebel GDC property


71/84


ViewProperties

Visibility Applet

Indicates which of the applets in the view is the one where visibility is

controlled.Usually this is the list applet in a list-form view or the master

applet in a master-detail view.

Visibility Applet Type

The visibility mode that will be applied to the applet.

Valid values are:

All,Catalog,Group,Manager,Organization,Personal,Sales Rep etc.

Siebel GDC property


72/84


View Web Templates

Web Templates

Indicates which web template to be used for the view.

Commonly used are:

View Basic

Applets are stacked one above the other.

Siebel GDC property


73/84


View Web Templates

View Detail

Here the non context views are presented as tabs and multiple

grandchild applets can be accommodated.

Siebel GDC property


74/84


View Web Templates

View Detail 2

Here the non context views and categorized sub views are presented as

tabs.

Siebel GDC property


75/84


View Web Templates

The applet mode of the applets mentioned in View Web Template Item ofthe view are the sameApplet Web Templates added for the applet.

The applet mode of list applets should be given as Edit List.

The applet mode of form applets should be given as Edit.

Otherwise,the following problems may be seen:

List applet showing no list columns.

List applet showing some list columns.

On doing a New Record on list applet,the Edit mode of the appletshown.

Form applet showing no controls.

Siebel GDC property


76/84


View

The possible reasons why a view is not visible:

The view is not given proper responsibility.

The view is inactive.

The view is not added as a screen view in the screen or the screen view

is inactive.

Proper visibility applet and visibility applet type not given for view.

The view web template does not support view tabs.

The application does not have proper license to use the particular view.The view is not compiled to the correct srf.

If the view and its parent screen are in different projects then it is better to

compile both.

Siebel GDC property


77/84


View

Remember!

All the views under a screen must be in the same Business object.

Or else,the consistency of record is not maintained when we navigate

from one view to another.

Exception: In case of Admin screens,the views may belong to different

BOs.

Siebel GDC property


78/84


Screen Level

Screen Properties

Screen View Properties

Siebel GDC property


79/84


Screen Properties

Screen-Logical grouping of views.

If the Visibility Applet property of the view is set to null,then the viewappears as a view tab.

If the Visibility Applet property of the view is not null,then the view

appears in the Show: combo box.

Siebel GDC property


80/84


Screen Properties

Default View-View that the user will see when he clicks on a page tab fora screen.

A screen added as a Page Tab in the application is visible as a Screen

Tab.

A screen added as a Screen Menu Item in the application is visible

in the site map.

Siebel GDC property


81/84



Menu Text- Both the screen view menu text property and the ScreenMenu Item display value is shown in the site map.The former shows up

as a sub item under the latter.

Sequence-Specifies the order in which the views will appear.

Category-Logical representation of what category the view belongs to.

Category Menu Text-The display value that appears within the combobox.

Category ViewBar Text-Display text of the view tab under which it

appears.

Siebel GDC property


82/84



ViewBar Text- The display text of the viewtabs of the view.

Note: The same view may be added in multiple screens.This may lead to

ambiguity in certain cases and the correct screen may not be displayed

for a view.

So it is advisable to inactivate the screen view under the screen which is

not needed.

Siebel GDC property


83/84


Q & A

Siebel GDC property


84/84

Thank You

Documents

Configuration Basics