So I was reading this thread: Text over image in a basic report and thought it would be great if I could make functions like that available for my business users who work with InfoAssist. I've never worked with user defined functions in WF before so I'm not sure what I need to do so that this function is available for use in IA. I appreciate the assistance.

Thanks,
Deb

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

Deb

There is a manual called Using Functions that describes how to create your own and publish them for others to use. You can find it on the techsupport site under technical content under the Reporting Languages section

Chuck,
it isn't really clear, all it says for running on Windows, "No extra work is required." But I don't understand where to save a function I've written in WebFOCUS so I can use it in a DEFINE field in InfoAssist. Will it really use it if I just save it anywhere?

Thanks,
Deb

I have 20+ DEFINE FUNCTION routines. All of mine are in baseapp on the reporting server. A good number of them are loaded with a -INCLUDE in edasprof, making them always available. For example, I have versions of DATEDIF, DATEMOV and DATEADD that I use in Dialogue Manager. We have to report on Federal and State Fiscal Years so I have a function that will compute the Fiscal Year when supplied a date and year type.

DEFINE FUNCTIONs and User Written subroutines are not the same. DEFINE FUNCTIONs reside in an app folder (like I said all of mine are in baseapp). They are .fex files. User Written subroutines are written in a compilable language like C. For example, RSTAT generates C code that is compiled. Those executables are stored in /opt/ibi/srvxx/wfs/user (where xx is your WebFOCUS release, in our environment it is 80).

@Jgelona
You don't have to do anything special in the fex file, just make sure to add a -INCLUDE functionname.fex in the edasprof?

Thanks,
Deb

Nope, nothing special. The -INCLUDE for the DEFINE FUNCTION can be in your fex if it is rarely used or in edasprof if used a lot.