Hi,
We have been moving documents to filesystem using the 'move to filesystem' smart service. But now we have to move files to a particular network folder from where Seeburger picks the file up and moves it to another location. The issue is when we are trying to move a larger file (over 5mb), the move to filesystem node is breaking with an error "The process cannot access the file because another process has locked a portion of the file".
We have identified that seeburger scans the folder for new documents every 20seconds, and for larger files, it is picking up and locking the file before the transfer has completed.
Is there anyway to make appian lock the file until transfer is completed so as to prevent seeburger from locking it before appian is done moving the file ?
note: Ideally we do not want to increase the poll time of the folder above 30seconds.
Discussion posts and replies are publicly visible
Hi srijans
Please explore the SFTP Smart Services Plugin as your alternative.This can be found in the AppMarket.
The Filesystem Utilities plug-in (which enables the move to filesystem smart service) is no longer recommended for use, and was removed from the AppMarket quite some time ago.
Does Seeburger have a configuration to ignore files having a certain extension (i.e. file extension whitelist/blacklist)?With the SFTP Smart Services plug-in, you can rename a file AFTER the transfer is complete.So, if you generate/transfer the file using an extension that Seeburger ignores, you can be assured the Seeburger won't lock the file while the SFTP transfer is in progress.Then, after the file transfer completes, use the Rename File Over SFTP smart service to rename the file with an extension that Seburger is looking for.
This should allow you to keep your polling frequency low.