Shouldn't it? The file was written successfully. I think I had asked something similar a while back but could not find it...
No, it will not continue after the write operation. This is the same for an SFTP, FTP operation as well. If you are performing a send operation via web service, for example, you might have a response message returned, or a status code, etc. But that isn't the case with an operation that writes a file to disk, FTP, etc.
Another scenario that I implement often is adding a branch before a single write operation. On the second branch, I set a property saying that the write operation was successful, or just return documents on the second branch. It just depends on what logic you need or want to implement.
Are you trying to write the same file to the second connector? Simply adding a branch before the first outbound operation should work well.
Does this mean that there is no outbound path from the disk connector? It is the same file but a different filename. I have it working on a branch but though I should be able to continue on the same path.
John is correct: no document is returned from the Disk Send connector so no subsequent steps will execute down that path. Admittedly it's a big misnomer and in my opinion there shouldn't even be an "output line" from the Disk Send if it doesn't return documents (similar to a Stop or Exception shape). That OR actually return a document, maybe a metadata file or something with the results of the write: Return actual filename for Send Connectors.
Bottom line: use a branch shape as suggested above.
Adam Arrowsmith, will using a branch ensure that the Disk write was successful? I need to move a file to another directory after the successful write to disk. I wish the Disk operation would include a 'move file to directory' option.
Hi Yechiel Kaplan,
Yes, the second branch would only execute if the disk shape was successful.
Retrieving data ...