Siebel REST API Interview Questions

Question 1 : What are REST APIs? 

Answer: REST stands for Representational state transfer. It is a protocol for data transfer using HTTP methods.

Usually REST API uses JSON format to communicate as it is simpler and lightweight than XML.

Siebel Integration Interview Questions - JMS Transport

This article only covers Siebel integration interview questions related to EAI JMS Transport , see Siebel EAI Interview Questions for other Integration interview questions.

Question 1: When should JMS be used over web services in Siebel integration requirement?

Answer: JMS queues are based on store and forward guaranteed delivery mechanism. That means source system sends the message to middleware which holds the message in queue until Siebel server reads it thus message is never lost.

However on other side web services doesn't have retry mechanism in architecture. In case of heavy load or server unavailability message can be lost if source system can't resend it. Benefit of using web services is that they are faster to develop, setup and maintain.

Question 2: How does JMS integration works in Siebel?

Answer : Siebel has JMS receiver server component which can pull XML messages from JMS queue for data transfer. For JMS components to get messages from JMS server Siebel needs to have JAVA installed on Siebel server.

Question 3 : What is the difference between queue and a topic of JMS?

Answer: Queue is is implementation of first in first out data structure, and can be used only between one source and one consumer. Once XML message is consumed by consumer it is deleted from the queue.

Topics also have queue like store and forward mechanism but with the difference that they do not delete XML messages immediately after it has been read, the same message can be read by another consumer (application). Thus well suited for 1 to many integration scenario.

Questions 4 : What steps are involved in JMS component setup in Siebel?

Answer:  Siebel JMS setup involves minimum three items :
- Setup of JVM (Java) subsystem
This tells where is Java files and server details of JMS server.
- Setup of JMS subsystem
This contains queue or topic information
- Setup of receiver component
This component pulls XML messages from JMS server mentioned in JVM sub system from queue mentioned in JMS subsystem.

Question 5: What is jndi.properties file? What it is necessary?

Answer: Java subsystem required for JMS integration required JMS server location information such IP address and port. This information is kept in jndi.properties file in Siebel filesystem.
It looks something like this: https://docs.oracle.com/javase/jndi/tutorial/beyond/env/src/jndi.properties

Questions 6: what kind of logging is available for JMS transport?

Answer:  EAI JMS Transport  provides two logging methods, first one is the traditional Siebel logs which can be turned on by increasing log level of receiver component.

Second type of logs are Java logs which generated by Java virtual machine installed on Siebel server , they can get turned on by setting VMOptions in Java subsystem.

See more Siebel EAI Interview Question

Siebel EAI Interview questions - Web services

View latest 2020 Interview questions here:
Siebel REST API Interview Questions
Siebel EAI Interview Questions - JMS Transport

Question 1: What is the difference between outbound and inbound web services?

Answer: Inbound web services are hosted/served by Siebel and is invoked by external application to send data or to query data from Siebel.

Siebel Inbound Web Service

Outbound web services are web services which are hosted by external applications like SAP or Middle-ware and is invoked by Siebel workflows/business services to send or query data from external system.

Siebel Outbound Webservice

Question 2: What is WSDL?

Answer: WSDL stands for Web Service Definition Language. It's a standard for describing web service end point, it contains information about what all methods external system can call and what are input and output arguments for the service.
For Inbound web services Siebel dev team needs to provide WSDL, which is created from Adminstration Integration> Inbound Webservices view.
For outbound web-services external system like a billing system provides WSDL which is imported into Siebel.

Generate WSDL in Siebel

Question 3 : How WSDL is imported into Siebel?

Answer : Siebel inputs WSDL in two steps. Firstly WSDL is imported into Siebel tools which creates proxy business service and IOs for arguments.

WSDL Import in Siebel Tools

Second step involves creating web service end point in Administration integration> outbound web service which is done by imported by xml generated in first step.

Question 4 : What is filter business service in Siebel?

Answer: Filter business service is a custom business service which can be configured to be invoked at web service invocation just before or after actual workflow call. This service is used to handle custom soap headers of web service .

Question 5: What is SOAP Message? Which version of SOAP is supported by Siebel ?

Answer : SOAP Stands for Simple Object Access Protocol it is a XML format which exchanged by web services, SOAP 1.1 is supported by Siebel.

Question 6: When would you recommend using web services over queue based integration?

