Okay fine, workflows are still out of box, what are we doing new in that? Imagine what would happen after a document (like our Functional Spec) is approved? Until the document is approved again it would no longer be in ‘Published’ state.To view the previous state would be slightly messy.What if these documents were to require review and approval?Share Point as most us know, has built in workflow capabilities.This whole architecture of hashtables of properties and trying to match up values seems to me to be pretty fragile, and I’m not sure why Microsoft went this way.It also seemed to create my second problem, where data I did set disappeared.It was only by using the Display Name of the field that I could actually get any of the data to stick.
Now you have the ability to catch events on practically every list type that Share Point offers, as well as at the site level, list or library level, and at the individual file level.
Unfortunately I was not able to find any online documentation about how to do this with code. Net reflector turned out to be the right way to go.
Microsoft made a lot of the required functions internal, which means that we cannot access the functions from our own code.
If we look at our example of creating a custom Content Type for “Functional Specifications”, we could extrapolate it to many different types of documents typically used in an enterprise, e.g.
In this article we’ll continue where we left off and see how we can add a hook in Share Point and enhance the content creation and approval process to make it more valuable to end users.