Skip to main content
C
Cynthia Pao
Inspiring
July 18, 2019
Answered

Using Conditional Tags to Include Specific Topics in a Build

  • July 18, 2019
  • 1 reply
  • 1053 views

I have a conditional tag called DialogHelp in my project.

I've tried to build a version of the help that includes only the topics with this tag. However, when I compile, the resulting help has all of my topics in it.

According to the RoboHelp help, creating a build condition with this tag in it should generate help with only the tagged topics, yet this is not happening.

How can you generate a version of the help that includes only tagged topics?

Thank you!

Cindy

This topic has been closed for replies.
Correct answer Peter Grainge

Please see the Sticky Topic Before You Post and note the section Include the Edition and Version.

Generally in older versions Not expressions work best. In Topic List select all the topics not to be included (sort the list by tags and those with DialogHelp will be top or bottom, select the others and apply a different tag) and set the expression as NOT NewTag.

See www.grainge.org for free RoboHelp and Authoring information.

@petergrainge

1 reply

Peter Grainge
Community Expert
Peter GraingeCommunity ExpertCorrect answer
Community Expert
July 18, 2019

Please see the Sticky Topic Before You Post and note the section Include the Edition and Version.

Generally in older versions Not expressions work best. In Topic List select all the topics not to be included (sort the list by tags and those with DialogHelp will be top or bottom, select the others and apply a different tag) and set the expression as NOT NewTag.

See www.grainge.org for free RoboHelp and Authoring information.

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
C
Cynthia PaoAuthor
Inspiring
July 18, 2019

Thank you, Peter! You always have an answer that we can use.

I'm using RoboHelp Classic 2019, so why is this still a problem? Do I have to use the new interface to correct it?

I do see this as a bug, as the software is not behaving as documented. Would it be correct to open a bug?

Cindy

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
July 18, 2019

What I have described is the way Classic has always worked. With 2019 now being the way forward, I can't see it changing in Classic.

No you don't have to change and it may be best to stick with Classic for the time being. Just work round the problem in the way I have suggested. Changing is a bigger learning curve.

See www.grainge.org for free RoboHelp and Authoring information.

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices