Recycle bin v3

[JimmyHartington]

Hi

I would like some input from other users about the change to Recycle bin in v3.

Now the Recycle bin is not a managed folder in which the files resides.
The are instead "held" in the last folder before the Recycle bin element.
See screenshot at bottom.

In my case I will have to add new folder before many Recycle bin elements in my many flows for this to make sense, since otherwise I would be confused about files in the folder.

If this is a default change Enfocus would like to have that is OK. But I would like an option to still have the old behavior.

[jan_suhr]

Aha, that explains why my files don't move to the bin

Not so logical, they should end up in the bin and stay there IMHO

[freddyp]

There is a very technical explanation why keeping the old behavior was not possible and keeping the files in the folder in front of the "Recycle bin" was the next best thing.

You can of course keep working with the previous version of the default app.

[Shawn_Anderson]

I absolutely hate the new behavior. It makes it unclear about the status of the files in the flow and it goes against common UI conventions where the trash/recycle bin is a container for files. We've had issues in the past with jobs getting stuck mid-flow so when I see files sitting in the middle of a flow it makes me think something has gone wrong.

I figured there were reasons for the change but I'll probably revert back rather than add extra folders to every single flow...

[JimmyHartington]

I agree with you, Shawn.

This is an app I will update as the absolute latest if the old behavior can not be added to the new version.

A yellow folder with lots of files is normally an error in my flows.

[freddyp]

Point taken, gentlemen! I cannot promise a better approach any time soon, but I will certainly report it.

[JimmyHartington]

Point taken, gentlemen! I cannot promise a better approach any time soon, but I will certainly report it.

Thanks

[tdeschamps]

In addition, it's not so much the fact that the job waits in front of the element that bothers me the most, but rather the change in behavior.

Here is an example:



In this case, the job is held with a constraint folder, and the Hot Folder Monitor will no longer behave as it did before the update.

We've already encountered a few customer cases like this.

It's something we'll have to live with and explain to our customers, but the behavioral change was unexpected from their perspective. After all, who reads the patch notes anyway?