Difference between revisions of "Knowledgebase Article Status Meaning"
Jump to navigation
Jump to search
(Created page with "Below are the statuses we have adopted to cover the typical life-time of a Knowledgebase Article: *Being Composed *Awaiting Approval *Approved for Publishing *Published *Ret...") |
|||
| Line 16: | Line 16: | ||
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). | 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). | ||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 09:32, 3 July 2018
Below are the statuses we have adopted 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).