Answer: Web services should be used when business process can not wait for response from external system. For example : Order can not proceed without checking the inventory and user cannot wait before submitting order.

Question 7: What is the difference between EAI HTTP Transport and web services?

Answer : Web services is a HTTP based standard which uses WSDL to describe structure of input and output arguments and methods which can be invoked on server.
HTTP Transport can also be use to transfer data in and out if Siebel server however there is no description of input and output data structure and types.

Question 8: Can workflow be published as inbound web services?

Answer: Yes workflow and business service both can be published as web service in  Siebel.

Question 9: What is proxy business service in Siebel? and How does proxy BS works internally in Siebel?

Answer : Proxy business services are business services in Siebel which are created for each WSDL import in Siebel tools. Proxy business service converts in the input arguments into SOAP message and invokes HTTP transport to send data to external system.

Scenario based Interview Questions - Part 3

This is the third post in series of Scenario based Interview Questions . I would highly recommend you to read the first two parts of this series.

 Scenario based interview questions Config - Part 1
Scenario based interview questions Workflows - Part 2

If you like the questions and would like to see more like this, then please +1 this post on google.

Scenario based Interview Questions - Part 2

This is the second post in series of Scenario based Interview Questions . I recommend you to read first post of this series where we discussed Siebel Configuration Interview Questions before going through this post.

If you like the questions and would like to see more like this, then please +1 this post on google.

Scenario based Interview Questions - Part 1

Long ago an avid reader of the blog requested me to post some scenario based interview questions, and sent some good samples as well. I asked the same on siebel-developers slack community and got some really good answers. This is a three post series so stay tuned for next two posts.

If you like the questions and would like to see more like this, then please +1 this post on google, and don't forget to share your answer in comments below.

Siebel Open UI Interview Questions plus bonus jQuery tips

Question 1 : What are different layers of JavaScript classes in Open UI ?

Answer: Siebel Open UI framework provider 4 different type of js files , proxy, presentation model(PM), physical renderer(PM), and plugin wrapper(PW). Out of these only PM, PR and PW are recommended to modify and extend. Proxy is an interface between Siebel server and browser, thus should never be changed.

Siebel Open UI Architecture

Read more

What are the limitations of Siebel Workflows?

This question was asked by one of readers of this blog, and it quickly got me intrigued to research for answer. While doing research I compared the capabilities of Siebel workflow vs Siebel scripting, and got amazed with results.

I started of by listing things which I thought wont be possible in workflows however I got surprised with its capabilities as I dig deeper. I am classifying results as Myths, Facts and Limitations.

Myths

Myth 1: Run time events doesn't work from workflows.

Absolutely wrong, runtime events are tagged to bus comps and work the same in workflow as they work on UI.

Myth 2: Can't update read-only fields in workflows.

One might think that as it is not possible to set admin mode to true in workflow thus it wont be possible to update read only fields. But that is simply a myth.The fact is that there is no need to set admin mode to true in workflows, read only user properties are inactivated for workflows all the time!

Myth 3: There is no way to associate and disassociate records of MVG BusComp in workflows.

If Siebel operation is used on detail bus comp, delete operation acts like dis-associate and insert like an associate.

Myth 4: Workflow can not query based on calculated fields.

Not True. Siebel Operation search spec can be created using Calculated fields, however be cautious of performance impact in case you plan to use calculated fields in search spec.

Facts

Fact 1: Cannot query on child BC directly in Siebel workflows. Workflow always queries Primary bus comp first.

True, however I don't consider it as limitation as one can create workflow based on a different BO which has child bus comp as primary buscomp, and there are many business services available which can query data from another BO without creating another sub process.

Fact 2: There is no way to change primary record in MVG in workflows.

This one I am not too sure about, would like to know from the experts, how they have overcome this problem.

Limitations

Limitation 1: It is not possible to change view mode in Workflows?
Siebel Operation step always queries database with "All View" view mode there is no way to change this pragmatically.

Limitation 2: It is not possible to pass variable by reference in to a workflow.
This seems to be the minor limitation of the workflow, however it does not limit the capability or usage in anyway.

Limitation 3: There is no native way of executing Clib functions in workflows.
There are lot of functions available for execution in workflows however Clib is not one of them. Thus if there is a need to call Clib function through workflow you will have to call a custom business service.

