The recommended way to search for Knowledge Articles in the Knowledge Base is to use the search field in the top-right of the Client Portal.
This article will explain the reason for and activities around aligning the Service Catalog in TDX with the MSU IT Service Portfolio.
Details about tags in the Knowledge Base and how they should be used.
TeamDynamix weights searches based on several criteria, which are described in this article.
TeamDynamix allows certain operators to modify searches and refine results from the Client Portal and Knowledge Base. This article covers what is available for the Full Search option.
This article gives guidance to how knowledge articles should be structured and written in the TeamDynamix Knowledge Base.
What templates are available to use in Knowledge Articles and how are they used?
Articles are ordered first by article type, then by the device / OS at issue, then alphabetically within those groups.
When no longer needed, articles are archived to removed them from active view. They still remain in the system, but will not be broadly accessible to customers.
This will guide you through the process of creating a new knowledge article in MSU IT's TeamDynamix system.
Following these steps will make changes to an existing knowledge article and either publish it directly or submit it for review and publishing.
Following these steps will bring up a report showing all Knowledge Base Articles (KBAs) owned by a Support Group you are a member of.
All articles are subject to a six month review period. This article goes over the process of reviewing them at that time.
This article details how to successfully complete the assigned Task called "SME Reviews Article Content for Accuracy and Relevancy", which is generally used as part of a KB Gaps Request. This process helps ensure that inaccurate or missing knowledge is corrected or added to the Knowledge Base for future use.
Following the steps in this article will determine the category where a new knowledge article should be created.
This process enables an individual to purchase an MSU-owned asset while ensuring that all MSU-owned software and information is securely removed and the IT Access Management (ITAM) Repository is updated accordingly.