Configuration Basics

Siebel Competency
Configuration Basics
Uddalok Basu
2006 IBM Corporation
Siebel GDC property
Level of Configuration
Applet Level BC Level View Level Screen Level
2Page 1
Siebel GDC property
Major Object Definitions
Keywords:
Joins, Links, MVFs, Picklists, Drilldowns, Properties, User Properties, MVGs, Primaries,
3Page 1 2006 IBM Corporation
Siebel GDC property
Applet Level
Applet Properties Applet Web Templates Controls Drilldown Objects List Column Properties Applet User Properties. Applet Toggle.
4Page 1
Siebel GDC property
Applet Properties
How to make an applet read-only.
The following properties of the applet should be marked TRUE:
No Delete No Insert No Merge No Update

Note:These properties can also be set at the Business Component level but then all applets based on this BC will be read-only.
5Page 1
Siebel GDC property
Applet Properties
How to increase or decrease the number of rows to be
shown for a list applet.
By the HTML No.Of Rows of the applet. If HTML No.Of Rows is left blank then Number of rows to be
shown in the list applet are set from the NumberOfListRows in SWE section of the cfg file. If both are left blank then default value of 10 is taken.
6Page 1
Siebel GDC property
Applet Properties
Class of the applet

The C++ class used to manage the applet. Form applets use the CSSFrame class,and list applets use the CSSFrameList class.There are also some specialized classes for applets that use special business components and have special features.
Note:
Controls on applets belonging to a specialized class should not be deleted because this may break methods used on applets.
7Page 1
Siebel GDC property
Applet Properties
Class of the applet
Special classes do not support certain functionalities which are otherwise supported by other ordinary classes. For example, popup for Text Areas and Continuous Scrolling might not function properly if the applet is based on a special class. Note:
Changing the class is a resolution which is not permissible since it might impair the functionality which necessitated the use of the specialized class. Hence a workaround has to be devised.
8Page 1
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 be ignored. 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 by forcing the database to execute a full table scan. Always Use Indexed Column in Search Spec.
9Page 1
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
10Page 1
Siebel GDC property
Applet Controls
For a list applet,the List control is mandatory for displaying columns of data 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 of data 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.
Siebel GDC property
Applet Controls
Button controls
*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 browser scripts can also be invoked in a similar method on a buttonclick event.
12Page 1
Siebel GDC property
Applet Controls
Special type of controls

How to display the Show More button in a list applet. The ToggleListRowCount control is configured: Control = ToggleListRowCount. HTML BitMap = BTTNS_MORE HTML Display Mode =EncodeData HTML Type =Link Method Invoked = ToggleListRowCount Sort = TRUE
13Page 1
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
14Page 1
Siebel GDC property
Applet Drilldown
Static Drilldown. -A specific view is referenced 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 and Destination field for the Drilldown Object should be given as Id.
15Page 1
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 number contains child Dynamic Drilldown Destination objects.These define the conditions under which each of the drilldown objects should be activated.
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 be marked 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.
17Page 1
Siebel GDC property

Each list column corresponds to one field in the Business Component. HTML Type Specifies the style of the control. Formsection is a custom control that 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.
18Page 1
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.
19Page 1
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.
20Page 1
Siebel GDC property
Business Component Level

BC properties BC Field Properties Join Multi Value Fields Multi Value Links BC User Property BC View Mode
21Page 1
Siebel GDC property
BC Properties
Class of the BC The C ++ class that implements the functionality of the business component. CSSBusComp is the class normally used. Force Active If set to TRUE,all fields of the BC are automatically retrieved from the database server. This substantially degrades the performance of the business component and is not recommended.
22Page 1
Siebel GDC property
BC Properties
Owner Delete A TRUE or FALSE value that establishes the deletion rights of the user to the business component. TRUE = Only the owner (under personal or team visibility) can delete 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 the view can delete any record.
23Page 1
Siebel GDC property
BC Properties
Popup Visibility Auto All If TRUE then if user has access to any All views,then pop-up visibility is All; otherwise pop-up visibility is determined by Popup Visibility Type property.
Popup Visibility Type Values are All, Personal, Sales Rep, Manager, Organization, Sub-Organization, Group, and Catalog.
24Page 1
Siebel GDC property
BC Properties
Sort Specification A sort expression is used to order the records returned in a view. But this may be ignored in some cases.
Use of a specialized business component class, other than CSSBusComp may disable a sort specification. Siebel applications ignore the sort specification in the BCs having All and Manager view modes. Sort specifications on calculated fields do not work.
But this behavior can be overwritten by the BC User Property All Mode Sort. Use the Business Component User Property "All Mode Sort" and give the Value as "Normal". This will allow to use the customized sort specification.
25Page 1
Siebel GDC property
BC Properties
All Mode Sort user property will allow the developer to manipulate sort behavior.
Providing a value 'TRUE' will allow Siebel applications to override 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 sort

