Discover the features to edit your published content with the pending versions in this article.
📝 Creation and publication of a pending version.
🎯 Why these pending versions?
😫 To update published content without these changes being directly visible to advisors,
⛔ To avoid changing content to “Draft” status when you update it because you do not want to generate downtime on the advisor side,
❌ To avoid duplicating content to modify it as this implies the loss of consultation data of the duplicated content,
✍ To update your published content with peace of mind and display all changes at once when these updates are ready.
🤔 How to use the feature?
Go to content (published or draft),
Click on the “Published” or “Draft” button or on the options menu “…” at the top right of the content,
Click on “Create a pending version”,
Write your changes on the pending version to avoid impacting the production version,
You can switch from the pending version to the production version and vice versa via this button:
Publish the pending version once you want to publish your updates,
✅ The production version is then replaced by the pending version in all available languages.
You can find this new version in the content version history. It is also possible to restore previous versions if you wish!
✅ What is currently possible:
Edit an entire article with a pending version.
Edit a guide with a pending version:
Edit the title and content of the guide or any of its steps.
Add/remove steps.
View the new structure through the tree view available in the pending versions.
Create redirect steps.
✅ It is possible to redirect a pending step to:
All published content (articles, guides, guide steps).
Other pending steps of the same guide, even if they do not exist in production.
This is not limiting; once the pending version is published, the redirect step will work.
❌ It is not possible to redirect a pending step to:
The pending version of another content.
A pending step of another guide if it does not exist in production.
Move a step.
⚠ A step from a pending version can only be moved within the pending version of the same content. It cannot be moved to another content.
Schedule the publication of the pending version.
As with regular content, you can schedule the publication of a pending version for a specific date.
At the chosen date (8:00 AM CET), it will be automatically deployed in all languages to replace the production version.
You retain full flexibility: change the date, cancel the scheduling, or publish instantly with one click.
Preview a pending version on Mayday Desk or Widget:
In your preferences, enable the option “Show pending versions”
From now on:
If the content has a pending version, you will see this version instead of the production version.
If the content does not have a pending version, the production version will be displayed.
This feature allows you to preview in real-time the appearance of your knowledge base with the pending versions before they go live.
❌ What will not be possible:
All metadata of content (labels, aliases, automations, etc.) are not included in a pending version. Only the title and content of the document are modifiable via a pending version.
⚠ Some important information:
All languages 🌍 are included in the same pending version. In other words, if you publish a pending version, it will replace the production version in all available languages.
A pending version is a copy of the content at the time of the creation of the pending version. If you modify your content while a pending version exists, these changes will not be reflected in the pending version.
When you publish a pending version, your content will be completely replaced by the pending version.
You should not edit content for which a pending version exists, but rather edit the pending version of this content, because upon publication, only the changes of this pending version will be applied.