Showing posts with label Siebel Browser Script. Show all posts
Showing posts with label Siebel Browser Script. Show all posts

Wednesday, January 27, 2016

Siebel: Dynamically show/hide a control on applet

The best way to do with configuration is using toggle applet.
The other way is to write browser script to achieve the logic.






Below code can be used to hide a form applet control ('AAA')

var vControl = this.FindControl( "AAA" );
vControl.SetProperty( "Visible", "FALSE" );
vControl.SetLabelProperty( "Visible", "hidden" );


Below code can be used to show a form applet control ('AAA')

var vControl = this.FindControl( "AAA" );
vControl.SetProperty( "Visible", "TRUE" ); 
this.FindActiveXControl( "AAA" ).style.visibility = "visible"; 
vControl.SetLabelProperty( "Visible", "visible" );

add a control user property for the control - 'AAA',  with the name 'useLabelID' (no quotes) and the value: 'TRUE' (no quotes).


Siebel: Generate browser scripts using genbscript utility in siebel

genbscript.exe is the utility that is sued to generate browser scripts from the .srf file. This executable is available in the siebsrvr/bin or the client/bin directories.
The syntax to run the command is:

genbscript <application cfg file> <dest directory> [language]






when generating browser scripts on the siebel server, the destination directory should be siebsrvr/WEBMASTER and the cfg file should be from the siebel server like below:

genbscript "c:\siebel80\siebsrvr\bin\ENU\siebel.cfg" c:\siebel80\siebsrvr\WEBMASTER ENU

After executing the genbscript utility, a new folder called <srfxxxxxxxxxx_xxx> is created in the c:\siebel80\siebsrvr\WEBMASTER folder

If deploying to the Mobile Web client, the dest_dir should be client/public/%LANG_CODE% and the config_file should be the appropriate language specific client configuration

genbscript "c:\siebel80\client\bin\ENU\uagent.cfg" "c:\siebel80\client\PUBLIC\enu"

if you are generating browser scripts for non ENU language then the syntax is as below:


genbscript "c:\siebel80\client\bin\FRA\uagent.cfg" "c:\siebel80\client\PUBLIC\fra" "FRA"

after the browser scripts are generated, either bounce the web servers to refresh the files from the siebel server or by Updating Web Server Static Files on the SWSE Using the Web Update Protection Key. more details can be found here

Thursday, July 30, 2015

Siebel genbscript Error: "Couldn't enumerate buscomps "

This Error "Couldn't enumerate buscomps <Initial>" might occur when you try to generate Browser Scripts using genbscript utility in Siebel.
Below is a screenshot of the same error:

The Error usually occurs when you get a fully compiled srf from one environment and try to use it in a different environment.

The error occurs due to missing [DataSources] definition for EBC's defined in the source environment.






Normally, DataSources are defined in the application cfg file in a local db while the same are defined in Administration - Server Configuration > Enterprise Profile Configuration view in the server.

To find the exact missing DataSource, we have to capture the logs for the session running the genbscript.exe

Steps to Increase Log level & find the DataSource name:

  1. Create an Environment variable on the machine where you are running the utility SIEBEL_LOG_EVENTS = 5
  2. Run the genbscript utility to get the error message.
  3. Open siebel.log in the [Siebel root]\client\log directory.
  4. Go to the line for the same error and then navigate to the steps prior to the error message.
  5. You will find the name of the missing DataSource definition.
Next, you need to create a dummy DataSource definition in the application cfg file like below:

Add under [DataSources]

TESTSOURCE = TESTSOURCE (where TESTSOURCE is the name of the missing DataSource from the log file)

Add after [ServerDataSrc]

[TESTSOURCE ]

Now, try running the genbscript utility using the same cfg file where you added the DataSource and it should run fine without any errors.

123Siebel

Search 123Siebel