When such a thing happens on sucha large scale, or when we know the exact pattern whereby we can detect these duplicate records in the system, we may look at options to automate the process of Merging Records. How nice would it be if we could just somehow put it all up in a workflow or script which would achieve the above objective.

Exploring further on the topic, I came to realize that there is an undocumented BC method which we may fire to achieve the objective above. Try looking at the script below:

var Target_Id = “Dummy-001″;
var Source_Id = “Dummy-002″;
var bo_Contact = TheApplication().GetBusObject(”Contact”);
var bc_Contact = bo_Contact.GetBusComp(”Contact”);

bc_Contact.InvokeMethod(”SetAdminMode”, “TRUE”);
bc_Contact.SetViewMode(All);
bc_Contact.ClearToQuery();
bc_Contact.SetSearchSpec(”Id”, Source_Id + ” OR ” + Target_Id );
bc_Contact.ExecuteQuery(ForwardBackward);

if (bc_Contact.FirstRecord())
{
while (bc_Contact.GetFieldValue(”Id”) != Target_Id)
{
bc_Contact.NextRecord()
}
bc_Contact.InvokeMethod(”MergeRecords”, Source_Id);
}

If you notice carefully, we have invoked the method, “MergeRecords” on the Contact BC. The Contact BC has the class, “CSSBCContactSIS” which definitely, thus, supports this method. My guess would be that this method would be supported for all the BCs, where the vanilla Edit -> Merge Records functionality is enabled for the corresponding views. I haven’t actually gone further than this.

If somebody has had any other experience with Merge Records, please do share!

Related posts:

1. Siebel – Merge Records – Checklist
2. Siebel – Merge Records Functionality
3. Siebel – Looping multiple records – Update records
4. Siebel – EAI Siebel Adapter – Looping Multiple Records
5. Siebel – Looping Multiple Records – III

Here is another such Business Service that I came across the other day, “FINS Teller UI Navigation”. It has the following methods (my uncalled personal analysis is mentioned herewith):

1) CallBusSvc
This takes in only one Method Argument, “Method Argument”.
After trying to work out as to what this one could possibly mean, I promptly noticed the comments by the kind developer, “A general purpose business service wrapper to be called from Command objects”. After this, I guess we can give it a pass!

2) GotoView
A very powerful method as I see it. It automatically forces a particular view on the User. I see it very useful from security point of view, in redirecting the user to a specific view, in case he dares enter the forbidden territory. Mind you, Siebel’s in-built Access Control mechanism and other security armour makes this seem almost trivial. This could also be a big help when designing help, to automatically navigate the user to a specific Siebel View.

It takes in the following two Input Arguments:
BusObj, and,
ViewName (mandatory)

3) RefreshCurrentApplet
This is a very powerful method provided, and I guess, the most important one. It takes in the following Input Arguments:
Refresh All!!

It will refresh the current context of the Applet. We have already covered this method in detail previously. Click here.

Related posts:

1. Siebel – FINS Industry XML Query Service
2. Siebel – SIA BC Utility Service – Loop multiple records
3. Siebel – SIA BC Utility Service – Invoke BC Method
4. Siebel – SIS OM PMT Service
5. Siebel – EAI Siebel Adapter – Looping Multiple Records

Well, here it is. The “FINS Industry XML Query Service” in Siebel does just that. I am covering this here because of lack of documentation on the same by Oracle, and the immense use that this can be put to. This BS can save you a lot of headache of writing custom scripts to parse the entire XML Hierarchy in Siebel eScript, which can be a real pain in the neck.

This blog post will target the detailed usage of the BS, “FINS Industry XML Query Service” in Siebel CRM. This BS can be used directly in a Siebel Workflow, since this is vanilla. No scripting is needed which is as per the recommendations of Siebel Best Practices.

To catch the implementation details of this BS, log into Siebel Tools, query for “FINS Industry XML Query Service” in the Business Services in Object Explorer.

Business Service: FINS Industry XML Query Service
Method: Execute
Input Arguments: XMLHierarchy
Output Arguments:

