What do you understand by the term XML Doc?

XML Doc is a XML String containing actual data. We use EAI XML Converter Business service to get XML Doc. In Siebel Inbound Integration we get data in XML string form and in Outbound Integration we send data as XML string. This XML string is referred as XML Doc We can use various methods of EAI XML converter BS such as

IntObjHierToXMLDoc : Used to convert output of EAI Siebel Adapter Query method to XML Doc XMLDocToIntObjHier: Used to convert an XML String into Hierarchy which can be used by EAI Siebel Adapter BS to perform various operations such as Upsert, Delete, Synchronize etc DocToHier: Used to convert XML string to generic hierarchical property set HierToDoc: Used to convert Generic Hierarchy to XML String

What is the Use of Providing BusObject in the Workflows?

Business Objects in workflows help you maintain the context and use Siebel Operation Steps inside workflows. You will not be able to use Siebel Query, Insert, Update step if you dont provide Business Object in Siebel Workflows.

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/

What is difference between Siebel Browser Script and Server Script?

Execution Context:

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.

How to enable a particular child entity?

Question: When Service Request status is set to Closed then everything including all the child entities of Service Request should become read only but user should still be able to attachments. OR When SR status is set to Close all the child entities except Service Request Attachments should become read only. Answer: Service Request and all its child entities become Read Only as result of class based functionality of Service Request. So, we need to override the functionality and enable Service Request Attachment even after the status is changed to Closed. This can be achieved as following: Define Always Enable Child User Property on Service Request BC will the following details: Name: Always Enable Child: Service Request Attachment Value: TRUE

difference between External and Internal IO?

Following are the differences between Internal and External Integration Objects 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

How to invoke Smart Script on click of a button?

We can invoke Smart Script from a button using RunCallScript method of an Applet. For Example on Applet_PreInvokeMethod below given line of code will invoke Smart Script named Test SS

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

RunCallScript Method accepts 4 arguments. 1. 2. 3. 4. Name: Name of the Smart Script to be invoked pathId: Row Id of the Smart Script Language: Language Code 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.

Closing Service Request Scriptless Siebel

Requirement: We have Service Request (Parent BC) and Activities (Child BC) when all the activities are Closed (status set as closed) Status of SR should automatically change to Closed. Scriptless Solution: I thought about the solution on the same lines as described in the previous post of Scriptless Siebel series. Here are steps to achieve that: Workflow Steps:

1. Query for Activities using PRM ANI Utility Service (QueryBusComp

method) 2. Use following Search Spec [Status] <> Closed AND [Activity SR Id] = GetProfileAttr(SRId)

3. Decision Step will have following condition

If Number of Records greater than 0 then go to End else use Siebel Operation Step to Update SR status as Closed

Runtime Event Details: Runtime events details are also very similar to last post, so you can refer to last post for screenshots. Event Detail: Sequence: -1

Object Type: BusComp Object Name: Action Event: WriteRecord Conditional Expression: GetProfileAttr(Me.ActiveViewName) = Service Request Detail View [To limit the execution to just that particular view] Action Set Name: UpdateServiceRequest Action Set Details: You need to create two action records for this action set. One will set a profile attribute and other will call the workflow process Action Details:

1. Name: SRId
Action Type: Attribute Set Sequence: 1 Profile Attribute: SRId Set Operator: Set Value: [Activity SR Id]

2. Name: CallWF
Action Type: BusService Sequence: 2 Business Service Name: Workflow Process Manager Business Service Method: RunProcess Business Service Context: ProcessName, NewServiceRequestUpdateWF