Expiration Notifications Sent for Published Articles
over 13 years ago
| Article no. 3687
0 stars
0 ratings
THIS ARTICLE APPLIES TO:
Knowledgebase version 8.3.2 and above.
ISSUE DESCRIPTION:
Knowledgebase editors report they get article expiration notifications for published articles after publishing a new version.
ROOT CAUSE:
There can only be one published version of an article at a time. Each time an already published article has a new version made live, it causes the previous live version to expire. The expiration of the previous live version of the article causes a notification to be sent saying that the article's status has changed to workflow step Expired. At the same time another notification is sent saying that the new version of the article has been changed to workflow status Published.
SOLUTION OR WORK AROUND:
This is working as designed. While each version of the article is a distinct entity, only one can be published. When publishing a new version of an article, this dictates that the previous version must be expired. When this happens two workflow notifications are generated: one for each version of the article. One relays the older version has been expired, while the other informs the recipient that the new version has been published.
AFFECTED SYSTEMS & USERS:
Knowledgebase authors/editors who are set up to recieve workflow status notifications.
ADDITIONAL INFORMATION:
ESCALATION PROCEDURE:
If you have additional questions, please contact our Support team at 877-373-7848 (option 2) or via email at CIMSupport@moxiesoft.com.