specifications for all views.
So to use the Custom Sort Specification set the value of All Mode Sort user property to Normal.
26Page 1
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.
27Page 1
Siebel GDC property
BC Field Properties
Dest Field If the Multi Valued property is TRUE, the field in the destination business component defined in the Multi Value Link field. If Multi Valued is FALSE, this property is ignored. Validation The expression used to ensure data correctness when data is entered. Also, the validation is evaluated only for the field for which it is added.
Note: Should be used only with single value fields,not MVFs.
28Page 1
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 Date field. Solution: In Siebel6 the validation property gets fired in the PresetFieldValue event of a field but in Siebel7 it gets fired in the PrewriteRecord event. So to make the validation immediately after changing the value of the Start Date field you have to set its Immediate Post Changes property value to True.
29Page 1
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 each time the business component is instantiated, even when the field is not exposed on the user interface. Force Active should only be set to TRUE when there is a need to put script on a field in the active business component and the field is not exposed on the active applet. Setting this property to TRUE may reduce performance.
30Page 1
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 business component.
Case Study: The requirement is to predefault the Account field in the AMGN SFA Account Professional Affiliation BC with the value of the Name field of the Account BC. Solution: Set the Link Specification property of the Name field in the Account to True.
31Page 1
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 is not exposed in the user interface. Postdefault Value The value used for an empty field when the record is initially written to the database. Note:
One can only pre-default system columns in the table level and the 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 field then the predefault is stamped.
32Page 1
Siebel GDC property
Join
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). Source Field property identifies the foreign key field in the business component. Destination Column property identifies the primary key column in the joined table. NOTE: In rare circumstances, there can be multiple join specifications in a single join. For example, the Sub Campaign business component has a join to the S_LANG table with two join specifications. In such cases the source fields in the join specifications should be based upon the same table. 2006 IBM Corporation 33Page 1
Siebel GDC property
Join
The join constraint is a constant-valued search specification applied to a column during a join.
34Page 1
Siebel GDC property
MVF Properties
Some special properties and restrictions of MVFs are
discussed below.
1)In Siebel 7 we can not make a MVF as required through configuration. This has to be done through scripting. Case Study: The requirement is to set the MVF Role in the XX BC as required. Solution 1: XX BC. Solution 2: Write the following piece of code in the BusComp_PreWriteRecord" of the Through Configuration.
35Page 1
Siebel GDC property
MVF Required Properties through script

function BusComp_PreWriteRecord () { required_view = TheApplication().ActiveViewName(); if(required_view == <The View on which we want the MVF mandatory") { var Required_BO = TheApplication().GetBusObject('<BO for Current view>'); var Required_BC = Required_BO.GetBusComp('<BC for current Applet>'); var MVG_Field = Required_BC.GetFieldValue ("<MVG Field>"); if((MVG_Field == "")||(MVG_Field.length <1 )) { TheApplication().RaiseErrorText("<MVG Field> is a Required Fields") return(CancelOperation); } } return(ContunueOperation); }
36Page 1
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
37Page 1
Siebel GDC property
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 scripting solution. Case Study: The requirement is to predefault the Role MVF in the child BC with the value of the Prof Role field in the parent BC. Solution:
Dim sRole As String Dim oParentBO As BusObject Dim oParentBC As BusComp Dim RoleMVG As BusComp
38Page 1
Siebel GDC property
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
39Page 1
Siebel GDC property
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 is thrown 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 of Address.
40Page 1
Siebel GDC property
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 errorJoin 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', the join 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 specification was inactivated.
Siebel GDC property
MVL Properties
No Associate A TRUE or FALSE value. TRUE = Specifies that no associations can be created through the 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 be popped up for any of the MVG values to be updated.
42Page 1
Siebel GDC property
What are User Properties ?

User properties are object definitions that are
added as children to an applet,business component,control,field or list column to configure specialized behavior beyond what is configured in the parent object definitions properties.
43Page 1
Siebel GDC property
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
1. All Mode Sort

This user property determines whether or not the Siebel
application overrides the sort specification and if so,determines the sort(if any) that is applied to the business component for All or Manager views.
The values are the following: Normal

Uses the BC defined sort specifications.Also allows the user to run a PDQ. Overrides the BC sort specifications and uses the standard user key. Removes all sorting.
TRUE
FALSE
45Page 1
Siebel GDC property
2. DB2 Optimization Level
Currently the DB2 connector uses an optimization level of 0 for optimizing client SQL statements.In some cases,certain SQL statements may perform suboptimally using optimization level 0.This user property allows an implementor to change the optimization level of all the SQL statements produced by the given business components. As this setting affects the whole BC,changing it may adversely affect the performance of other SQL statements produced by the same BC.
This user property can only be used in expert mode.
46Page 1
Siebel GDC property
3.Deep Delete
Normally the Delete option only deletes one level. Deep Delete allows child business components and their respective child business components to be deleted automatically when selecting the Delete option. How to configure? 1 Create a user property for each child BC to be included in the Deep Delete. The child business component user properties are: Name: Deep Delete 1 Value: [Child BusComp Name] Name: Deep Delete 2 Value: [Child BusComp Name]
47Page 1
Siebel GDC property
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 each child BC, using the multivalue link. This field is usually not displayed on the screen but needs to be present on the business component.
48Page 1
Siebel GDC property
4.Manager List Mode

Using this user property, in a manager view records for all people who report to a manager (not only the primaries) may be seen . Values: Primary (the default) or Team. When set to Team, a sub query is performed for the My Teams views to retrieve the accounts,opportunities etc.where the reps are anywhere on the team,not just the primary. Performance is slower but yields more data.
49Page 1
Siebel GDC property
5. Named Method n
This user property allows to invoke a method from a BC or a business service,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].
50Page 1
Siebel GDC property
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] business component on the defined [Action].
51Page 1
Siebel GDC property
6. On Field Update Invoke

