It's exactly that !
Now the job ends without error.
Thank you so much.
Try removing the pause.
Yes, I send it below.
The script is a .bat file that gets the arguments from FreeFlow Core.
It calls a PHP script for sending e-mails by passing FreeFlow Core arguments.
And I added the line to copy the PDF file following your advice.
Thank you
@echo off copy %3 %4 "C:\php\php.exe" -f "C:\FFCEmails\TestEmail.php" %1 %2 %3 %4 pause @echo on
Can you send the script.
I did the test but it didn't change anything.
The $FFin$ file is copied to the $FFout$ directory and then it disappears.
And the flow is in error.
Try using:
%1 %2 %3 %4 in the batch file
with the parameters
$FF<max variable 1>$ $FF<max variable 2>$ $FFin$ $FFout$
My parameters used for the external process:
"$FFin$" "$FFout$" "$FFNomSociete$" "$FFNomClient$"
The last 2 parameters are variables of MAX.
Thank you
Can you supply the content that you are specifying in the Parameters field of the External node?
Note: FFCore variables cannot be edited/updated via an External node script.
Hello Stephan,
Thank you for your reply.
I was not very clear in my explanation.
I am actually using a hotfolder with MAX, but I am not using a script with the hotfolder.
The script is called in the workflow, along with an external process.
I tried your method.
I added the $FFin$ and $FFout$ variables in the parameters.
And I got them from the .bat file to make the copy.
The copy seems to work. A temp.pdf file would appear in the script folder and then disappear 30 seconds later.
However, I still have the same error.
FreeFlow Core job 890124 failed with the following error: External process: script timeout C:\FFCEmails\ScriptEmail.bat "C:\Xerox\FreeFlow\Core\00000000-0000-0000-0000-000000000000\Platform\Spool\f6bc347b-cce0-427a-8a7e-0110126af151\temp.pdf" "C:\FFCEmails" "Variable3" "Variable4" after 30 seconds.
When you use a script on the hotfolder then only $FFin$ and $FFout$ are supported. This is from the Help guide:
--------------------------------------------------------------------
Scripting
When the Hot Folder option to Execute Script Prior to Workflow is enabled, the system issues a CLI call in response to retrieving a file in the Hot Folder. The CLI call concatenates the following attributes:
• The URI defined in the Script. The following URI formats are supported:
• script.xxx (Sandbox Location)
• <drive letter>:\folder\script.xxx
• The text string defined in the Parameters. This field has two predefined variables:
• $FFin$ the URI of the file that was put into the Hot Folder
• $FFout$ the URI of the folder where the script is to output a valid job file
* Note: Other variables are not supported in the Hot Folder Scripting tab.
Each time a script executes, Xerox® FreeFlow® Core archives the contents of stdout and stderr to XML files in the Manifest Status subfolder of the Hot Folder. This subfolder is accessible using the filesystem of the host.
* Note: When scripting is enabled the Hot Folder will accept files of any type. However, the output file from the script must be a file type supported by Xerox® FreeFlow® Core. The file must be placed in the location defined by the $FFout$ variable.
--------------------------------------------------------------------
I would run the script on the hotfolder like you do but add something like
copy %1 %2
where %1 is $FFin$ and %2 is $FFout$