copy folders strategy

Users can be so creative.

Here's another user idea. They want to use the copy feature of Webtop to copy doclist folder and subfolder structures from one project to another. They want to set up a standard folder security set on the source project ("template") and when any folders are copied from the source project, have the source's security migrated to the target project when the folders are "copy here" from the clipboard.

OOTB, the folders copied to the target project will inherit the security set of the target parent folder, and that doesn't work for this idea, we have a mix of security settings on the indented folders depending on which external group (customer, partner, supplier) uses a particular folder.

The goal of all of this is to create a configurator, that can build the necessary doclist folder structure per order. This way, the target project will only have the minimum # of folders and these folders would be configured specifically for that customer order.

Currently, we just establish a template with the max case of folders and create the new orders from that. So on every project there are some folders that are never used. Makes the folder structures larger than they have to be in most cases.

Summary: what they're looking for is functionality that behaves like add to clipboard--copy here, except that they want the source project's folder security to be dragged along to the target project.

Ever encountered a request of this nature before? Any suggestions?

Many thanks,

Bill

Find more posts tagged with

Comments

lastnitescurry

first thoughts would be to call a server method at the end of the Webtop copy. Run as super user to avoid permission problems

2nd thoughts would be to create an Aspect or TBO (only if you have custom folders) and add logic into doSaveAsNew (I presume this is what is called for copy).

server method way avoids any security issues but maybe more difficult to deploy or move customisations later

TBO would be easy to deploy (as part of Composer project) but coding it would be an intersting excercise. NO WDK customisation required

Aspect would have same coding difficulty as TBO, and would required WDK customisation but would work for dm_folder objects

rohit.khattar

I would agree with Brian , there are mutiple solutions to achieve this however depends on few criterias,

If there is a only single client Application like Webtop , then triggering a server method after Webtop copy can be considered.
If there are mutiple client Applications or the functionality needs to be implemented at server level rather than client level then TBO will be a good option(only if you have custom folders) again just check it is not impacting the performance. The above solution is still at server level but triggered from Webtop.

The coding in TBO should not be too complex , you can make it configurable by creating the XML configuration file that will contains the necessary permissions to be applied. The TBO will read the XML configuration file while applying the necessary permissions on the copied folder structure.

DCTM_Guru

"The goal of all of this is to create a configurator, that can build the necessary doclist folder structure per order. This way, the target project will only have the minimum # of folders and these folders would be configured specifically for that customer order."

Do you have Process Builder? There is a workflow activity that will copy/create case folder template. This includes subfolders and all documents located in the subfolder. You can also configure which acl to assign them.