In a project without source control I was able to apply tags to a parent folder and sub folders quite independently without any problem.
My own way of working would be to apply a tag called Hazard and exclude that from builds not requiring those topics.
There is an argument for supplying the help for all modules as they will not have the functionality but might want to buy it when they see what it does. Of course, there can be valid reasons against doing that but it is worth thinking about.
See www.grainge.org for RoboHelp and Authoring tips
I am working on my project in source control, and I got an error message when RH tried to check out files to apply the tags: "The files in the list below could not be checked out from version control [even though they were checked in!]. Exclusive access to these files is required to execute the selected action." To resolve this I have to check everything in and shut both RH and Visual Studio down.
That said, for the first folder I right-clicked the folder, clicked Apply Conditional Build Tag, selected or created the tag, checked out the files when prompted, and had no problems. It was the subsequent folders where this did not work.
However, in reading the Help, I noticed that the instructions tell you to select the folder, click Format, etc. And it worked.
Now I can check to see whether my build expressions work as desired.
I've applied "Hazard" and similar tags to each of the Help folders associated with the licensable modules and Main to all the other Help folders. I've built an expression in each output to exclude all but the one appropriate module. And it works.
The company does have valid reasons for not including functionality that is licensed; in other companies we have included everything for the reason that you note.
Thanks for your help.
My spidey sense is tingling and telling me that maybe you are thinking of folders and conditional tagging incorrectly.
When tagging a folder, it's a *SINGLE SHOT* that says "apply this tag to all topics inside this folder."
Often, folks will misunderstand this and think they are somehow configuring a situation whereby anything they later place inside the folder is tagged. But that's not the case. If you later add content to the folder you will need to tag it.
Helpful and Handy Links