Combining Documents and No Delete Rights-1518736819

Good Afternoon, Everyone:

We have a need to combine documents that are in a File Cabinet into a single document, hopefully without the need to then go back and delete the original documents being combined.

Main issue being that the users do not have Delete privileges.

My default angle for this is to copy them to a Document Tray and Staple or Clip them before shooting them back into the File Cabinet.

Aside from being more steps than I'd ideally have to have them use, we're left with the originals in there if we go this route.

What do you think?

Thanks!

Chris,
You've answered your own question. Without delete rights you will have the duplicate documents in the cabinet. However, once clipped to another document you will have no reference to find duplicates. But you know this. There is no magic here. You either give the users delete rights so they can delete after copy to the tray, or you need to develop another strategy.

It always helps to know what the use case is. That is - Why? Then it may be possible to help you.

Footnote: Stapleware Stapler is designed to do what you want.

Phil Robson
Senior Director Support Americas

Chris,

We had a similar need - to clip (or staple) multiple documents based on certain index criteria, such as Order#s being the same, as an example.

The StpleWare Stapler is certainly a great 3rd party add-on that would do this, but we developed our own REST API based program that serves our needs better. It is not that difficult, especially if you have a developer on staff who could write C# code.

Thanks for taking a look, guys.   

Use Case:  We are capturing Picking Lists for Orders, and we're capturing them via DW Printer resulting in some orders having a number of these Picking List doc types for that order.

The users would like to combine all of these into a single Picking List doc once they're all in there.

I've heard of StapleWare Stapler over the years, and actually thought about it here, but nice to solve some other way.

Not necessarily opposed to going the API/SDK route, either.   Only very little C# experience, but familiar with general off the GUI, script based operations (mostly SQL, but some other stuff, too...) and I might be able to pull it off.

I'll need to mull it over a bit...