Limitation 4: There no native way to execute methods on application or BC level.
Agreed as limitation unless someone suggests any way out. Some BusComps exposes some methods that can be executed only with scripting. For Example: 1. RepriceAll Method on Quote Item and Order Items. 2. GetFile Methods on Attachment Buscomp etc..

 

Limitation 5: It is not possible to set sort spec on Siebel operation?
This seems to be the only glaring Limitation of workflow/Siebel Operation that Siebel operation does not contain any way to query based in a sort spec. Arguably one can say sort spec can be specified on bus comp, however it wont be wise to clone buscomp just to change the sort order. Would like to know what readers think?

I don't believe that this list is complete in anyway, hoping to get some answers from community. Please feel free to contribute your thoughts on this topic, would be more than happy to be proved incorrect on the points above.

Download Siebel Interview Questions - PDF

I have published all the Siebel Interview Questions in a easy to read PDF e-book  format, it will be available for download freely.

To get the download link, register your email and leave a comment below.

Siebel Interview Question eBook

Siebel Interview Question 2015 PDF  Contains interview questions on :

Siebel Workflow
Siebel EAI
Siebel Configuration
Siebel Scripting
Siebel Open UI

Updates to PDF will only be sent to registered readers. After registering with email do not forget to leave comment below and plus one on google to receive the link.

Get Download link:

How to interview a Siebel Resource?

Originally posted on blog.notesonsiebel.com on March 26th, 2007 by stuandgravy

I’ve interviewed a bunch of Siebel techies and have evolved a few favourite questions, all based around the same theme: attempting to uncover technical breadth while avoiding obscure ‘gotcha’ questions. Things like this:

Q: How would you update a second field every time a first field is changed?

This is a great question: simple enough that a junior dev straight out of a tools course should come up with a few options and have some idea how they weigh up, but broad enough that a senior techie can lead you into detailed discussions about performance vs maintainability, good practices, upgrade issues, etc etc.
If the candidate’s running out of steam, leading questions can coax them toward more inventive answers.

For instance:

• What if the second field is in a different business component?
• What if there are multiple fields to be updated?
• What if the second update needs confirmation?
• What if the update still has to happen for batch (EAI/EIM) updates?

To the answer: I reckon the following is not a bad list to cover-off, but there’s still a few missing…
User Properties
+ minimal config
+ real time
+ robust (mostly!)
- limited
- require srf update

Runtime Events to Workflow Process
+ most things possible with native, compiled Siebel Operations
+ declarative, flexible, upgradable without srf update
+ long-running workflows for multiple consecutive events
+ real-time, optional asynchronous
- no loops (almost) without custom business services
- overhead of instantiating the workflow first time (then cached), which can have a big impact on mobile users

Server scripts
+ simple to write
+ low overhead
- not declarative, requires srf release
- higher level than vanilla C++ services (so slower, in theory)
- limited possibility to interact with the user


Browser scripts
+ opportunity for full manipulation of DOM, real-time interactivity
- maintenance headache (generating script, keeping versions current)
- interpreted at run-time (so slower, in theory)
- limited speed, memory space etc

Workflow Policy to Workflow Process
+ fully robust database-level trigger
+ fully asynchronous
- not real time, interactive
- not declarative, requires DBA maintenance

How to build Siebel Workflow Expression?

I remember my days when i started with Siebel, I just couldn't get the syntax of workflow expression correct. I still see newbies of siebel struggling to get it right the first time. In this post I would try to make the basic rules of workflow expressions as simple as possible.

Basic Rules of Siebel Workflow Expression are :

1. Siebel Workflow takes String as input.
2. + (plus) is the concatenation operator.
3.  Process properties can be referred using & operator like this > [&Object Id] 
4.  Don't worry about spaces in process property names, they are allowed.

Let's take an simple example where we want to build the expression to search for records with Contact Id specified in Object Id the search spec would be:

if Object id contains : 1-12345 then expression will be evaluated as :

Did I say its a H.U.G ?

See what is the difference between Expression Business Component and Filter Business Component


Hope it helps. If you know similar topic and want to share with Siebel community, please post it in comments below. I will post it as blog post.

Siebel Open UI Interview Questions

Read Latest Open UI Interview Questions here.

What is Siebel Open UI?

