Job prefix problem

[ArielRauch]

I am working with Smartstream Composer and unfortunately HP has not developed a configurator for it yet.

The Composer works with hot folders and after injecting a job I need to check another folder for the response. When I integrate this other folder as an entry point for a flow every resulting file put in this folder receives the job prefix. This is problematic as Switch is not the only "user" of the Composer.

Any ideas how to avoid the prefix?



Thanks



Ariel

[gabrielp]

If you archive a file, Switch should remove the prefix. But you said an entry point for a flow, so I'm confused. Why would you have another system fighting for files in the same hotfolder that Switch is watching?

[ArielRauch]

that is exactly the point - I am talking about Smartstream Composer - an independent system that outputs its files in a specific folder. I have to watch this folder in Switch in order to take the output and go on with it.

[gabrielp]

Is your problem that Switch is adding the prefix before it goes into Composer or something wrong with Switch picking up the jobs after Composer is done?



Still a little unclear but if you want Switch to remove the prefix just archive it or if the folder you're dropping the files (into Composer) has no outgoing connections, there is a folder property to remove the unique prefix.

[ArielRauch]

I know it is a bit complicated to explain:



Composer outputs file in a folder. I have to take them from there to continue with my flow. In order to do so I have to define the output folder of Composer as an input folder for my flow -> which adds the prefix to every file outputted by Composer.



This I would like to avoid

[gabrielp]

ArielRauch wrote: I have to define the output folder of Composer as an input folder for my flow -> which adds the prefix to every file outputted by Composer.



This I would like to avoid


Why do you want to avoid that? Composer is done with it. Switch needs that to keep track of the job's metadata and move it around.