Self-service and directory structure

stevekrys

Greetings,

We are trying very hard to establish a self-service model for a small sub-section of our business users. To date we have implemented a fairly intelligent templating system that makes a lot of redundant tasks invisible to the users. We have NOT implemented any workflows as of yet. That said, I know workflow should be a critical part of any content self-service system. I'm curious to hear how others are using workflow within their orgs to support non-technical (business users). At the end of the day someone with some technical knowledge needs to understand the directory structure enough to add files to a workflow to get it started and sent off to a business (non-technical) user. The staff in our group who assign work to other resources are not technically oriented so they are not capable of attaching the right files in TeamSite to a workflow. How are others doing this from a roles/responsibilities perspective? Thanks in advance!

Migrateduser

You could have them use CCStd and even customize that or (in my opinion) even better, you could have them start the workflow via a custom menu item. This menu item could invoke a home grown file browser that, let's say, starts in a certain directory, depending on the identity and possibly the role of the user logged in to the system. As I understand your requirement, browsing for the file is perhaps the ugliest aspect of workflow that these people will have to deal with, so this might alleviate some of that. Otherwise, a little creativity will point you in the right direction. I'd recommend you allow them to start the workflow via a custom menu item and perhaps a series of screens as part of that menu item.

Dave

Current Environment(s):
(1) TS 6.5 on W2K3
(2) TS 6.1 SP1 on W2K3
(3) TS 6.1 on W2K