gotcha!
Whenever you wish to use an external script such as browser script (which IS external because it runs in the browser) to call a method of a Siebel Business Service, you have to declare this Business Service so that the application accepts the call.
This is a security feature which has been introduced in Siebel 7.5.
Because otherwise any script kiddie could inject javascript code into the Siebel Web Client, call any Business Service and wreak havoc.
Most of you are familiar with the odd entries in the applications .cfg file
ClientBusinessServiceN = Name of the Business Service
(where N is a sequential number)
(where N is a sequential number)
However, during some upgrades to Siebel 8, things went bump in the night.
That is, their browser scripts didn't work anymore, and adding the line to the .cfg file didn't help either.Here is the solution, and it is in fact related to the year-long effort to get away from text files to configure server components. So since Siebel 8 you have to declare the Business Services which you would like to call from external scripts as an Application User Property.
Migration is rather easy, because they have the same syntax as in the .cfg file.
As you can see in the screenshot below, also PDQDisabledViewN made it into the Application User Props.
