1. There are two type of users, sales user and risk user. The Differentiating factor between them is User Type in Employee table. How can we configure that for risk user the records are editable and for sales user it is not.
2. How can a view be read only for a particular user and editable for the other user?

But in short we need to answer how to make a view read for some users and editable for some users.

Answer:

Create two responsibilities named Sales_User and Risk_User. Assign the view to both responsibilities and for Risk_User responsibility make “Read Only View” flag as true.

Now add sales users to Sales_User Responsibility and Risk Users to Risk_User Responsibility. Now for Risk_User records will be read only and for Sales user records will be editable.

• Siebel Server Scripts are executed in Siebel Application Servers by Application Object Manager (AOM).
• Siebel Browser Scripts are executed at Client Side by Client Browser (Internet Explorer)

Files:

• Siebel Browser Scripts are converted in JS (Java Script) files and stored in PUBLIC\ENU directory.
• No JS files are created for Server Scripts and they are executing using Siebel Scripting Engine either T or ST engine depending of Siebel version.

this.InvokeMethod ("RunCallScript", "TestSS","","ENU","USD");

RunCallScript Method accepts 4 arguments.

1. Name: Name of the Smart Script to be invoked
2. pathId: Row Id of the Smart Script
3. Language: Language Code
4. Currency: Currency Code

You can specify either Name or Row Id of the smart script. It is compulsory to mention at least one of them.

Base Object Type:

• Internal Integration Object has base type as Siebel Business Object
• External Integration Object has base type as XML

 EAI Siebel Adapter – Query Method:

• Internal Integration Object is used in Query Method of EAI Siebel Adapter BS.
• External Integration Object cannot be used with Query method of EAI Siebel Adapter BS.

Creation:

• Internal Integration Object is usually create through EAI Siebel Wizard
• External Integration Object is usually created while importing an External WSDL

1. PickMap is not defined for Field which is showing Picklist values
2. LOV Type and LOV Values are not defined
3. Runtime Flag on Applet level is not true.
4. You have not clicked on Clear Cache after adding the values and trying to see values in same session.

If any of the above mentioned reason is true then you will not see the values in the dropdown of field

When you execute a workflow through runtime event or a user property then the active Business Object context is passed to the workflow which allows workflow to work on any child business component records without actually need to query on the BC.

Below given link will provide an example of such behavior

http://siebelunleashed.com/closing-service-request-–-scriptless-siebel/

P.S: Data Validation Manager (DVM) works similarly using Active BO context

How to pupolate a field with the value of another field whenever a new record is created for the first time?

Answer:

Use Post Default Value property of the field using experssion to populate its value with another field value.

Example:

To populate value of  field “Sub Status” with value in field “Status” I would use  below given expression in Post Default value of “Sub Status” Field

Field: 'Status'

You can read more details about Post and Pre Default Properties from the link given below

http://siebelunleashed.com/pre-default-and-post-default-properties/

We are receiving an XML containing account information from external system. In one of the XML tags “Active” they are going to send Value as 0 or 1 but in Siebel we are need the value of “Active” XML tag as “Y” or “N”. How can you achieve this?
Answer:

Using EAI Value Maps present in Administration – Integration Screen.

We are going to define an Inbound Map and use functions like EAILookupSiebel and Translate methods to get the required values.

Or

When we get an XML from external System. If a record with received data is not present in Siebel then it should be inserted and if record is already present in Siebel then nothing should happen.

Answer:

On Integration Object that you are going to use for this integration, create “NoUpdate” user property with value as ‘Y’ on all Integration Component instance present in that Integration Object.
Use Upsert method available in EAI Siebel Adapter Business Service.

Due to NoUpdate user property if record is found nothing will be updated and if record is not found then it will be inserted.

It can be really handy if you are preparing for interview and work in testing.

You can download it from the link given below
Download: a2ztesting