This user property allows a business component method to be invoked when the specified field is updated.
The value consists of 3 quoted parameters: [FieldToCheck], [BusCompName], [MethodName]
[MethodName] is invoked on the [BusCompName] business component when [FieldToCheck] is updated.If [FieldToCheck] is not defined,the method is invoked when the user saves the record.
A fourth parameter can be used to define a condition.Then the method is invoked if the condition evaluates to TRUE.
52Page 1
Siebel GDC property
6. On Field Update Invoke

In the example below, the method UpdateStatus is invoked when the Status field of Contact BC is updated.
53Page 1
Siebel GDC property
7. On Field Update Set

This user property allows to set the value of a field in the business component 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 Value parameter is not defined, [FieldToSet] is set to the value of [FieldToCheck] . An expression can also be used for the Value parameter.
54Page 1
Siebel GDC property
7. On Field Update Set

In the example below, the Partnership Contact Flag is set using the expression when the Partnership Key Contact Flag field is updated.
55Page 1
Siebel GDC property
8. BC Read Only Field

Specifies a TRUE or FALSE field in the record that, when TRUE, causes the current record to become read-only. This user property specifies a Boolean field that, when TRUE, causes all fields in the current record to become read-only. This also prevents the user from updating or deleting the record, 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 parent object 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 Inactive Account field in an account record is a TRUE or FALSE field that, when TRUE, indicates that the account is inactive. Following are the property settings: Name:BC Read Only Field Value:Inactive Account
56Page 1
Siebel GDC property
9. Field Read Only Field

This user property is similar to BC Read Only Field,however, unlike BC Read Only Field, the Field Read Only Field user property restricts one field in the same business component,rather than the entire business component record. Name Contains an expression in the following format: Field Read Only Field: fieldname Note: only a single space between the colon and the field name. Value Contains 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 a competitor, you do not want users to be specifying that accounts competitors.
Cont..
57Page 1
Siebel GDC property

To restrict the Competitor field in an account based on the accounts type
1 Navigate to the Business Component object type in the Object Explorer, and thento the Account object definition in the Object List Editor. 2 Create a calculated Boolean field in this business component that will have a 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 Competitor Calc,although the name is unimportant as long as it is referenced correctly in the userproperty. 3 In the calculation property of the Competitor Calc field, enter the following value:IIf([Type] = "Competitor", "Y", "N") 4 Expand the Business Component object type in the Object Explorer, and select 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 object Definition Name : Field Read Only Field: Competitor Value : Competitor Calc 58Page 1
Siebel GDC property
59Page 1
Siebel GDC property
10. Parent Read Only Field

