Knowledge Management architecture
Overview
A database forms the underlying element of the architecture. The is on top of the database and processes all data entered by applications. In addition, the is the workflow engine between the application and the database. It also verifies that a user has permission to perform each action, thereby enforcing any access control defined in the applications.
The also manages , the
, and , as follows:
- — Self-contained, shared module that helps you automate any approval or signature process. For more information, see the Using Approval Server to automate the approval-driven business processes documentation.
— it helps you to automatically assign requests to individuals. For more information, see the Configuration guide.
- — Search mechanism that is typically much faster than the native database searching functionality in long text fields. It is also the only search method available in for searching text within documents that are attached to requests. For more information, see Enabling and disabling full text search.
also uses several integrated modules and supporting applications that extend and enhance the basic functions:
Foundation — Contains the common forms, workflow, and data that are needed to support the applications. It also provides a repository for the following data structures that are used by each applications:
- Company (tenancy and external company definitions)
- Organization
- Location
- People
- Support groups
- Categorization
- Notification Engine — Provides a back-end workflow model for defining which notifications should be sent, based on different events in a application. Support staff uses the People form to define which notifications they want to receive. Included predefined notifications can be turned on or off.
The application components as well as the relationships among the database, , ,
, , the application's Foundation, Notification Engine and the applications are illustrated in the following figure:
product architecture
Main components
The application consists of the following main components:
- Self-service search interface — Entry point where users can search for knowledge from the knowledge base without accessing the application. Direct, user-friendly access to knowledge articles without the intervention of organizational members helps to reduce inbound call volume.
- Console (KM Console) — Location that lists knowledge articles in various lifecycle stages that are available to you, and relates to the functionalities according to your permissions. Based on your permissions, you can use the console to select an article for viewing or editing content and metadata.
Application components
consists of the following components:
- Knowledge articles
- Knowledge lifecycle management
- Knowledge search
has two types of knowledge articles:
AR form-based — Customers can use the registration tool in to define which forms and which fields on this form they would like to integrate with the knowledge base. Using the AR form rich text fields, you can include rich text formatting and can embed objects including images and hyperlinks in AR form-based knowledge articles.
uses the AR based knowledge articles to define the knowledge article templates. By default, provides the following knowledge article templates:- How to
- Problem solution
- Known Error
- Reference
- Decision Tree
- KCS Template
Because these templates are based on AR System forms, a knowledge article can have permissions assigned by group. This feature creates a knowledge article that has field-level and knowledge article-level security. You can assign knowledge article permissions to a knowledge article in the . Customers can create their own templates or modify and customize the existing templates by using the Developer Studio. They should use the Knowledge Management tool to register new templates.
- External Sources — Using platform ARDBC Plugins, can connect to any external knowledge source and can integrate that source into knowledge base as knowledge articles. By integrating into the knowledge base, these external knowledge items will include information like categories, update requests, feedback and workflow lifecycle management. is shipped by default with a connector to file systems. This connector enables external file system folders to be defined, and files such as PDF articles or Microsoft Word documents to be integrated into the knowledge base as knowledge articles. These knowledge articles are later indexed by the search engine and can be searched for like any other articles in the knowledge base.