Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Siebel Revision

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 5
At a glance
Powered by AI
The key takeaways from the document are the different Siebel objects like picklists, links, joins, drilldowns and their usage and properties.

The different types of picklists in Siebel are static picklists which have fixed values and dynamic picklists which can have values dependent on another field. Hierarchical picklists also allow constraining child values based on parent values selected.

A link defines a relationship between two business components and allows master-detail views. A join creates a relationship between a business component and an external table to access columns from that table usually in a 1-1 relationship.

1.

Picklist
a. Static (based on Picklist Generic/Hierarchical)
i. Hierarchical
1. A hierarchical picklist displays values that are
constrained by values selected in another picklist. For
example, in the Service Request Detail Applet, the Area
and Subarea fields are both picklists that draw their
values from the List of values table (S_LST_OF_VAL).
The items available in the Subarea picklist depend on
what the user has selected in the Area picklist.
ii. Constraints
1. constraints values for dynamic picklist
b. Dynamic (based on BC, needs pick applet)

2. Audit Trail
a. Audit Trail creates a history of the changes that have been made to
data in Siebel applications. An audit trail is a record showing who has
accessed an item, which operation was performed, when it was
performed, and how the value was changed.

3. What are the different mechanism for the Access Control


a. Personalisation
b. Views + Responsibilities
c. BusComp View mode
d. Organisation vs division
i. Organizations can be used to control data visibility, Divisions
cannot. Division is the child of organization and can be used
to set Default Currencies.

4. MVG
i. Primary in MVG increases the performance by allowing a
single query using the SQL join to display both the Parent
and the Child records in parent Applet. (from 1:M to 1:1)

Without primaries, each MVG needs a separate query to


display a child record in the parent Applet. With Primary,
using a single query,you will be able to diaply both the
parent and the child records.

5. Link
a. Specifies the relationship between two business components. The
relationship can be one-to-many (1:M), such as parent/child, or many-
to-many (M:M).

A link defines a one-to-many (or master-detail) relationship between


two business components. The Link object type makes master-detail
views possible, in which one record of the master business component
displays with many detail business component records that correspond
to the master.

6. Join
a. A Join object definition creates a relationship between a business
component and a table other than its base table.

This relationship allows the business component to use columns from


the other table. The join uses a foreign key in the business component
to obtain rows on a one-to-one basis from the joined table, even though
the two tables do not necessarily have a one-to-one relationship.

Join have 1:1 and Many:1 RelationShip

7. Drilldown
a. Drilldowns allow users to click a hyperlink in a field and be taken to
another view that displays more information about the field.
Drilldowns are used primarily in list applets. The drilldown object is a
child object of applet. Drilldown behavior is not supported on MVG
applets, pick applets, or association applets.

Drilldowns can be either STATIC or DYNAMIC:

1 A static drilldown always takes the user to the same view.

2 Dynamic drilldown enables hyperlink navigation to multiple views


from the same hyperlink field, depending on the value of a field in the
applet's current record.

8. Toggle
a. 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.
There are two types of applet toggles, static and dynamic:

■ Static applet toggles. Allow users to toggle between applets by


selecting the name of the applet from the Show drop-down list.

■ Dynamic applet toggles. Automatically toggles between applets


based on the value of a field in a parent applet

9. Association Applets
a. Association applets are used with pairs of business components that
have a many-to-many relationship. Association applets can be invoked
from master-detail views or from MVG applets. They allow users to
associate a parent record with one or more children through an
intersection table.

Association applet presents the user with a selection list of available


detail records. If users see the desired detail record in the selection list,
they choose it. If not, they have the option to create a new detail
record.

In the context of a many-to-many relationship, creating a new


association for an existing detail record is called association; creating a
new detail record and an association is called addition. Both
association and addition of detail records result in the creation of a new
row in the intersection table.

10. Invoke Business Service/Workflow Process (via ProcessName = Workflow


Process Manager)

We can invoke a business Service through

1. Runtime Events
2. eScript
3. User Property

• Runtime Events

To call a business service through runtime events

Enter the following information in the Action Set that you are creating

Business Service: Business Service Name


Business Service Method: Method Name
Business Service Context: “Input Argument”, “Value”

And based on the Event that you choose this business service will be invoked

• eScript

You can use the following Code to invoke a business service from escript

var svc = TheApplication().GetService(”BS Name”);


var Input = TheApplication().NewPropertySet();
var Output = TheApplication().NewPropertySet();
Input.SetProperty(”Type”,this.GetFieldValue(”Status”)); // Input Agruments
svc.InvokeMethod(”BSMethod”, Input, Output);

• User Property

You can use named method property to invoke a business service from BC but
this method is rarely used as it including complex conditions in the User
property might not be possible. But it can come quite handy if you just want to
invoke BS based on simple conditions

Name: Named Method 1


Value: “New Record”, “INVOKESVC”, “BS Name”, “BS Method”,
“‘Input Agrument’”, “Value”, “‘Input Argument 2’”, “Value”

11. Spooling
a. By Spooling means logging a file which store the sql script and help us
in finding the error which has been occurred during transaction.
b. 2 Environmental Variables
i. SIEBEL_LOG_EVENTS
ii. SIEBEL_LOG_DIR
c. Setup spooling in tools/shortcut (/s "c:\spool.txt")

12. Performance Best Practise


a. Database query
i. Analyse slow running SQL (>1 sec) execution plan (Ctrl-L)
ii. Create index on new extension columns and foreign keys if
necessary
iii. Avoid all mode sort (e.g. PDQ with sort spec)
b. Calculated field
i. Disable querying and sorting on calculated field (DisableSort
user prop, BC PreQuery function)
ii. Disable wildcard search (DisableSearch user prop)
iii. Use EXISTS rather than aggregated functions (i.e. SUM,
COUNT)
c. DVM rule
i. Current Validate button requires fields to be “Force Active”
ii. Keep test expression simple in IIF statement
d. eScript
i. Consider Requery vs Force Active
ii. Keep PreCanInvokeMethod simple. Consider error message on
save rather than greying out buttons
iii. Avoid Delete, set foreign key column to “No Match Row Id”
e. Workflow
i. Consider executing long running workflow in Batch mode or
by Workflow Policy
f. Picklist
i. Set Long List property = Y if picklist returns large result set
(>30)

13. EIM vs EAI


a. EIM is a part of EAI and is used to transfer data from siebel to other
databases and viceversa. EAI is Enterprise Application Integration
means integrating two applcations i.e. siebel and .net application or
siebel and sap

14. If we run a workflow process through Administration – Server


Management > Jobs or using “Workflow Process Manager (Server
Request)” it will be executed in Asynchronous mode

If we run Workflow process through BS “Workflow Process Manager” it


will run in Synchronous mode.

Difference between Asynchronous and Synchronous mode:

• Asynchronous mode means that user does not have to wait for
process to complete. He will get the control back after submitting the
request and Server will execute it later.In Synchronous mode user will
get the application control back only, when the execution of the
process is complete.

• In case an error occurs while running the asynchronous


process user will not get any error message and workflow will go in
Exited state.In case of error in Synchronous mode, error message is
displayed to the user (unless it is explicitly suppressed through error
handling)
15. M:M link
a.

You might also like