HEX
Server: Microsoft-IIS/8.5
System: Windows NT YDAWBH120 6.3 build 9600 (Windows Server 2012 R2 Standard Edition) AMD64
User: tentjecom_web (0)
PHP: 7.4.14
Disabled: NONE
Upload Files
File: D:/HostingSpaces/LHouwen/dokuwiki.logic.nl/wwwroot/data/pages/crm/kb-article.txt
====== Knowledge Article ======
This section of Dynamics 365 functionaly is currently only available in the new UI tab "Customer Service Hub". When you select this Topic from the //Navigation Bar//, a new explorer window opens and you are redirected to the new UI with a list of //Active Articles//.

===== Creating an Article =====
 The creation and publication of an articel is a //Business Process//:
  - An article is created by an Author
  - It is Reviewed by someone else
  - There may be several review iterations
  - Then it is Approved and receives the Status //Published//.

Logic's current business process ends with the status //Approved//. We cannot publish an Article at current. Remember when you are searching for an Article that you set the search Status to //Approved//. By default this is set to //Published//.

The creation and modification of Articles is done with the help of the new //Unified Interface// platform. This is the next generation of User Interface which is not yet in full available for our on-premise version.
The new UI is availabe in the //Customer Service Hub// area. When you select //Knowledge Articles// from the Navigation menu, the //Customer Service Hub// is opened automatically.

**Note:**
Once you are in the //Customer Service Hub//, you cannot return to the conventional user interface: you have to close the window and open an new Dynamics session.

===== Article Sections =====
There are four sections that need to be completed before an //Article// can be published:

==== Title ====
Choose the //Title// with care: its content is used to perform an intelligent search and match when someone is looking for a KB-Article for a particular //Case//.

==== Keywords ====
Like the //Title//. Keywords are used when searching for KB-Articles. Good practice is to add words (separated with komma's) that identify the KB-Article to a //Product//, Supplier, Chip, license type, usage etc.

==== Description ====
Explain what kind of problem is being solved in the Article, or what a recommended course of action is for a problem, or what Question you are answering in this Article.

==== Content ====
This is the //Content// that is being published an that is sent to Customers. It should at least consist out of three sections:
  - Always start with an introduction describing the problem or the question you are going to solve / answer.
  - Next plain what needs to be done in good details and if nescessary with screenshots and imoages.
  - Last is a short conclusion and redirect back to Logic in case of any problems or suggestions.