Session variables carry-over
I have a new application that seems to need a function that doesn't "pop out" at me from the documentation.
I would call it: [b] unSetAllSessionVariables(); [/b]
I'm getting carry over when session variables are set to optional (which they need to be) but we don't want to carry the prior data forward which seems to be the result when a value is discovered in one session, but not in the next.
I think it will work if I create individual "[b]session.setVariable("MyVar1", null);[/b]" code in the first script before the first scrape, but that seems a little "ungraceful" for such an otherwise elegant mechanism such as SS!!!
If you have thoughts/suggestions, please e-mail or post for my benefit.
TIA.
Dave Nuttall
San Antonio, Texas[b][/b]
Session variables carry-over
That is the current way to do it, or use a dataRecord / dataSet. Or possibly
for (i=1;i<=maxVars;i++) {
session.setVariable("MyVar"+i, null);
}