I selected Sandboxed because I want the feature to be limited to the site collection where I am publishing only.Step 3: As seen below we’ve selected our “Type of event receiver” to be “List Item Events” and “Event Source” to be the “Pages Library” because that’s the library use has the pages that have our custom content type.
Eventhandler itemupdating updating fmla policy
You can also change the deployment scope here from Web to farm etc. I’ll cover xsl transforms and more customizations in a future article. This class will save our transformed html as a file into a given sharepoint library.
For now we’ll use the quick-and-dirty ‘code transformation’. This class also has a single method Save File To Library that takes the site url, library name, html content and file name as parameters.
Step 6: Next if you expand the Feature node you’ll see an element called Feature1.
I have renamed it to Custom Content Publish Feature.
Policy documents, Functional Specs, Technical Specs, Time Sheets, Work-Orders etc.
Custom Content types help us with defining the data-structure while layouts help us define the presentation.
Instead of using the out of box revision history, if we built a capability where after every “Publish” the content is converted into a read-only format (like HTML/doc/pdf) and kept in a different location, it would solve our problem.
If that location is a version controlled document library, then each version of the complete document would be available for anytime reference! Share Point has this infrastructure built in where certain SP objects raise events that can be handled by custom code.
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.Tags: Adult Dating, affair dating, sex dating