Product feedback: your Autocomplete experience in Publication Manager

Hello community,

Our Product team is currently working on bringing the Autocomplete feature to the Publication Editor on the web. 
As part of this process, we’d love to learn how your team currently uses Autocomplete feature in Publication Manager.  

Autocomplete dialog with options to select Baseline, Candidate for Baseline, Latest released versions, Latest available versions, or First versions.

Updating Baseline dialog asking if the user wants to overwrite version '1.1.1' of the object 'What is caving?' with version '2'.

Please vote below for the option that best matches your team’s typical practice: 

Please share more context in the comments — when and why does your team use these options or maybe why don't you :) ?

Your input will really help us shape the web experience. 



-
[edited by: Kseniia Kurganskaia at 2:59 PM (GMT 1) on 8 Oct 2025]
emoji
Parents
  • This survey is missing options, and it should be a multi-select survey for the options it has. Our real answer is, "We use autocomplete frequently in both 'Yes to all' and 'Yes/No' mode, depending on the document."

    We often document multiple related products in a product family, and we share bookmaps and/or chapter maps between them. We typically do our primary authoring using the most featured product, and then we autocomplete the other publications against the baseline of the primary publication. We try to keep all the related product manuals on the same version of each topic so that we can use a "Yes to all" completion, but sometimes there are enough inconsistencies between the products themselves that we must select yes/no for each object.

    For ISPI documents, we always use autocomplete to roll up to the latest version of all content. Because they contain sensitive, pre-approved legal and certification content, we must always use the latest, most updated version.

    For us, autocompleting baselines is a must-have feature, and we would not want to lose any of the existing options. It's critical that we can complete either to the newest or to a specific baseline. We require the ability to select each object in some instances, but the "yes to all" option is a big timesaver when we know that our document strategy allows for it.

    emoji
Reply
  • This survey is missing options, and it should be a multi-select survey for the options it has. Our real answer is, "We use autocomplete frequently in both 'Yes to all' and 'Yes/No' mode, depending on the document."

    We often document multiple related products in a product family, and we share bookmaps and/or chapter maps between them. We typically do our primary authoring using the most featured product, and then we autocomplete the other publications against the baseline of the primary publication. We try to keep all the related product manuals on the same version of each topic so that we can use a "Yes to all" completion, but sometimes there are enough inconsistencies between the products themselves that we must select yes/no for each object.

    For ISPI documents, we always use autocomplete to roll up to the latest version of all content. Because they contain sensitive, pre-approved legal and certification content, we must always use the latest, most updated version.

    For us, autocompleting baselines is a must-have feature, and we would not want to lose any of the existing options. It's critical that we can complete either to the newest or to a specific baseline. We require the ability to select each object in some instances, but the "yes to all" option is a big timesaver when we know that our document strategy allows for it.

    emoji
Children
No Data