Add scope="session" to <set>; replace setenv with it
<set name="x" value="..." scope="session"> now writes x to the session file (any name, no @ prefix); values are still read with $[@x]. storeVariable passes the scope through instead of repeating the global/local/parent checks for each value source. Convert every <setenv> use on barant-site and qualityiron-site to a plain <set> plus a scope="session" <set>, which keeps same-request $[name] reads working, and remove setenv from both SESSIONCTL.tag copies (sessionctl is deprecated for session management). Document session variables and the set tag scopes in the Jet manual. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
867ace3cb3
commit
08462ca996
26 files changed
+108
-82
No files matched your search
@@ -1,6 +1,6 @@
|
||||
<process>
|
||||
<setenv name="_login_id"></setenv>
|
||||
<setenv name="_login_email"></setenv>
|
||||
<setenv name="_login_name"></setenv>
|
||||
<set name="_login_id" value=""><set name="_login_id" value="" scope="session">
|
||||
<set name="_login_email" value=""><set name="_login_email" value="" scope="session">
|
||||
<set name="_login_name" value=""><set name="_login_name" value="" scope="session">
|
||||
<setpage name="login">
|
||||
</process>
|
||||
Reference in new issue
Block a user