Answer: Siebel Open UI is HTML 5 based Siebel High interactive client which is released by Oracle to replace older Active X based HI client. It is available in Siebel CRM from version 8.1.1.9 onwards. The name derived from Open source JavaScript libraries which it is based on.

Siebel Open UI

It is fully HTML 5 compliant user interface, which is based on jQuery and jQueryUI frameworks. It does not uses any active x component thus it can be accessed using any HTML 5 compliant browser like chrome, safari and Firefox along with latest Internet explorer.

Question : How to enable Open UI in Siebel?

Answer : To enable Open UI create new application object manager and set following parameters

Enable Open UI = true
HighInteractivity =true

Siebel Open UI exists parallel to existing Siebel clients. It references same srf and database and shares the same object definition with High Interactive application. 

 

Question: What are major customizable components of Siebel Open UI ?

Answer: Open UI can be customized extensively with help of jquery classes(known as presentation mode and physical renderer), which can override the default behviour of controls and can mash up with other HTML widgets.

 

 Question: What is the difference between presentation model and physical renderer?

Answer : Physical renderer is JavaScript layer in Open UI stack that is responsible for building the UI and showing the data. It communicates with presentation model to fetch data.

Presentation model is second layer which maintains the data state in Client. All the events and methods(such as delete record, write record or update record) are managed by PM layer. It communicates with proxy layer to get and set data on server.

 

Question: What is the difference between the PM of List applet and Form Applet?

Answer: Class of PM Layer is of list applet is different from Form applets and is extended as : 

SiebelJS.Extend(CustomClassName, SiebelAppFacade.PresentationModel); for form applet

and List applet uses SiebelJS.Extend(CustomClassName, SiebelAppFacade.ListPresentationModel)

Recommended way to customize PM and PR layer is use code creators
Duncan ford template generator 

 

Question : How to access Applet's Client User properties in Presentation Model?

Answer: Client user properties specified in siebel tools can be retrieved in Siebel Presentation Model JS by accessing the constants in the Setup method. Example:

