Development in Siebel inevitable results in scripting for one or the other requirement and we end up writing a business service quite often in case of bigger requirements.

I have written quite a few business services myself both on client side and tools side. The biggest difficulty I have faced with business services is testing them, as many of the business services are to be actually call inside workflow which is invoke at the particular value of field or on button click. So, to test them we actually have to go through the whole business process number of times which is quite cumbersome.

Today I am going to share with you the strategy that I follow to test Client Side business services which helps you to avoid actually performing the business process. Simulating a business service can help you to achieve that. As usual I will explain this with help of an example.

We have business service named with following parameters

Name: TestBS
Method Name: TestMethod

This method expects two input arguments Testarg1 and Testarg2

Here is how I can test my business service

  • Goto Administration > Business Service
  • Go To Simulator View
    Siebel Application Business Service View Screenshot
  • Click New Button in Service Simulator List Applet
  • Enter Service Name as TestBS
  • Enter Method Name as TestMethod
    (as shown below)
    Siebel Application Business Service Screenshot
  • Click New Button in Input Argument List Applet 
  • Click on Property Name Pick Applet (as shown below)Siebel Application Business Service Property pick applet
  • Click on New and Enter
    Property Name: Testarg1
    Value to value1
  • Enter the 2nd argument so that you pick applet looks as the screenshot below
    Siebel Application Business Service Property pick applet screenshot
  • Click on OK

You are ready to test your BS now.

Click on the Run button in Service Simulator List Applet and you should see the output in arguments list applet if any or you would receive the error if there are any.

Make sure that you business service doesn’t contain code such as TheApplication ().ActiveViewName or TheApplication ().ActiveBusObject this would result in error.

OkAvarageGoodVery GoodExcellent (1 votes, average: 5 out of 5)
Loading ... Loading ...

Related Posts