nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

IW_USER variable works in one environment but not the other?

System

I have a simple IPL (attached) calling the below variable from a WFM custom_Instantiation.cfg

my $user = $ENV{"IW_USER"};

...it works fine on our beta environment, and returns the proper Domain\User. when i moved the exact same code to our production environment, it doesnt return anything! im totally stumped...

[HTML]
Issue Tracker ID
Select the Issue Tracker ID from issues you are assigned

[/HTML]

i thought maybe it had something to do with environment variables, but when i move the code to a standard DCT (not a custom_instantiation.cfg) on our production environment, it works ok!

any thoughts would be greatly appreciated, thanks

Find more posts tagged with

Comments

Adam Stoller

I'm not sure about answers, but ...

You said the script was attached, it wasn't (perhaps it was on the first attempt at creating the thread, I didn't bother to look).

You're using an inline directive - which implies a command-line oriented script, but your running a script from httpd/iw-bin/ - which implies a CGI-oriented script. It doesn't have to be, but that's the implication.

If that's true, perhaps it has something more to do with the context in which the script is being called than the script itself? I realize that's a bit of a leap, given all the other things you said, but I figured I'd throw it in just in case.

Perhaps seeing the code might help...

BIRT2.jpg

BIRT1.jpg

Migrateduser

ahh sorry, devnet was killing me yesterday. IPL attached (renamed to .txt). let me try moving the ipl out of the iw-bin...

my main kicker is that the IPL works fine referenced in a standard DCT and gets the global variable fine, but returns nothing when the exact same code is moved to the custom_instantiation. I can use

my $user = getlogin();

in the ipl, but that only returns SYSTEM as the user...would another option be to

1) use formapi in the custom_Instantiation to get the userid, then pass that into a callserver that builds the multiselect? that just seems like overkills since the simple env variable worked fine on our beta environment Smiley Sad

Adam Stoller

...
1) use formapi in the custom_Instantiation to get the userid, then pass that into a callserver that builds the multiselect? that just seems like overkills since the simple env variable worked fine on our beta environment

It may seem like overkill, but if this script is being used for callserver purposes (in which case, leaving it in httpd/iw-bin/ makes sense) - then I'd say setting the param from within the primary FormAPI code makes sense and will ultimately be more reliable.