I wonder if anyone else has noticed this anomaly in WebDirect:
The Export field contents scriptstep is allegedly compatible with WebDirect, but if you're using a variable to store an exported image's filepath, then the scriptstep ignores the export path and dumps the file in your downloads folder instead.
If that wasn't bad enough, it also drops the file extension, so the file can't be opened correctly until (for example) ".jpg" is appended to the downloaded file.
Curiously, right-clicking on an image in a WebDirect browser and choosing Export Field Contents, shows the correct filename by default. The file is, as expected, downloaded to your Downloads folder.
Surely, the scriptstep should work in WebDirect as it does on an FM client. If it doesn't, then it's not compatible ...