CustomPM.prototype.Setup = function (propSet){
var consts = SiebelJS.Dependency("SiebelApp.Constants");
var apm = propSet.GetChildByType(consts.get("SWE_APPLET_PM_PS"));
var value = apm.GetProperty("User Property1");

Question: Does open UI support browser script events defined in tools?

Answer: Yes open UI supports browser scripts specified in tools. All the browser script events are supported. In addition to those events Open UI supports presentation model and physical renderer js class files to leverage HTML 5 capabilities.


Recommended Reading from Bookshelf:
Deploying Open UI
Configuring Open UI

Read for More Open UI Interview Questions - New

Siebel Interview Questions : Scripting

See collection of Date functions in Siebel eScript

Siebel Scripting is one the most interesting areas of Siebel, if it is done properly it can do wonders for business, otherwise it can lead to ever increasing technical debt.

Siebel Tools Scripting IDE

Before jumping to questions let us look at some lessor known facts of Siebel Scripting:

1. Siebel support two scripting languages: eScript and VBScript
2. Full name of eScript is ECMA script which developed further to become javascript. 
3. Garbage collection of Siebel scripts in not automatic
4. Siebel eScript does support prototype overriding and classes
5. Siebel eScript can pass arguments by value and pass by reference

Question: Which Siebel objects supports scripting?

Answer: Script can be written on following objects in Siebel:

1. Business Services
2. Client Side Business Services
3. Business Components
4. Applets
5. Application
6. Product Configurator Events
7. Smart Scripts
8. Workflows (via business services)
9. Open UI js class files
10. Browser scripts on Applets, BusComps, Application, Business Services
11. Siebel Webtemplates SWTs
12. ?????

Question : How to change primary record of MVG using scripting?

Answer: Primary record of MVG can be changed by setting the SSA Primary Field of the associated record. 

Script could look like:  

        bcOpty.ClearToQuery();
        bcOpty.ExecuteQuery();
        if(bcOpty.FirstRecord())
        {
            var bcMVG = bcOpty.GetMVGBusComp("MVF Name");
           bcMVG.ActivateField("SSA Primary Field");
            bcMVG.ClearToQuery();
            bcMVG.SetViewMode(AllView);
            bcMVG.SetSearchSpec("Id", "1-12345");
            bcMVG.ExecuteQuery();
             if(bcMVG.FirstRecord())
            {
               bcMVG.SetFieldValue("SSA Primary Field", "Y");
               bcOpty.WriteRecord();
            }
        }

Question : How to set pick list field using script?

Answer:  GetPicklistBusComp() Pick() methods are available in eScript by which system can search on pick list buscomp and pick desired record.

Syntax for pick method can look like:

oPickBusComp = buscomp.GetPickListBusComp("FieldName");
oPickBusComp.ClearToQuery();
oPickBusComp.SetSearchSpec("Id","12345");
oPickBusComp.ExecuteQuery();
oPickBusComp.Pick();
buscomp.WriteRecord();

Question : How to show a confirmation(Ok/Cancel) dialogue box in Siebel?

Answer: Confirmation Dialog box should be implemented through browser script using javascript confirm method. This method prompts users with option to proceed or cancel the process.

Click here for example.

Question : How to call batch file through scripting?

Answer: Siebel provides C libraries to access the host of Siebel server.
Clib.system() is one of those functions which allows script to pass some instructions to command processor of server host.
Using this method, a batch file can be invoked from Siebel which can do OS level changes.
Following instruction can execute Siebel.bat file on the server:

Clib.system("C:\\Scripts\\Batch\\Siebel.bat");

Question : How to update read only fields in Siebel?

Answer: Fields in Siebel are configured as read-only using "Field Read Only Field" and "BC Read Only Field" user properties. These user properties does not work on views where admin mode flag is set to Y.

BusComp.InvokeMethod("SetAdminMode", flag)

Question: What is the difference between SetAdminMode and SetViewMode(AllView)?

Answer :

• SetAdminMode mimics the behaviour of Admin Views, and is used to update read only fields
• SetViewMode instruction changes the default view mode of the business component, it used to access records which are not visible with default view mode.

Question : Is it possible to invoke workflow through browser script?

Answer: Workflow can be invoked through browser script if "Workflow Process Manager" declared as Client side business service in Application's User Property. 

Question : What type of error handling is available in Siebel eScript?

Answer: try catch finally instructions helps to handle run time errors in e-script.

• try block marks the code which needs to handled
• catch block declares commands which should be executed in case of error,
• finally block is executed after try and catch has completed executing.

try
{
   statement_block
}
catch
{
   exception_handling_block
   [throw exception]
}
finally
{
   statement_block_2
}

Finally block is always executed no matter if there was error encountered or not.

Question: How to get language of Object Manager?

var lang = TheApplication().InvokeMethod("LANGUAGE");

Question :  What is difference between ActiveBusObject() and GetBusObject() methods?

Answer: ActiveBusObject is mostly used in UI based scripting requirements, this method can only return the handle of current BO instance.

For example: In Accounts screen ActiveBusObject will return Account BO and subsequent .GetBusComp().GetFieldValue will return the information from the record selected by user.

Same script in Contact Screen will return the Contact BO.

Important Points about ActiveBusObject: 
- It is not recomended to use ClearToQuery and ExecuteQuery on BC of ActiveBusObject as UI context for user will get lost.
- ActiveBusObject is the only way to get BO in browser script.

GetBusObject method should be used when current BO instance does not have the BC of interest. We can get handle of any BO in application using GetBusObject This is mostly used in background processes and workflows.

 

100 Siebel Interview Questions : Workflows : Part 2

On readers interest, creating Part 2 for the post on Siebel Workflow Interview Question, feel free to leave a comment for any specific question that you faced difficulty in answering or would like to know more about any specific area in Siebel.

Question: Is it mandatory to specify Business Object on a Workflow?

Answer: No, Business Object needs to specified only when there is need to use Siebel Operation in Workflow.

Question: What is the difference between Expression business component and Filter business component in Siebel Operation?

Answer: These business components fields are used in Siebel Operation when search spec is built by referencing another business component field.

For Example: To find Account records where Account Id is specified in Contact's Account Id field, expression will be created like :

"[Id] = [Account Id]"

And Filter Business Component will be set as : Account and Expression Business will be set as Contact. Thus it will be evaluated as :

"[Account.Id] = [Contact.Account Id]"

read more on :
How to create Siebel Operation Expression 
Bookshelf: Defining Siebel Operation Search Spec

Question : How to compare two properties in Siebel Workflow?

Answer: Expression on Siebel Conditional branch can be used to compare two properties.  To see how to create expression in siebel workflow please see.

Quiz: How to change the destination field of MVG?

This could be one of the most difficult Siebel Configuration Interview Question, it took me some time to understand it and found it quite amusing. Let us see how many of us could answer this. :)

