A really powerful new feature in SharePoint 2010 is the content organiser, a suped-up version of the routing engine found in the SharePoint 2007 records centre.
There are a good many articles out there extolling the virtues of this flexible new feature which is great. In this post however, I want to concentrate on one very specific area: -
http://YourSiteName/_vti_bin/OfficialFile.asmx
I know, I know, not catchy (or fun) and I know it’s not gonna get you out of bed on a wet London morning.
What it is going to do though, is be the url for the content organiser web service for that particular site collection.
Big wow!?
Whilst this might not seem like a massive deal, I’m sure you’re not lining it up to fill that elusive after dinner speaking slot, it does open up a few interesting possibilities – namely easy document routing workflow.
Now I know what you’re thinking, “hang on a minute…isn’t that what content organiser already does?”
Well yes, it handles document routing based on rules in a really slick way. It even has other elegancies such as evoking the routing engine when you update a document to a library that has rules pointing to it (see fig. 1 below)
This is really nice and very fast to configure. But what if you wanted to build in more complexity to how the documents are routed? Not so easy.
Back to that url and how it can help? Anyone who has looked at SharePoint Designer 2010 will know that things have moved on in leaps and bounds since the 2007 version and certainly where creating workflows is concerned.
The beauty of that url is that it can be referenced in workflows, meaning document routing can be achieved without having to worry about complex rule creation in SharePoint Designer.
So why would this be useful?
Take the example where you have an image library storing corporate images, but you need to be able to move items based on their status to a different location – where an image is marked archive or inactive for example.
Simply create a basic workflow in SharePoint designer and let the content organiser handle the complicated rule based and alerting functionality.
The advantage of this approach? Should it be decided at a later date to change where archived images are to be stored this can be easily handled by simply changing the ‘Target location’ in the organiser rules.
No need to worry about setting up complex alerting rules in designer either, as this can be addressed in the content organiser settings, along with other useful functionality such as saving original audit logs and properties with the content wherever it lands.
Great! Of course if your organisation doesn’t have particularly strict audit requirements but it would be really useful to know where the image has moved to and from (and who changed its status from archive to inactive for example), you could always look to expand on the variable outputs in the SharePoint Designer workflow…
…and write these outputs to a ‘Multiple lines of text’ field that appends (version control required here of course).
Voila – a rudimentary audit trail of what your image has been up to while you’ve been away! If only it was that simple with cats…and children! (and stocks, and socks, and so on, and so on).
Have a play. Get creative. Enjoy.





























































