Tag Info

Hot answers tagged

2

Yep you can. You need to make sure that you have the Document Set feature enabled on the Site Collection and then from the Content Organizer Rules you can specify the Group as 'Document Set Content Types' and the type as 'Document Set'. One thing people frequently forget is that you also need to have the content type available within the destination ...


2

You can create a content organizer rule that will route the document to a directory with a folder name corresponding to one of your fields, creating the folder if necessary. So potentially you could solve your requirement with a single content organizer rule. I'm guessing your file plan is more complicated, but I am sure you can work out a fairly manageable ...


2

Apparently I just needed to go one more page on the Bing search results :) The answer is here: http://www.scottjamison.com/blog/2010/11/the-sharepoint-2010-content-organizer/ Two of the questions I get regularly on the content organizer: Does a user need write permissions on the destination location? Answer: Actually, no! The content ...


2

Marco, this is unfortunately functionality you need to "live" with. We created our own unique document ID service application that ensures document ID's are maintained through the lifecycle even when moved to the records centre. We also created a configuraiton page to allow unique numbering to be set at a content type level therefore you are not restricted ...


2

You can enable the management of content types in the document library. Add the Link to Document content type to the library. Then in the folder of your choosing, select the Link to Document from the New menu and point it to the file you'd like. Rinse/repeat as nessary. (Steps above taken from memory of SP 2007, exact process for 2010 may be different).


1

I'm going to go ahead and say "no". Here's an interesting article that agrees. In certain scenarios you would like to be able to re-submit documents when certain metadata of that document is changed. Out of the box this isn’t possible this means you will have to create a custom solution. ...


1

The only thing I could think of is to add an item event receiver to your document library. When a new document gets added, start the Content Organizer Processing timer job manually. public class EventReceiver1 : SPItemEventReceiver { public override void ItemAdded(SPItemEventProperties properties) { using(SPSite site = new ...


1

OK, since the user doesn't need to have rights, I would look into implementing an approval process. Items can be forced through a content approval process prior to it being routed. I believe you would add the content approval to the drop off library. Check out the diagram from Microsoft


1

One of the functionalities, when using the Content Organizer, is whenever the “Content Organizer Processing” timer job runs and finds documents in the drop off library, it will fire off that reminder email EVERY TIME it runs. So You can't disable sending email to the content owners. Keep this in mind when you are configuring the Content Organizer ...


1

If your concern is that the # of pages is going to continue to grow on these sites, then using the Content Organizer and routing rules is the best approach for physically organizing pages into a folder hierarchy. You will need to figure out a file plan in which to organize pages (can be based on date) or it can be based on some sort of metadata fields, or by ...


1

QuickLaunch items could be linked only to separate lists and pages, not to their groups. Heading items, which reference your Discussions "groups", are not more than simple links with some custom anchor text. So don't expect any intelligent behavour from them. OOTB viewlsts.aspx page presents some functionality for filtering by type of list and by list ...


1

Serge Luca has already found a workaround for that: schedule the Content Organizer Processing timer job or launch it manually.


1

As @David says above, you can create a rule for one contenttype, then add other contenttypes as aliases to this rule. This way you end up with much fewer than 200x500 rules. Each rule has a ContentTypeString, which is the main content type and a property Aliases (or RoutingAliases) in the format of "ContentType1/ContenType2/ContentType3". The string for ...


1

Well, not exactly. But you can indicate the parent content type as the rule (like you did) and then specify all of the other content types as an alias. Priority then works and recognizes your "alias types" and applies the rules as you have previously defined. The downside is your rule would not automatically recognize additional content type "children" ...


1

Not so fast :P You need to have also enabled "Content Organizer" feature in site scoped features to do rule sets. SAV


1

The way to deal with this is to create a Content Organizer rule which has the destination set to 'Another Content Organizer in a different site' - this allows you to move content between webs in a site collection (from memory the dropdown is only populated with other webs in the current site collection which have the Content Organizer feature activated). In ...



Only top voted, non community-wiki answers of a minimum length are eligible