TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Can anyone venture a guess as to why my employerâa Fortune 500 company
known as a "document company"âwould elect to deploy SharePoint Server 2007
on any large-scale project? That is, are there valid reasons for having
chosen SPS 2010 or 2013? Curious minds would like to know....
For the following, assume we're stuck with SPS 2007:
Any experience with using the built-in workflow system for document
routing? Each doc needs to be passed along a defined path, with several
approvers along the way. Is SharePoint Designer required to do this
effectively (that is, make it actually function as desired)? What's
> Chris (who took Tony's advice for now and is just watching the Kafkaesque
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com