Are there "best practices" for using Conditional Text?

Forum|Forum|9 years ago
November 3, 2016
1 reply
531 views

(Using Unstructured FM 11 in Windows 7.)

I have 30 years of legacy FM files with conditional text reflecting 30 years of company growth. When there were a few differences between models, this was fine. But as things grew, more and more conditions grew. Each file is looking more like a file folder, instead of a stand-alone file; some files have no unconditional text in them other than the title. When I turn on "show all" and "show conditions indicator," I get a rainbow. There are approximately 40 various conditions in our main system now, such that updating them is a nightmare.

I'm trying to get a good idea on some "best practices," so that any newly created manuals don't fall into this pattern. -- And perhaps I can figure a way to dismantle the still-live legacy documents.

And, no, we are no where close to being able to move to structures XML. I looked into that already and can't justify the cost. It's just me and one 25-year (seniority, not age) colleague who doesn't want anything to change, since he grew up with this system.

Indyrose

This topic has been closed for replies.

Arnis Gubins

Inspiring

What approach to Conditional text is being used, i.e. old FM style to "hide" content or new conditional expressions to "show" content?

Are you using text insets for some of the conditional content? This creates a more modular approach and may be easier to maintain with multiple conditions.

milmacroseAuthor

Known Participant

The old "hide" version. No text inserts. This illustration below is a typical book setup for an operator's manual -- we have around 15 base models with multiple variations of each base model. In some instances the differences between each file can be as simple as changing "gasoline" to "diesel" -- but in other files (specifications comes to mind), there is a distinctly different information for nearly each model and variation.

Keeping with the concept of sole-sourcing, many of the same parts/procedures are used in different models, which makes the text common across many models. It made sense when there were just a few models, but now... -- and our product line is growing. Each time we've added a product, we've added two conditional text tags (one for current-only and one for parts history).

Barb Binder

Community Expert

What a great question. It would be nice to see multiple contributors to a list of best practices.

I'll kick it off:

Mishandled spacing is a nightmare. In the case of changing gasoline to diesel, or updating phrases with in a paragraph, or sentences in a paragraph, make it a habit to always tag the leading space. For example, gasoline diesel
Or, consider only tagging whole paragraphs.
Condition Indicators: use either a line style or a background color (or both) as a condition indicator in addition to the color so that you can proof the leading spaces.
Use keyboard shortcuts: Control 4 to assign a tag, Control 5 to remove a tag, Control 6 to remove all condition tags from the selected text.
Consider assigning tags in the same order. For example, Get someone else to put gasoline diesel in your car truck so that your hands don't smell for the rest of the day.

~Barb at Rocky Mountain Training

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded