Skip to main content

We have articles in our Knowledge Base that need to be updated, but it may take more time than the author has at one time. Similar to git version control, we want to create a new ‘branched’ version of the content, edit it in a draft state until it’s ready, then merge the changes with the published version.

Hi @chelsea.cowley, thanks for submitting this idea! I would like to ask a few follow up questions on this :slight_smile:

  • Do I understand correctly that you would like to keep the existing article visible while working on the draft update?
  • How do you envision this working in combination with the current edit feature? Do you like to have the draft edit replace the existing edit feature or have the possibility to do both draft edit and direct edit at the same time?
Updated idea statusNew→Open

Hi @janina.woita - thanks for looking into this!

  • Do I understand correctly that you would like to keep the existing article visible while working on the draft update?

Yes, that’s correct.

  • How do you envision this working in combination with the current edit feature? Do you like to have the draft edit replace the existing edit feature or have the possibility to do both draft edit and direct edit at the same time?

I would like to have the draft edit replace the current direct edit feature. This would mean that there would need to be some indicator on articles that have a draft that’s pending publishing when they are viewed by users with Control access, and those users would need to be able to either need to be able to collaboratively edit or the article would need to be locked to only the person who initiated the edit.

@chelsea.cowley thanks for elaborating! :slight_smile:

Agree this would be an extremely helpful feature.

We release platform updates in a 2-week cycle and I have 1 week to update our existing guidance to reflect any changes.  This involves editing already published guidance.  Being able to make changes but leave the new edits in draft until the day of release would make a big impact.  The current workaround is to make a copy of the existing guidance, make my updates and copy/paste the updates on the day of release and delete my draft.

This should be standard content functionality - we often have to update existing articles to account for UI or feature changes and don’t want to create NEW articles to replace them. There should be a “save Draft” function when editing an existing article and some view where I can see all pending drafts.

This would be extremely helpful and should be standard functionality. Sometimes we have as many as 50 articles to update for a release and need to work on them ahead of release date. The copy/paste option is very clunky and difficult for such a large workload. 

This would be so helpful!!! Please keep us posted on the status of this.

This would be very helpful and this is functionality that is available in Salesforce Knowledge base.

Terms & ConditionsCookie settingsAccessibility statement