Body
Overview
This article is for Purdue IT technicians who have access to create articles in the Knowledge Base. For technicians who do not have KB access, see “How do I submit knowledge base articles in TDX?”
Team lead technicians should also see, “Roles and responsibilities of Knowledge Base Team Leads”
Instructions
-
Sign into service.purdue.edu and select the “Knowledge Base” tab.
-
Click on the ‘+New Article’ button.
-
Complete the fields:
-
Category = Choose from the available category structure; do not create a new category. If you believe a new category is warranted, email itservicemanagement@purdue.edu and make a request.
-
Leave the ‘Order’ as 1.0; do not click the "Pin Article" check box.
-
Subject = Article Title. Articles intended to be a team-specific internal article should start with “Internal “Team Name” Article:”; articles intended to be internal to all Purdue IT should start with “Internal Purdue IT Article:”
-
In the “Body” field, add your article content. Use available templates for formatting or to insert text options.
Note about adding images: Before adding images to an article, consider if they are truly necessary. Screen shot images can change frequently as services/devices are updated and may not reflect the user’s experience. If you believe the images are necessary, be sure to include alternative text to make the images accessible (See, “Internal Purdue IT Article: Web Accessibility best practices for images on websites).
To add images, see Internal Purdue IT article: How to add image to TDX Knowledge Base article.
-
If this is a public facing article, include the “Still need help? Click the 'Purdue IT Request' button to start a ticket.” Further instructions regarding this step are listed below in Step 11.
-
In the Article Summary field, summarize the article. This is the description uses will see when searching for articles.
-
In the “Tag” field, search for product name (if applicable) and add.
-
Check “Notify Owner of Feedback”
-
In Internal Notes, add any notes that you want technicians to see, but not customers. Note: In TDX, internal notes are limited to 4000 characters and cannot use rich text, meaning no hyperlinks; if you need to include a link, use the full URL address.
-
If the article is complete; click the “Save” button, this will save the article as a draft it is not yet visible to other users.
-
The article draft is now available for submission, however, please consider the following:
-
If (in previous step 5) your article includes ““Still need help? Click the 'Purdue IT Request' button to start a ticket.” you will need to link the article to the service button.
-
Click the “Edit Article” button and then open the “Related Services” tab.
-
Click the “+ Add” button
-
Select the appropriate Service.
-
Select the related service. Typically this is the same name as the related service followed by the word ‘request’.
-
Click Save
-
On the Related Services table, click the “No” option under “Display Request for Service Button” which will change to “Yes”
-
This step is now complete.
-
How to create Internal team-only article permissions. (“Purdue IT Internal” articles do not need to follow this step; team leads will have instructions on how to approve IT-all articles)
-
Click on the permissions tab
-
Uncheck the “Inherit permissions” box
-
Uncheck the “public” box
-
Check “Allow ONLY the associated groups below to view this article.”
-
Enter names of TDX groups who can view this article.
-
Click Save.
-
In the "Next Review Date" select a future date when article should be reviewed. Standard practice is to set it one year into the future, however, if the information is likely to change before then, select an earlier date. Do not set the review date more than a year into the future - this ensures that articles are being reviewed at least annually. Only users with KB Contributor access or higher can set the review date; other users won't be able to see this option.
- Return to the article by clicking the article title at the top of the page. Review the article by using the Checklist for Internal and Public-Facing Knowledge
- If the article is ready for submission, select “Submit Article”. Copy the URL of the article and send an email to your team lead, letting them know the article is available for review; they will approve for addition to the knowledge base or reject submission if article is incomplete.
- If you do not have a team lead to notify about your article, or if you are the team lead and the article needs published to the public knowledge base, please use this form to create a ticket that notifies ITSMO that a knowledge base article is waiting for approval or publication: Click here to submit a notification to ITSMO that your knowledge base article needs published or approved.
For additional questions about creating a knowledge base article, click the Purdue IT Request button to submit a question to the IT Service Management Office.
Still need help? Click the 'Purdue IT Request' button to start a ticket.