Viewing Undefined Conditions

You can view a list of all files where you have condition tags in the content, but those condition tags have not been defined. This might occur, for example, if you have applied a condition tag in a topic and then later change the name of the tag or condition tag set. The old tag or set name is still used at the location where it was previously applied in the topic. Therefore, a problem exists. From the Undefined Condition Tags window pane, you can open the file in question and fix the undefined condition tag. You can also quickly rename or remove multiple condition tag occurrences in a single batch, add the undefined tag to the project, or map the undefined tag to an existing condition tag.

How to View Conditions

  1. Open a project.

  2. Do one of the following, depending on the part of the user interface you are using:

    • Ribbon Select Analysis > Undefined Items > Undefined Condition Tags.
    • Summary Window Pane Double-click the row that mentions undefined condition tags.

    The Undefined Condition Tags window pane opens, displaying a list of undefined condition tags.

  3. To see more of the information in the window pane, drag the divider bar to make the pane wider.
    • Condition Tag Displays the name of the condition tag set and the tag within it. The condition tag set is listed first, followed by a period and then the name of the condition tag (e.g., Primary.Print).
    • File Displays the name of the file.
    • Title Displays the properties title of the file (if any).
    • Folder Displays the folder where the file is found.
    • Tag Displays the tag being used by the condition tag.
    • Exclude ActionDisplays the kind of "exclude" action tied to the condition tag. In most cases, the exclude action is "remove." However, in some instances, this action might be "unbind." For example, you might have the unbind action for a condition tag if you have applied the tag to a hyperlink and want the link to be removed from the text in some outputs, but you still want the text to be shown in those outputs.
  4. If a certain number of items have been found, page navigation buttons in the local toolbar may be enabled. You can use these buttons to go to additional pages to display more items. You can also click View All in the local toolbar to see all results on a single page. Keep in mind that the more items you have in the project, the longer it will take to load this view.

How to Fix Undefined Conditions

There are a few different ways to fix an undefined condition tag: (1) You can rename the condition tag or condition tag set so that it matches what you have used in the topic; (2) you can reapply the condition tag in the topic so that it uses an existing condition tag set/condition tag; (3) you can add the undefined condition tag to the project as a new condition tag; (4) you can map the undefined condition tag to an existing condition tag; and (5) you can delete references in content files (e.g., topics, snippets) to the condition.

To Rename Conditions

  1. In the window pane, select all condition tag occurrences that you want to rename. If you want to select all rows click Click to select all rows.. You can hold the SHIFT key to select a range, or you can hold the CTRL key to select individual items.

    Note All condition tag occurrences that you select will be renamed to the same condition tag that you provide in the following steps.

  2. In the local toolbar, click the Rename button. The Rename Condition Tag(s) dialog opens.
  3. In the New condition tag name field, enter a new condition tag. Type the name of the condition tag set, followed by a period, then the name of the condition tag (e.g., Primary.Print).
  4. Click OK.

  5. A message lets you know how many files were changed. Click OK. All of the selected condition tag occurrences are renamed.

    Note If you want to undo the conversions, you can use the Backups window pane (View > Backups). See Restoring Backup Files.

To Reapply Conditions

  1. You can either double-click on the specific row, or right-click on the row and select Open.

  2. Reapply the condition tag to the content, selecting an existing name from a condition tag set. See Applying Conditions to Content.

To Add a Condition

  1. In the window pane, select all condition tag occurrences that you want to add to the project. If you want to select all rows click Click to select all rows.. You can hold the SHIFT key to select a range, or you can hold the CTRL key to select individual items.

  2. Do one of the following, depending on the part of the user interface you are using:

    • Local Toolbar Click Add a condition tag to the project..
    • Right-Click Right-click on the condition tag you want to add and from the context menu select Add New Condition Tag.

    The Condition Tag Set Editor opens, with the new condition tag(s) displayed.

    Note When you create a new condition tag, one of two things will happen:

    1. If the Condition Tag Set file specified exists in the project, Flare will add the new condition tag to the existing file.
    2. If the Condition Tag Set file specified does not exist in the project, Flare will create a brand new Condition Tag Set file and add the new condition tag to that file.
  3. (Optional) In the Condition Tag Set Editor, edit the condition tag's properties (e.g., name, color, comment).

  4. Click Save the active file. to save your work.

To Map a Condition

  1. In the window pane, select all condition tag occurrences that you want to map to an existing condition tag. If you want to select all rows click Click to select all rows.. You can hold the SHIFT key to select a range, or you can hold the CTRL key to select individual items.

  2. Do one of the following, depending on the part of the user interface you are using:

    • Local Toolbar Click Map to an existing condition tag..
    • Right-Click Right-click on the condition tag you want to add and from the context menu select Map to Existing Condition Tag.

    The Condition Tags dialog opens.

  3. In the dialog, select the existing condition tag in the project to overwrite the current undefined condition tag reference.

  4. Click OK.

  5. A message lets you know how many files were changed. Click OK. All of the selected condition tag occurrences are overwritten with the new condition tag.

    Note If you want to undo the conversions, you can use the Backups window pane (View > Backups). See Restoring Backup Files.

  6. Click Save the active file. to save your work.

To Delete References to a Condition

  1. In the window pane, select all condition tag occurrences whose references you want to delete. If you want to select all rows click Click to select all rows.. You can hold the SHIFT key to select a range, or you can hold the CTRL key to select individual items.

  2. Do one of the following, depending on the part of the user interface you are using:

    • Local Toolbar Click Use delete to empty contents..
    • Right-Click Right-click on the condition tag and from the context menu select Delete.
  3. Click OK.

Note This activity deletes the references to the undefined condition only. It does not affect your content file(s) in any other way.

What’s Noteworthy?

Note Another way to apply a different condition tag to many places throughout a project is to use the Find and Replace in Files feature in Flare. For example, let's say that you originally applied a condition tag named "Print" (from the "Primary" condition tag set) to a lot of content in your project. Later, you renamed the condition tag "PDF." You can perform a find and replace in your entire project. In the "Find" field, you can enter Primary.Print, and in the "Replace with" field, you can enter Primary.PDF. Also, make sure you select the "Find in source code" option in the Find and Replace in Files window pane. After replacing this text throughout your project, that condition tag will no longer be considered "undefined" in Flare. For information about using the Find and Replace in Files feature, see Find and Replace.

Note You can also include this information in reports that you create. See Reports.