This feature is supported in all outputs.
You can create tag expressions when performing any of the following tasks:
Most of these tasks have to do with condition tags. However, when exporting projects, you can also create expressions based on file tags. The process for creating file tag expressions is essentially the same as that for condition tag expressions. The following information describes condition tag expressions, but you can simply substitute file tags wherever condition tags are mentioned.
When you create tag expressions, you have the choice of working with conditions in Basic or Advanced mode. You can switch between the two modes by clicking Basic or Advanced in the user interface. You can use Basic if you are newer to condition tag expressions, or you can use the Advanced mode if you are experienced at writing condition tag expressions by hand. While the Basic section is easier for most people to use, it is also more limited in the type of expressions it can create.
With the Basic method, all of your work is done on the top half of the user interface, by just clicking check boxes. On the other hand, with the Advanced method, most of your work is done on the bottom portion of the user interface.
note
Note: If you are an experienced user and want to use the Advanced mode, you might find it helpful to begin with the Basic mode to create the initial expression and then switch to Advanced when you are ready.
The following instructions are based on the task "Associating Condition Tags with Targets," but the same principles apply to the other tasks. The only real difference is that this task affects the content that is included in the output. For example, the "Previewing Topics" task does not affect the output; it is merely a way to see temporarily how different condition tag settings would change a particular topic. And the "Global Project Linking" tasks affect which files are imported into a project, based on condition tag settings.
instructions for the basic method
In the Condition Tag Sets area, you can choose to view tags for all condition tag sets or you can select a specific set. The tags associated with the selected set are shown to the right, with their associated colors. An Include and Exclude check box appears next to each condition tag.
When Basic is selected, the check boxes are shown and the Advanced section is disabled.
example
example
If you want to exclude a condition tag, click the Exclude check box next to it. If you want to make sure a condition tag is included, click the Include check box next to it. The primary reason for having Include check boxes is to account for possible conflicts.
example
example
Suppose you have two condition tags—one called "Beginner" and another called "Advanced." Let's say that you have a
You have created a
By default, Flare will include content associated with both tags, unless you tell it not to. So you tell Flare to exclude the content associated with the Beginner tag. The problem is the middle paragraph from the
warning
Warning: If you do not select any check boxes at all, all of the tags will automatically be included. If you include only some tags and exclude others, any remaining tags without check marks for either Include or Exclude will automatically be included. However, if you select Include for any of the tags (even just one) and do not select Exclude for any tags, all of the other tags that do not have Include check marks will automatically be excluded. If you want to be safe and always know that the correct tags are included or excluded, you can make sure that all of the tags have check marks with either Include or Exclude.
When you click check boxes in the Basic section, you are creating expressions with "or" statements (e.g., "include this condition tag or that one"). And when you do this, you can see the resulting expression displayed in the Advanced section below.
example
example
instructions for the advanced method
If you are a more experienced user, you may decide to use the Advanced section to write expressions manually, rather than clicking check boxes. You can type the names of the condition tags as well as any of the following tokens: OR, AND, NOT, (). This allows you to produce more complex, robust expressions to control your output (i.e., "and" statements, as well as "or" statements).
copy from basic
When you select Advanced for the first time, the Basic section becomes disabled (i.e., the check boxes are hidden), and the Advanced section is enabled but empty (even if you've previously selected conditions in the Basic section). However, you can copy the expression from the Basic section to the Advanced section. This is a quick and easy way to create an initial expression and then tweak it with "and" statements.
example
double-click tags
Another trick you can use while working in the Advanced section is to double-click any tag from the Basic section. This adds the condition to the Advanced section so you do not have to type it. Just make sure your cursor has been placed in the Advanced section before double-clicking a condition tag. If you don't click in the Advanced section first, the newly added condition tag will overwrite all of the text you've entered previously in the Advanced section.
example
warning icon
When you type in the Advanced section, a yellow warning icon displays with relevant text if you have typed an error.
example
You can expect to see this icon quickly appear and then disappear as you type. However, if the icon remains after you finish, you can click it. The error will then be highlighted in the text below.
example
examples of condition expressions
Following are some examples of condition expression strings.
example—or
Primary.Website OR Primary.AllPrint
This is a simple expression that includes content that has either Website or AllPrint conditions applied to it.
So let's say you have a topic that looks like this.
In the output, you will see this.
example—and
Primary.Website AND Primary.AllPrint
This expression includes content that has Website and AllPrint conditions applied to it. However, the output can also include other conditions not listed in the expression, since they are not explicitly excluded.
So let's say you have a topic that looks like this.
In the output, you will see this.
Notice that the second sentence is included even though it contains not only the AllPrint and Website conditions, but also the PDFA and PDFB conditions.
example—and/and not
Primary.Website AND Primary.AllPrint AND NOT Primary.PDFA
This expression includes content that has Website and AllPrint conditions applied to it. In addition, it specifically excludes content with the PDFA condition.
So let's say you have a topic that looks like this.
In the output, you will see this.
The second sentence with both Website and AllPrint does not display in the output because the PDFA condition is in that sentence too, and it was set to be excluded.
example—and not (and)
Primary.Website AND NOT (Primary.AllPrint AND Primary.PDFB)
This expression includes any content with the Website condition applied to it. In addition, it specifically excludes content with both the AllPrint and PDFB conditions.
So let's say you have a topic that looks like this.
In the output, you will see this.
The sentence that had both the AllPrint and PDFB conditions was excluded. However, another sentence that has the Website and PDFB conditions was included. That's because the exclusion only occurs if both the AllPrint and PDFB conditions have been applied to the sentence.
warning
Warning: When you switch between the Basic and the Advanced view, your work is preserved independently in both. However, be cautious when using the copy button. Because of the way this feature is designed, it is a best practice to use either the Basic section or the Advanced section in the long term, but not both. Although it is possible to copy expressions from the Basic to the Advanced section, and this can save you lots of time, you should not try to switch between sections over time. The reason for this is that every time you make changes in the Basic section and click the button to copy the expression to the Advanced area, your previous advanced expression will be overwritten.
note
Note: When you generate the target, Flare uses the expression from the section that is selected—Basic or Advanced.
