Aha. Since I wrote my original response I have become aware of a potentially better way to do it. The Requester element. Info in online help with heading "Configuring Request/Response Communication".
It works like a message placed into an output channel, except it waits for the response. It gives your workflow the chance to do error detection. Everything else is as described below.
It works like a message placed into an output channel, except it waits for the response. It gives your workflow the chance to do error detection. Everything else is as described below.
--- In vantage@yahoogroups.com, "thedemondamian" <sheath@...> wrote:
>
> Alex,
>
> Would either of these methods work if the file already exists. The file is being placed by a Poster method from another workflow. It could be a few days before the scheduled workflow has to pick it up.
>
> The file location will never change so putting that in the channel setup is no problem. The file name will be determined by the PO Number of a Sales Order so I wont know which file I need until I am ready to grab the file.
>
> - Scott
>
> --- In vantage@yahoogroups.com, "Alex Fiedler" <alex.fiedler@> wrote:
> >
> > Ok there are two ways to achieve what you want to do:
> >
> > Both require you to write the required information (e.g. the file path etc) to an output channel.
> >
> > In the first case the output channel is a FILE output channel. Have a vbs script scheduled to poll for the appearance of this XML file, parse the XML for the path and then copy the specified file into an input channel.
> >
> >
> > In the second case your output channel is a COM output channel and your COM object does the file copy directly. I have not done any output channels which are COM objects, presumably having been written with Visual Studio.
> >
>