This read-only restriction on an entire business component, rather than a single target field. This restriction occurs when a TRUE or FALSE test field has a TRUE value. 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 multivalue group. It could also be used to restrict the detail records in a master-detail view, but in that case you need to make sure that the restricted business component is not also used in the context of some other business object than the intended one. Name Contains the literal text Parent Read-Only Field. Value Contains an expression in the following format: buscompname.fieldname where fieldname is the name of the test field, that is, the TRUE or FALSE field to be evaluated, and buscompname is the name of the business component in which the test field is located.
Siebel GDC property
10. Parent Read Only Field

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 Only Field user property to the Business Address business component with the following values: Name: Parent Read Only Field Value Account.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 must have its Link Specification property set to TRUE. Otherwise the dynamic read-only functionality does not work. However, if the child record is displayed in the multivalue field in the parent business component, it is not necessary to have the Link Specification property of the field set to TRUE.
Siebel GDC property
11. Sort Field Map n

Several opportunity-related business components, such as Opportunity and Global Account Opportunity, have a one-to-many relationship with the Revenue 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 business component, 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-related business 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
11. Sort Field Map n

In the example below, the Close Date is a multivalue field and the Primary Revenue Close Date is a single value field stored in Opportunity BC. Functional Area : Predefined queries on opportunity-related business components
63Page 1
Siebel GDC property
12. State Model

This user property allows you to make additional business components accessible to the State Model business component Multi-Value Group applet
64Page 1
Siebel GDC property
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
65Page 1
Siebel GDC property
13. Picklist Pre Default Field n

When 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 the Opportunity business component:
66Page 1
Siebel GDC property
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 a view where the view's Admin Mode property is set to TRUE.
67Page 1
Siebel GDC property
View Level
View properties View Web Templates
68Page 1
Siebel GDC property
View Properties
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
View Properties
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 access to a secure view by typing HTTP instead of HTTPS.
70Page 1
Siebel GDC property
View Properties
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.
71Page 1
Siebel GDC property
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.
72Page 1
Siebel GDC property
View Web Templates

View Detail Here the non context views are presented as tabs and multiple grandchild applets can be accommodated.
73Page 1
Siebel GDC property
View Web Templates

View Detail 2 Here the non context views and categorized sub views are presented as tabs.
74Page 1
Siebel GDC property
View Web Templates

The applet mode of the applets mentioned in View Web Template Item of the view are the same Applet 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 applet shown. Form applet showing no controls.
75Page 1
Siebel GDC property
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
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.
77Page 1
Siebel GDC property
Screen Level
Screen Properties Screen View Properties
78Page 1
Siebel GDC property
Screen Properties
Screen-Logical grouping of views.
If the Visibility Applet property of the view is set to null,then the view appears 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
Screen Properties
Default View-View that the user will see when he clicks on a page tab for a 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.
80Page 1
Siebel GDC property
Screen View Properties

Menu Text- Both the screen view menu text property and the Screen Menu 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 combo box. Category ViewBar Text-Display text of the view tab under which it appears.
Siebel GDC property
Screen View Properties

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.
82Page 1
Siebel GDC property
Q&A
83Page 1
Siebel GDC property
Thank You
84Page 1

Configuration Basics

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Configuration Basics

Hochgeladen von

Copyright:

Verfügbare Formate

Siebel Competency

Siebel GDC property

Applet Level BC Level View Level Screen Level

2006 IBM Corporation

Siebel GDC property

Major Object Definitions

Siebel GDC property

2006 IBM Corporation

Siebel GDC property

No Delete No Insert No Merge No Update

2006 IBM Corporation

Siebel GDC property

2006 IBM Corporation

Siebel GDC property

2006 IBM Corporation

Siebel GDC property

2006 IBM Corporation

Siebel GDC property

Applet Properties -Search Spec

2006 IBM Corporation

Siebel GDC property

Applet Web Templates

Base(Read-only). Edit New Query Edit List

A list applet usually has 3 web templates

A form applet usually has 2 web templates

2006 IBM Corporation

Siebel GDC property

Siebel GDC property

2006 IBM Corporation

Siebel GDC property

2006 IBM Corporation

Siebel GDC property

2006 IBM Corporation

Siebel GDC property

2006 IBM Corporation

Siebel GDC property

Siebel GDC property

Applet List Column Properties

2006 IBM Corporation

Siebel GDC property

Applet List Column Properties

2006 IBM Corporation

Siebel GDC property

Applet List Column Properties

2006 IBM Corporation

Siebel GDC property

2006 IBM Corporation

Siebel GDC property

Business Component Level

2006 IBM Corporation

Siebel GDC property

2006 IBM Corporation

Siebel GDC property

2006 IBM Corporation

Siebel GDC property

2006 IBM Corporation

Siebel GDC property

2006 IBM Corporation

Siebel GDC property

Providing a value 'Normal' will allow the use of custom sort

2006 IBM Corporation

Siebel GDC property

2006 IBM Corporation