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.
This includes information about the Knowledge Document plugin, which
permits publishing managed docs to the Knowledge Base (convenient).
On Wed, Aug 29, 2018 at 4:45 PM John G <john -at- garisons -dot- com> wrote:
> My wife has extensive ServiceNow design experience and says:
> Yes, we put runbooks in ServiceNow.
> We put them in the Knowledge Base, but you can also use the Managed
> Documents module and its functionality.
> With Managed Documents, runbooks and other critical documents can be
> created, requested, checked out, edited, checked in, copied, and, if
> necessary, rolled back to an earlier version. Documents can follow a
> customized approval workflow.
> Another important aspect is that when documentation is stored in
> ServiceNow, it can be incorporated into the workflow for Change Management.
> So, when a particular technology (represented by a configuration item in
> the CMDB) has a Change, it can follow a customized workflow which includes
> appropriate modifications to the Runbook.
> Hope this helps!!
> On Wed, Aug 29, 2018 at 3:36 PM Shari Punyon <sharipunyon -at- gmail -dot- com>
>> Hi All,
>> Thanks in advance for any replies. I searched back emails, and didn't find
>> anything on this topic.
>> I'm currently working for a "knowledge management" organization in the IT
>> area. We currently keep the bulk of our "runbooks" and other tecnhical
>> documentation in a Confluence Wiki. However, a new management edict means
>> that we will be moving much of our technical documentation to a ServiceNow
>> (Fusion?) portal. This will have the benefit of better integrating with
>> Configuration management database (CMDB), which holds application and
>> infrastructure information, such as all the server details.
>> It has the negative that it is a far less easy to use system, although
>> we've discovered that if we turn on certain add-ons it will do most of
>> we do using Confluence and it's plug-ins.
>> My questions are -
>> - Has anyone used ServiceNow to hold documentation, other than a few
>> help articles?
>> - Can anyone point me to good training or documentation?
>> Our bonus difficulty round is that we want to have our SMEs complete the
>> information, and we need an approval workflow.
>> Thanks in Advance,
>> Visit TechWhirl for the latest on content technology, content strategy
>> and content development | http://techwhirl.com
>> You are currently subscribed to TECHWR-L as vwritert -at- gmail -dot- com -dot-
>> To unsubscribe send a blank email to
>> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>> http://www.techwhirl.com/email-discussion-groups/ for more resources and
>> Looking for articles on Technical Communications? Head over to our
>> online magazine at http://techwhirl.com
>> Looking for the archived Techwr-l email discussions? Search our public
>> email archives @ http://techwr-l.com/archives
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com