Requirement: To change the destination field of an MVG. Siebel Provides option to change the source field of an MVG so that child records for some other key field can be fetched.

From Siebel tools help: 

MVG Source field Definition

Source Field (O)
Specifies the name of a source field that Siebel CRM uses to link the child business component with the source business component. The source business component is the business component that includes the object definition for the multivalue link. If the source field is different from the Id, then the Source Field property is required.

Requirement is to change the destination field, please bear in mind the MVG is based on M:M relation using a inter table. 

Update:  Sorry guys to being so late in responding to the comments.


Answer to the question is: Source Field and Destination Field of the M:M links can be modified just like 1: M link. Siebel supports having source and destination fields as well as inter-table on a link, this makes the links most configurable.

I have explained all the links in my latest post : Links Demystified

100 Siebel Interview Questions: Workflows

 You are reading, the most read article of this entire blog. Please share in comments if it helped you, if you would like to any other question to the list. 💙

This article has been added on reader's request, and these are not the 100 questions as of now ( ideally there should not be 100 question in an interview :) ). My intention with this article is to point all the minor doubts of Siebel Consultants regarding workflows. Feel free to suggest any other question on this topic, I will be more than happy to add it to the list.

Question: What are the different ways to invoke workflows in Siebel?

Answer: Some of the known ways of executing workflows are:
1. Named Method User Property
2. Calculated Field expression
3. Script on BusComp, Applet, Application, Business Services
4. Workflow Policy
5. RCR & Server Requests
6. Asynchronous Server Request - Business Service
7. Run Time Events
8. Command line using Server Manager
9. Web services & Receiver components(JMS,MQ)
10. Through Siebel URL 
11. Commands
12. Order Management Signals

Question: How to invoke workflow on specific server?

Answer: Workflows executed through workflow process manager business service are executed on the same server where request is made. Asynchronous Server Request and Server request business service can send request to other servers for workflow execution; this can be done by specifying server name as input argument.

Question: What are different ways of error handling in workflow process?

Answer: There are two ways of error handling in Siebel workflows. Most popular to handle error in workflows are exception branches(the red arrows :) ), they can be created for each step in workflow to handle error for the step.Secondly  we can use Error Process Name property of workflows to call another workflow process to handle in case of any error.

Question: How to configure a workflow policy?

Answer:
1. Ensure Workflow Policy column is created in Siebel tools & Added in workflow policy object
2. Create workflow policy action to execute workflow
3. Create workflow policy record and create conditions and associate action to the workflow policy.
4. Execute “Generate Trigger” task to create triggers
5. Restart Workflow Monitor Agent

Question: What is the difference between Synchronous and Asynchronous workflow execution?

Answer: Synchronous workflow is executed in user session and user has to wait till workflow is executed. Workflow is executed synchronously usually through button click or record operations like set field value or write record, where user need to know the outcome of the workflow.

Asynchronous workflow requests are executed by server in background and does not requires user to wait for the outcome. These type of workflows are usually interface workflows.

Question: What is the difference between Stop step and End Step?

Answer: Stop step sets the status of workflow to “In Error” and End step set the status to “Completed”
Stop steps should be avoided in integration workflows and workflow policies as they may cause server component to error out.

Question: What is the difference between Workflow policy and Run time events?

Answer: Workflow policy adds the workflow execution request to the queue and executes the workflow from server components.
Runtime event executes workflows as and when requested and process is executed in user session user has to wait for the workflow to complete.

Questions: Is it possible to create Workflow without Business Object ? If yes how ?

Answer: Yes it is possible to create workflow without business object. Business Object is not a required field on Workflow. It is only required when workflow need to use any siebel operation.

Question: How to get current date in Siebel Workflow?

Answer:  Property can be populated with current date by using Timestamp() in Siebel Workflow. Syntax of Timestamp in Siebel Workflow.

Question: What is stored in Siebel Operation Object Id when Query method from Siebel operation step returns more than one record?

Answer: Siebel Operation Object Id contains * if more that one records or updated are queried using Siebel operation.

