hyper/logos

For this post, I might even go with, “Just because you can doesn’t mean you should.”

Task: The Helpdesk needed a series of forms created that would allow managers and employees to make requests for things like new employee accounts, employee moves, teeminations, etc.

The approach: Since the New Employee Request incorporates most of the other requests, I decided that I would create a single form. You would select the request type from a drop-down control and the appropriate sections would appear. So, I got to work. Now, it’s done - except for one minor detail: workflows.

Each content type in a library can only have one workflow, it seems, so I will have to code workflows for the various forms. Rather a pain, one would think. And one would be correct, both in regards to coding and maintaining the coded workflows.

Reality rears its ugly head: in retrospect, not the best way to go. After some discussion with my coworker and a weekend of thinking about it, here’s what I’m going to do: finish the existing form so that /something/ is available. Then, I’m going to recreate the forms individually and assign them all to a library as different content types. This will allow me several things: 1. Centralized storage 2. Multiple content types means multiple workflows 3. Only one document library to maintain

Yeah, that sounds much better. I’ll follow up with what I do. Stay tuned!