🚀 go-pugleaf

I'll chime in, but I'm basically going to repeat what Russ has just said. Whether you use XML or structured FrameMaker, the best method of identifying "conditions" is to use attributes and their values. If your condition is a customer, for example, you might have a "Section" element with a "Customer" attribute, which you give values of "CustomerA", "CustomerB", "CustomerC", etc. Something like that.

The problem, as Russ said, is that you can mark up attributes and values all you want, but then you need to process them to create your desired output (such as "CustomerA" but not "CustomerB" or "CustomerC"). FrameMaker itself does not do this unless you use conditional text. And since conditional text is an unstructured tool that has no real relationship to structure, you'd have to do complex search and paste operations to conditionalize output. It can be done, but it's neither fast nor 100% accurate.

Russ pretty much covered the other options that I am aware of: (1) XML/XSLT, (2) FrameMaker plugins, or (3) custom FrameScript or FDK work. Whichever method you choose, you are going to see amazing benefits over conditional text (if that is what you are using today). Conditional text is difficult to work with and rather limiting, particularly when you require overlapping conditions. Better solutions are out there, but you will need something beyond FrameMaker itself.

Gary