We have a Cascading Data Set with two levels that is configured on multiple doc types. For purposes of illustration we'll use State and County.
State - County
OH - Cuyahoga
OH - Erie
OH - Lake
Most of the doc types contain documents that are specific to the State and County, but some of them apply to all Counties within a State. We may terminate a relationship with one of the Counties (and start retention clock / Cutoff RM folders for "Cuyahoga") while leaving other RM folders (Erie, Lake) in an Open status.
We've handled this situation up until now by having two RM folder types - one configured with only State as the required Keyword and a second with both State and County required. The doc types that apply to all Counties were configured to use the former RM folder, and doc types that were unique to Counties configured to use the latter RM folder. This required additional logic be setup to ensure that when the relationship with a State was terminated - all State/County folders were also Cutoff.
This has complicated re-indexing of documents necessary because they were stored incorrectly, and it has also limited our ability to group all documents within intefaces (such as Custom Queries) as not all of the doc types have County as a keyword. We're looking to simplify this design by moving to one RM folder with State/County but in order to do this we need to make copies (both existing and going forward) of the documents that apply to all Counties. We need to avoid asking associates to store the same document multiple times because it is inefficient but more importantly because it will be forgotten and once a folder is destroyed - necessary docs could be lost.
We use Unity scripting and Workflow to make copies of documents using standalone keyword types but the Cascading Data Set introduces a new variable. Is anyone doing something similar (even if not using CDS but similar RM setup) that has a suggestion?