Question: How to pass hierarchical property set from custom business service to Workflow?

Answer: To pass hierarchy from custom business service to workflow, type of property set should be the same as the name of output argument. 

Download Siebel Interview Question eBook

See Part :2 of Siebel Workflow Interview Questions

See more EAI Interview Questions here.

Siebel EAI Interview Questions

Question: How to generate XML in Siebel?

Answer: Use EAI Siebel Adapter Business Service Query method and then EAI XML Converter Service Method HierToDoc to generate XML Doc.

Question What is the difference between External & Internal Integration Object? 

Answer: Internal Integration Object refers to Siebel Business Object for querying and saving data.
External Integration Object refers to XML schema, one can not use query or insert operation on external integration object.
To create external integration object, either XSD or DTD document is required.

Question: How to change the XML tag in an Siebel Message?

Answer :  Find the Integration object from the xml and then go to the desired integration component and update the XML Tag of desired integration component field.

Question: How to change the source field of XML tag in Siebel XML?

Answer : Find the Integration Component Field and update the External Field name to the new field name.

Question: What is the significance of Name of Integration Component Field?

Answer: Name of Integration Component Field is used to create the Siebel Message property set, It is essential to know the ICF name if script is used to get value from XML.

Question: What is the use of XML Container Element?

Answer: XML container element if specified on IC then Siebel adapter will always create an XML tag before the start of child IC records, and it will always be present in XML even if no records are returned by query method.

Question: What is XSD? How to create XSD in Siebel?

Answer: XSD is an XML Schema Definition document. It is a type of XML document which defines the structure of an XML document. It contains the structure of the XML and the data type and length of XML.
Siebel tools can generated by Generate XML Schema wizard by clicking Generate Schema Button.

Question: What DTD? How to generate DTD of an Siebel Integration Object?

 Answer: DTD is Document Type Definition, it is another form of document which describes the structure and data types of an XML document. It can also be generated through Generate Schema Button on the Siebel Integration Object.

Question: What is a WSDL?

Answer: WSDL stands for Web Services Descriptive Language. It is an XML file which describes everything about a web server. 

Typically it contains:

• Web service end point (URL)
• Methods web service Support
• Input and output arguments.

WSDL is technology/platform independent syntax thus it is widely accepted way of describing web services definition.

Question: How to import WSDL in Siebel?

Answer: Importing WSDL in Siebel is two step process.
First, WSDL is imported into Siebel Tools using WSDL Import Wizard. It creates Integration objects and proxy business service from WSDL definition, and generates XML for run time data creation.

Secondly, XML generated  is then imported in to web client. Process is outlined in bookshelf here.

Question: How to convert incoming Data to uppercase before importing in Siebel?

Answer: Siebel does not support changing the case of through EAI, however it is possible to call a custom business service through data maps which can convert the case.

InvokeServiceMethod ("CustomDataMapper", "UpperCase", "InputStr='"+[Integration Field Name]+"'", "OutputStr")

   

See more EAI Siebel Adapter Interview Questions.
See more Siebel Workflow Interview Questions.

Download Siebel Interview Question eBook

Popular Configuration Interview Questions:

• How to fix a picklist field?

• What is the performace impacts of using applet toggles?

• What are different forms of applet toggles?

• What is the difference between Constraint pick map and Copy pick map in Siebel?

• What is the difference between Picklist and MVG?

• How to create a new static picklist in Siebel?

Siebel Configuration Interview Questions - Picklists

This post focusses on the interview questions that are related to picklists fields in Siebel. I have tried to list all the possible questions and will keep updating it in future.

Question: What is the difference between dynamic picklist and static picklist?

Answer:Static picklist always show a static list of values which are store in List of Values buscomp. Values in static picklists can only be modified by Siebel Administrator from Administration Data> List of Values view. Example: Salutation pick list on contact form applet.

Static Pick list in Siebel

Dynamic Pick list in Siebel

Dynamic picklist source its data from user buscomp such as contact, account and product.
Examples:
1. Product pick applet on Order line item
2. Account pick applet on contact form applet

*** Static picklist are generally dropdown and dynamic picklists are configured through pick applet.

Question: How to create a new static picklist in Siebel?

