Greetings, Focalpointers!

I am trying to set a variable as global from a list box selection in the first tab of my html & access it in filters through out my fex's in other tabs in a SINGLE browser session.

I am having multiple tabs (tab control) in a single html & each tab defaults to a html of its own & each htm has like 4 frames running graphs/reports.
I can access my set global var in all the procedures of the first tab , but not in the other tabs.

I've verified that the ibi_persstant setting is set to yes.

I've referred through the documentation resources & previous FP posts & everything seem to be indicating that my global var should last through out the browser session. What am I missing here? Please suggest!

This message has been edited. Last edited by: FP Mod Chuck,

Since HTML objects can only populate local variables, how are you setting the value in your global variable?

list box sending a local var to a fex on submit & am setting the global var in one of the procedures with in a frame.

Thanks.

So the users will always open and run the procedure in the first tab before going to any of the other tabs? It would be interesting to -DEFAULT the global variable before opening your first HTML page and then check it's value after running the procedure in the first tab and opening one of the other tabs.

Hi Dan - Thanks for writing in.
Yes, the users would always start/go to the first tab to change the client (& set the value for global var)
I've checked by defaulting it in the procedure before the first tab gets loaded it. the default val does get picked up in the procs of the first tab & even change when the value is set again.
it. when i go to the second tab...the default value is seen but not the changed val.
I am also reloading the second tab on click to verify it's not picking up the value from the first tab.

After thinking about it, each HTML launch page probably does open a separate session (a new call to the WebFOCUS servlet). You could try passing the value of your global variable to subsequent tabs by adding it to the HTML form that calls the WFServlet (some variation of the sample below) in those other tabs. A hidden local variable (name of your chosing) can be created with its value set to the global value, which will be passed to the servlet along with any other values from the HTML page.

<FORM name='....' action='/ibi_apps/WFServlet' method=..... >
<input type='hidden' name='IBIMR_domain' value="..../......htm">
<input type='hidden' name='IBIMR_action' value="MR_RUN_FEX">
<input type='hidden' name='IBIMR_sub_action' value="MR_STD_REPORT">
<input type='hidden' name='IBIMR_fex' value="app/......fex">
<input type='hidden' name='IBIF_ex' value="app/.....fex">
<input type='hidden' name='IBIMR_flags' value="">
<input type='hidden' name='IBIMR_folder' value="">
<input type='hidden' name='IBIMR_defer' value="">
<input type='hidden' name='IBIMR_random' value="">
<input type='hidden' name='USERACTION' value="">
<input type='hidden' name='LOCAL_VAR' value="&&GLOBAL_VAR">       <------------ add this

This message has been edited. Last edited by: Dan Satchell,

Thanks for that suggestion Dan, I'll try it out!
Best Regards & Have a great week-end!

global variables can be set in the startup file
you can add many...

I use some like previous workday, yesterday and things like that

That's true Frank, but as the profile gets executed as the first part of the FOCUS session the "global" variables get set each time a new fex is executed, so whilst we perceive them as persistant .......

Kal,

You might have to look at setting local cookies and their retrieval.

T

I've tried adding the hidden variable as Dan suggested along with trying to assign the changed global var back in the server profile...but still not able to get it to work yet..
Thanks Tony for your indication- Though hoping for another route, I've started to look at taking the cookies retrieval path.
will post back the progress..
Thanks for the help.

Hi Kal,
I've had success saving amper variables as session variables. Session variables are set and reset in site.wfs. They can be used in focexecs and passed to maintains. Some of my past posts to focal point contain this technique.

I must run now but can detail this technique, if you are interested.

Please advise.

Nick

Dr Nick, please elaborate.

Thanks,

Hi,

In my application, we post the userid of the person entering the system from the portal to WebFocus. A focexec is also called from the post statement. Since all focexecs call site.wfs, I have an "if" statement identifying the first or subsequent pass of site.wfs.

The first time sets the session variable and subsequent passes retrieve the session variable. In each cases, a focexec is called setting the local variable to a global variable using the statement "-SET &&ID = '&ID.EVAL';".

The global variable can now be used in a focexec.

In a Maintain, COMPUTE a variable as follows:
"COMPUTE ID = IWC.GetAppCGIValue("ID");" and test for a null value. If null, the values was not passed.

Hope this helps.

Nick

Hi Kal,
I faced a similar issue regarding dropdowns and passing the selected value to some other fex. i worked for sometime and realized that if i store the value from the dropdown to a global variable,and call the global variable in some other fex which uses that value to filter and stuff like that.it just works fine.
I dont know whether this will help u.
I tried sending it through forms but with no luck.

My global variable persists even if i close the browser and open it back. it still holds the value i selected last time.

Thanks
Badri

I found that explicitly calling -EXIT in a fex procedure erases session-global variables. I consider that a bug and have opened a case. Just in case anyone else runs into this.

We were using an && variable to pass on some session data through drilldowns, but sometimes the && variable was suddenly not set anymore. At first we suspected session time-out, but it was happening too soon for that. Replacing a few -EXIT statements with -GOTO :END and a -:END label at the end of each procedure resolved the issue.

The -EXIT in the procedure terminates the procedure and prevents the global variables from being written back to the .tmp file in your webfocus\temp folder associated with your browser session.