+2
Basically, I have a workbench that produces a CSV that I want to use in other workbenches and get a result. But There doesn't seem to be a trigger that works for me in this idea.
Here is how the automation would look:
How can I trigger an automation from the result of the first workbench?
How can I transfer the resulting dataset into the automation after the trigger?
Thank you,
Kevin
Best answer by chrisatsafe
View original
+2
Hi @kbraun77 ,
How are you intending to run the first job that produces the CSV? Is this going to be a server app, are users running this from the Run Workspace page in FME Server (or even locally on FME Desktop), or do you want this to be part of the automation but be triggered by something else? The reason I ask is because Automations have to start with a trigger like the Directory Watch Trigger you have on the Automation Canvas. In my mind, you have many options but it depends how you intend to run the first job:
Hope that gives you some ideas, if you could clarify on how you want to run the first job we can provide additional suggestions.
+2
Hi @kbraun77 ,
How are you intending to run the first job that produces the CSV? Is this going to be a server app, are users running this from the Run Workspace page in FME Server (or even locally on FME Desktop), or do you want this to be part of the automation but be triggered by something else? The reason I ask is because Automations have to start with a trigger like the Directory Watch Trigger you have on the Automation Canvas. In my mind, you have many options but it depends how you intend to run the first job:
Hope that gives you some ideas, if you could clarify on how you want to run the first job we can provide additional suggestions.
Yes the initial job is a user input server app that produces the csv, that will be outside of and before this automation but I put it in for a visual of the workflow.
+2
Yes the initial job is a user input server app that produces the csv, that will be outside of and before this automation but I put it in for a visual of the workflow.
Hi @kbraun77 ,
Got it, okay so the second bullet point should work in your case. Simply setting the destination folder for the CSV in the server app workspace to the same directory that you are watching should do the trick - this is the simplest approach.
+2
Yes the initial job is a user input server app that produces the csv, that will be outside of and before this automation but I put it in for a visual of the workflow.
Hey, thanks again for the response.
This was a working solution, however when the tool is used by multiple users the file being overwritten causes an issue with the end results. I've tried experimenting with having the CSV exported with unique file names and then the automation reads in the newest files.
Is there an easier approach?
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