Answer:
1. Create new LOV_TYPE by creating record in Administration Data> List of Values view. Keep:
Type :  LOV_TYPE
Language Independent Code : CUSTOM_PICKLIST
Display Value : CUSTOM_PICKLIST
Language : English-American
Active : Y
2. Create List of values by using newly created LOV_TYPE in step 1. Set the following values:
Type :  CUSTOM_PICKLIST
Language Independent Code : Value1
Display Value : Display Value1
Language : English-American
Active : Y
3. Create new picklist in tools and set:
BusComp :  PickList Generic
Static : Y
TypeField : Type
Type Value : CUSTOM_PICKLIST
4. Associate picklist to the field, by selecting this new picklist on the field. And set the PickMap as:
Field: "New Field Name"
Picklist Field : Value
5. Place the field on to the applet and set runtime=true

Question: What is the difference between bounded picklist and unbounded picklist?

Answer:Bounded picklist allows user to select value only from the list. User can not type in new value into the field.
On the other side Unbounded picklist field can accept values which are not available in dropdown.User is allowed to type in new value and can save the record.

**Both Static and Dynamic pick list can be bounded or unbounded.

 

 

Question : What is the difference between Picklist and MVG?

Picklist allow user to select on value from list of valid values.
Example : Account Field on Opportunity BusComp.

MVG stands for multi value group is used to associate multiple values to a record. MVG show relationship of one entity to other multiple entities.
For Example: Contacts on opportunity, each opportunity record can be related to multiple contacts records, however it can only be related to one account.

 

 

Question: What is the difference between Constraint pick map and Copy pick map in Siebel?

Answer: Copy pick map copies the selected value to the field. This type of picklist shows all the values from the pick list buscomp.

Constraint pick map is used when there is requirement is to limit the values which are shown on UI. Field value of constraint pick map is used to filter values shown in picklist.
For Example:  Contact Field on Sales Order only shows the contacts of the selected account, this is because account id in mapped as constraint pickmap in account.

Question: How Multilingual LOV works in Siebel ?

Answer: When Multilingual LOV is configured, Siebel save LIC (Language independent code) on the database and shows Display value on the UI depending upon the language of the object manager.

For Example: Event Status will show "Zugewiesen" if user is using German application and for same record English application will show value as "Assigned" and the database column will have "Assigned" value.

Multilingual LOV

Popular Interview Questions:

• How to fix a picklist field?

• What is the performace impacts of using applet toggles?

• What are different forms of applet toggles?

• What is the difference between Constraint pick map and Copy pick map in Siebel?

• What is the difference between Picklist and MVG?

• How to create a new static picklist in Siebel?

More to come...

please feel free to use comments to share any question that you had difficulty in answering?

Siebel EAI Interview Questions - EAI Siebel Adapter

Question: Explain the methods of EAI Siebel Adapter

Answer: EAI Siebel Adapter is pre-build business service which interacts with Siebel Object manager to perform CRUD operations on Siebel Database. Following methods are available on the service:

Query

1. Query method is used to query data from Siebel, output of this method is Integration Object instance.
2. Query can be executed using :
1. Row id of the primary BusComp
2. Search spec consisting of parent and child buscomp fields.
3. Integration object instance - which is also known as Query By Example
3. Only required input argument of this method is Output Integration Object Name which is the name of integration object which is queried by the service.

How to create Pick list field in Siebel?

This is one of the most common problem that is faced by new siebel developers. Answer of this question can tell a lot about actual hands on experience of the developer and how much experience he holds in debugging.

There are only few reasons why picklist doesn't work, which can be summarized as below:

1. Pick map of the new field is not populating the foreign key field of the field.
2. Join created to pull the value of the field is not created properly.
3. If no values are shown in drop down then pick list is might not compiled yet, or the LOV type and values are not created in administration views.
4. If value is not displayed after selecting value from pick applet then wrong field is selected in pick map of the field.
5. Update only if null is not configured properly. 

Related Questions:

Question :What are the reasons for field based on picklist not showing drop down or pick applet icon?

Answer: Pick applet might not be selected on the list item or control of the applet or runtime property of the control is set to false.

Please feel free to leave a comment if you have faced any other issue with the pick lists. 

Popular Interview Questions:

• What is the performace impacts of using applet toggles?

• What are different forms of applet toggles?

• What is the difference between Constraint pick map and Copy pick map in Siebel?

• What is the difference between Picklist and MVG?

• How to create a new static picklist in Siebel?