Hello!

The subject of this post explains it pretty well.

Is there a way to call a FEX and supply it with variable values?
Like so...
EXEC someprocedure.fex (value1, value2)

The IBI docs only show
EXEC someprocedure.fex
and fail to mention anything at all about passing values to a fex.

Thanks!

There are 3 ways (that I know of) to pass variables through to an exec.

EX procName var1=value1,var2=value2
refer to &var1 and &var2 in procName.

EX procName value1,value2
refer to &1 and &2 in procName

-SET &&var1 = 'value1';
-SET &&var2 = 'value2';
EX procName
refer to &&var1 and &&var2 in procName

This is Great!

Thank you for your patience.

Is there any difference between EXEC and -INCLUDE?

I get a FOC not found error when I do
EXEC app/wcqrgj18.fex

but it runs fine when I do a
-INCLUDE app/wcqrgj18.fex

Thanks again!

Jason

There are only a few differences between EXEC and -INCLUDE, really only to do with the &vars. An -INCLUDE is part of the host focexec, the EXEC is a seperate entity, but basic environmental things will be carried through. When you say you get a FOC not found error, that means nothing without further information I'm afraid.

You will have to do some debugging to find out what is missing/different.

Code the fex name as (do not include the "app/"):

-INCLUDE FEXNAME
EXEC FEXNAME
EX FEXNAME

If you want to refer to a focexec in a different application, then the syntax appName/focexecName is valid and is fine.

HUGE differences between EXEC and -INCLUDE
EXEC VAR1=VAL1, VAR2=VAL2, VAR3 = VAL3
is self contained.
it doesn't communicate with the surrounding fex at all. So, that means you can have loops inside that EXEC fex and not worry about having them branch to statement labels inside your surrounding fex, your &vars don't escape your EXEC'd fex.

-INCLUDE does become part of the surrounding fex..so if it were to contain loops and goto labels, they had better be unique.

To repeat an operation inside a surrounding fex, use EXEC
EXEC MYCAR COUNTRY = 'FRANCE'
-RUN
EXEC MYCAR COUNTRY = 'SPAIN'
-RUN
EXEC MYCAR ...you get the idea.
But...
The EXEC command contains an inherent MRNOEDIT
so you canNOT use EXEC in a surrounding fex when that EXEC fex issues a REMOTE call to a REMOTE server. To me, this is a big mess. its a change from 5 to 7, and for me, this killed an entire application in my site...

There's something about the EX command..from 5 to 7, but i can't quite remember. i think its going away. its different from EXEC..

Another way to answer your question is via an http call...

<A HREF="
http://servrname/cgi-bin/ibi_cgi/webapi.dll?IBIF_ex=fex...&VAR2=VAL2&VAR3=VAL3">

This message has been edited. Last edited by: susannah,

I stand corrected.

You can code the EXEC statement in one of several ways (though I couldn't find this in the documentation anywhere). e.g.:

EXEC fexname
EXEC fexname.fex
EXEC appname/fexname
EXEC appname/fexname.fex

-INCLUDE fexname
-INCLUDE fexname.fex
-INCLUDE appname/fexname
-INCLUDE appname/fexname.fex

The folder appname does not have to be in the APPPATH, as long as it's in the IBI Apps folder. You could also run a APP MAP command to enable an application folder that's outside the IBI Apps folder.

This is probably a little different for MRE.

Susannah

Never come across the MRNOEDIT command. Suppose that what comes from only using self-service on one server!

Is there anything I (and others) should know about it?

crossing domains (but that's only if you're using mre)

quote:

Originally posted by susannah:
The EXEC command contains an inherent MRNOEDIT
so you canNOT use EXEC in a surrounding fex when that EXEC fex issues a REMOTE call to a REMOTE server. To me, this is a big mess. its a change from 5 to 7, and for me, this killed an entire application in my site...

There's something about the EX command..from 5 to 7, but i can't quite remember. i think its going away. its different from EXEC..

Another way to answer your question is via an http call...

<A HREF="
http://servrname/cgi-bin/ibi_cgi/webapi.dll?IBIF_ex=fex...&VAR2=VAL2&VAR3=VAL3">

Thank you!

Since this is all within MRE, should I abandon the EXEC command all together? We're on 7.1.3

Thanks again.