Showing posts with label Regulatory Document Management. Show all posts
Showing posts with label Regulatory Document Management. Show all posts

Saturday, March 17, 2007

SPWebEventReceiver - SiteDeleting

I have been searching for examples of SPWeb event handlers that can block the ability to delete a site/web from SharePoint as outlined here. The SPWebEventReceiver class is outlined at msdn - unfortunately without an example.

So far I have not been able to get it working - but hopefully shortly.

Ideas and input very much appreciated.

I found a good example here.

Thursday, March 01, 2007

InformationPolicy - content types - challenges

The excellent information policy example described by Ton Stegeman here is an excellent starting point for learning more about SharePoint 2007 Information Policies. The example given works like a dream.

However - there is a challenge that I have not yet managed to overcome. When associating the informatonpolicy with a content type within a document library it works just fine.

But when I create a site content type and then create a new document library and add the site content type (with the information policy associated) to the document library nothing works :-(

When inspecting the details it turns out that no event receivers are associated with the content type found on the document library.

I was assuming that once an information policy is associated it would be enforced in all locations. This assumption is not correct.

Friday, February 02, 2007

Modifying barcodes in Word - uniqueness

SharePoint 2007 features supporting records management are very promising. Reading various MSFT whitepapers have convinced us that SharePoint can certainly be the core platform for Regulatory Document Management.

My experience with SharePoint has proved this as we have had a solution for regulatory document management based on SharePoint since 2001.

However, in SharePoint 2007 things are not as easy as we expected. As an example SharePoint build in barcodes - which I have assumed to be unique - can easily be modified by the end-user as sketched below.

First - take a look at the SharePoint document library:


Then we open the file in Word, and access the properties. Note that the barcode value has been synchronized with a Word property - which can be edited manually as sketched below:


When I finish editing my Word document and return to SharePoint document library the barcode has been modified:



The result is fairly disappointing as uniqueness of barcodes cannot be guaranteed by SharePoint.

Wednesday, January 03, 2007

MOSS Barcodes not unique


To our disappointment it turns out that SharePoint 2007, MOSS, barcodes are not unique.

SharePoint does not guarantee uniqueness.

Did I miss something?




Check out this blog for information.

Sunday, November 12, 2006

SharePoint 2007 compliance

Microsoft announces that they expect to support more formal compliance requirements such as DoD 5015.2 in May 2007. Hopefully support fo FDA CFR 21 Part 11 will follow shortly.