Hi Maya and welcome to the RH community.
I am a little confused as to what you are trying to achieve. Have you a variable (e.g. client name) that can have three values and you want to use a build tag to produce the required value? If so, you could use:
NOT APPLICATIONA AND NOT APPLICATION B to output the variable for applicationC
NOT APPLICATIONA AND NOT APPLICATION C to output the variable for applicationB
NOT APPLICATIONB AND NOT APPLICATION C to output the variable for applicationA
You could even set-up different single source layouts for each scenario to prevent you having to change it each time. You can read about this here.
Read the RoboColum(n).
I'm looking at this and wondering why a simple variable won't work. If you have Adobe RoboHelp 6 or newer, you have Variables at your disposal.
Helpful and Handy Links
Thanks for the Response.
I will try making the scenario little bit more explanative:-)
Based on the user requirement, the OLH must be generated for the following combinations:
- OLH for Application A standalone
- OLH for Application B standalone
- OLH for Application C standalone
- OLH for Application A and Application C
- OLH for Application B and Application C
In all the HTMLs, in the header I have 'Client Name - Application Name', where in Application Name is conditionally tagged as Application A, Application B, Application C.
Thus while generating OLH for Application B and Application C, I used NOT APPLICATION A or APPLICATION B OR APPLICATION C. As required, the OLH does retrieve all the files that have been conditionally tagged as
- only Application B
- only Application C
- Application B, Application C
But at the same time, in all the retrieved files, the Header states Client Name - Application B Application C (as expected from RoboHelp based on the condition defined). The customized requirement needed is to display only Client Name - Application B when we generate an OLH for Application B and Application C .
There is no issue in the way OLH is generated for standalone scenario.
Isn't the real solution here to use variables rather than CBTs?
Am I understanding correctly that it is the application name that changes and not the client name?
Set the whichever it is as a variable and have a layout for each. When you generate the first one it will take the default of say Application A, the next layout you would set to generate Application B and so on.
Also, wouldn't merged help be a solution? You generate a project for each output and then mix and match.
See www.grainge.org for RoboHelp and Authoring tips