Hi to you,
nice to read, that my example helped to find out:
division of script's primary name and all following values as parameter(s) (bracked by ") into parameter field.
Bye Robert from Germany
Woa, that worked!
This should work. However, you have to point to cscript.exe in the Script field.
The vbs file and other information should be in the parameters field.
FFCore will concatenate both fields. The result of that concatenation should look like this: cscript [script name] [host options] [script arguments]
Nope. No workie!
Still need help :-)
Thanks rm59 - i'll try batch-files again :-)
Yours doesnt call a script, it seems, but maybe if i fiddle some more, i can get it to work.
If i check the MantisDebug.log, i see this " The specified executable is not a valid application for this OS platform. "
No support for vbscript?
You should start with a simple *.bat script like this (it works here):
REM logging.bat RM mit P1=Step-Bezeichnung P2=Auftragsnummer P3=FFC-Zeit P4=FFC-FFin
REM Zeitstempel in Log schreiben
echo Auftrag %2 Stufe %1 fertig >>%2.log
time <enter.txt >>%2.log
REM echo FFC-Zeit %3 >>%2.log
echo FFC-FFin %4 >>%2.log
From the view of FFC (Workfloweinrichtung):
Art = Script
Script = D:\Hotfolders_Test\dz_opti_steps\bat\logging.bat
Parameter = "Schritt" "$FFwfJob.Id$" "$FFtimeStamp$" "$FFin$" "$FFout$"
Result: D:\Hotfolders_Test\dz_opti_steps\bat\FFCnumber.log - files were written
Good luck Robert M. from Germany
I have a vbs-script i'd like to call with the external node. This script connects to a mysql database + writes to a csv (max-file), but when using it thorugh FreeFlow Core, it errors. It doesn't in a cmd-window.
I'm guessing it's due to permissions, though FreeFlow core doenst really tell me what errored. How are the scipts called from FreeFlow Core? Do i need to adjust something? Change "log on as" on the services? folder permissions? something? :-)
In scheduled tasks, i know that some people launch scripts through a .bat containing "cscript.exe somescript.vbs", to overcome issues, but i havn't managed to get this fix to work either.
Solved! Go to Solution.