Please note that this BS takes only the XMLHierarchy type of Hierarchy input. So, in case you have some other hierarchy available in your implementation, you would need to convert it into XMLHierarchy. I can suggest one of the following in this case which mostly save the day:
EAI XML Converter
XML Hierarchy Converter
EAI Integration Object to XML Hierarchy Converter

There is already sufficient documentation for the above.

Now that you have the XML Hierarchy available, you can feed this into the service, “FINS Industry XML Query Service” as an input from a Worfklow Process Property, in the Input Argument, “XMLHierarchy”.

Create a new Input argument. Let’s call it “TestProperty”. Set the Input Type as “Literal”.
In the Value column, you need to pass the location of the tag in the entire hierarchy, from which you wish to extract the value. This location is specified in terms of the XML XPath notation, or the more commonly called Dot Notation. If the tag in question exists only once in the entire length of the XML, we can set the XPath as, “.//” which we used in our example. In case of repeating tags, use the notation, “.///“.
You can further create new Input Arguments as above, to extract multiple values from multiple tags at the same time.

Now that the inputs have been provided, we need to set the output arguments from this BS in the workflow.
Create a new Process Property by the name, “TestProperty”. (I have named this same as the Input Argument just for the ease of use. You can always select a different name).
Create a new “FINS Industry XML Query Service” BS Output Argument, and set the following values:
Property Name: TestProperty
Type: Output Argument
Output Argument: TestProperty (Please note that this value must be same as the name given to the Input Argument above.)

Now, you are ready to go. Simulate this workflow to see the Output arguments being extracted from the input XML Hierarchy in the Watch Window during simulation.

One of the limitations that I have come across for this BS is that it cannot fetch value from a tag in case of repeating instances of ICs in the same XML, typically a case of repeating instances of child objects with the same tag name.

Let’s have cleaner Siebel, better Siebel. Let’s aim for Scriptless Siebel.

Related posts:

1. Siebel – FINS Teller UI Navigation
2. Siebel – EAI Siebel Adapter – Looping Multiple Records
3. Siebel – SIA BC Utility Service – Loop multiple records
4. Siebel – SIA BC Utility Service – Invoke BC Method
5. Siebel – SIS OM PMT Service

“Every now and then, there comes about a thought powerful enough, to make me sit straight in my chair and start hitting the keyboard!!” – Nitin Jain

When I first looked at this problem statement on one of the public forums, it got me thinking. I had already been thinking about it for some time, just that wasn’t really implementing the possible solution to this. In this blog post, I will demonstrate how I read the data from the Siebel SRF, and exposed its objects to me.

I did this with the Business Services which are from one of the objects that you generally compile from Siebel Tools into the Siebel SRF.

I noticed that Siebel generally accesses all objects in the Siebel SRF using special Business Components (dare I call them virtual!!).
For accessing the Business Services, it uses the Business Component called, “SRF Service”. From my experiments, it seems that this Business Component returns the list of all the Business Services compiled into the SRF, and also, those that are present in Siebel Web Client.

Similarly, siebel uses the BC, “SRF Service Method” to get the list of all the available Business Service Methods from the SRF.

I noted that these Business Components are not mapped to any particular Business Object in Siebel. So, for my experiments, I created some custom Business Objects using these Virtual BCs exposing the Siebel SRF functionality. After creating Applets, Views, etc. you can see what I ended up with in the image below:

Siebel SRF - List of all BS

Similarly, for all the different entities in Siebel Tools, which upon compilation go into the Siebel SRF, Siebel has exposed the list through these Business Components. You can see the complete list by typing out, “SRF*” against Business Components in Siebel Tools.

Let me know what you think about it. You can add your comments to this thread.

From when I started working on this problem, I got this within the first 10 minutes. So, I guess this is very very limited and there must be much more. I would appreciate if people with better insight could add to the understanding for all of us here.

“Knowledge is the only thing in the world which grows by sharing”. So, “Let’s Share!!”

Related posts:

1. Siebel – About SRF Window – Remove data
2. Siebel – Autosave Opportunity data – The concept
3. Siebel – Autosave Opportunity data – Sample Code
4. Siebel – Run Case Insensitive queries
5. Siebel – Unable to check out objects