Knowledgebase Document Status Meaning: Difference between revisions
(Created page with "Within the knowlegdebase documents we have adopted the following statuses to cover the typical life-time of a Knowledgebase Article: *Being Composed *Awaiting Approval *App...") |
No edit summary |
||
Line 1: | Line 1: | ||
Within the knowlegdebase documents we have adopted the following statuses to cover the typical life-time of a Knowledgebase Article: | Within the knowlegdebase documents we have adopted the following statuses to cover the typical life-time of a Knowledgebase Article: | ||
*Being Composed | *Being Composed | ||
Line 9: | Line 10: | ||
Please note that this is SEPARATE from "Visible to public". | Please note that this is '''SEPARATE''' from "'''Visible to public'''". | ||
Provided the article is visible to the public, customers who have subscribed to the parent catalogue, get a notification on the creation of a new document. | Provided the article is visible to the public, customers who have subscribed to the parent catalogue, get a notification on the creation of a new document. |
Revision as of 09:28, 3 July 2018
Within the knowlegdebase documents we have adopted the following statuses to cover the typical life-time of a Knowledgebase Article:
- Being Composed
- Awaiting Approval
- Approved for Publishing
- Published
- Retired
Please note that this is SEPARATE from "Visible to public".
Provided the article is visible to the public, customers who have subscribed to the parent catalogue, get a notification on the creation of a new document.
On any change in the document, subscribers (customers/analysts) to the document get a notification. Please note that for a CUSTOMER to see (and subscribe) to a document, the document will have to be PUBLISHED and Visible.
The other statusses are to aid the KB manager(s) so content can be curated more precisely - (i.e. get in a state appropriate to be read by customers).
Customers can subscribe to a document via the WSS.