Rules for Global Project Linking

If you use the Global Project Linking feature to import files from other projects, you should be aware of the various rules at play, depending on the settings you choose. See Global Project Linking—Importing Files From Other Projects.

  • Include Files Required The Include Files field is mandatory. You can use wildcards, add specific file names, and specify multiple kinds of file types to include.
  • Auto-reimport Memory If you use the Auto-Reimport check box, Flare will remember to not import any files that you have told it to exclude (either by using the Exclude Files field or by deselecting check marks in the Accept Imported Documents dialog). Flare will only import files that you told it to include (or did not specifically tell it to exclude), thus bringing in any new files added to the source project or any changes to files that you have imported before. If a file in the current project is newer than the same file in the source project, the source file will not automatically replace the current file.
  • Exclude Files Not Required The Exclude Files field is optional. You can use wildcards, add specific file names, and specify multiple kinds of file types to exclude.
  • Condition Tags Not Required, But Recommended The Import Conditions section is optional. It lets you include or exclude files that have any condition tags applied to them at the file level. If you decide to take advantage of Global Project Linking, it is highly recommended that you use condition tags when doing so. By applying condition tags to your files (e.g., topics, images, stylesheets, page layouts), you can more easily control which files are imported into (or excluded from) a particular project. This is especially true if you elect to use the "auto-reimport" feature, which automatically imports files that you specify when you generate targets.
  • Condition Tags > Include Files If you complete both the Include Files field and the Import Conditions section, the condition tags specified take precedence over what you have specified in the Include Files field.

    Example If you tell Flare to include all topic files, but you have excluded condition tags that are applied to some of those topic files, then those topics will not be imported.

  • Exclude Files > Include Files If you complete both the Include Files field and the Exclude Files field, the exclude files that are specified take precedence over the include files.

    Example If you accidentally specify "All Topic Files" in both fields, then no topic files will be imported.

  • Exclude Files > Condition Tags > Include Files If you complete the Include Files field, the Exclude Files field, and the Import Conditions section, the exclude files field takes highest precedence, then the condition tags, then the include files.

    Example You have specified "All Topic Files" in the Include Files field. Furthermore, 30 percent of those files have an "advanced user" condition tag applied to them, and the other 70 percent have a "beginning user" condition tag applied. You have told Flare to include the files with the "advanced user" condition tags and to exclude the files with the "beginning user" condition tags. Finally, in the Exclude Files field, you have specifically typed the file name "My Big Topic.htm," which has an "advanced user" condition tag applied to it. In a case such as this, Flare imports all topic files that have the "advanced user" condition tag applied, except for the file "My Big Topic.htm," which it will not import.

  • Exclude Files > Auto-include Linked Files > Condition Tags If you complete the Exclude Files field and the Import Conditions section, as well as select the "Auto-include linked files" check box, the exclude files takes highest precedence, then the auto-include files, and finally the condition tags.

    Example You have specified "All Topic Files" in the Include Files field. Furthermore, 30 percent of those files have an "advanced user" condition tag applied to them, and the other 70 percent have a "beginning user" condition tag applied. You have told Flare to include the files with the "advanced user" condition tags and to exclude the files with the "beginning user" condition tags. You have also told Flare to automatically include files that are linked from the files that you are specifically importing. Finally, in the Exclude Files field, you have specifically typed the file name "My Big Topic.htm," which has a "beginning user" condition tag applied to it, but there is an "advanced user" topic that links to that file. In a case such as this, Flare will import all topic files that have the "advanced user" condition tag applied. It will also import any "beginning user" files that are linked from any "advanced user" files. However, because you have specifically told Flare to exclude the file "My Big Topic.htm," it will not be included in the import.

  • "Domino" Effect for Auto-include Linked Files If you select the "Auto-include linked files" check box, Flare will import any linked files it finds, even beyond the first level. Not only will the immediate linked files be included, but any linked files from those files as well, and so on. It is a "domino" effect until no more linked files are found.

    Example You have told Flare to import just one topic called "My Big Topic.htm," but you also tell it to automatically include any linked files. If "My Big Topic.htm" contains a cross-reference to a topic called "My Little Topic.htm" and it also contains a picture called "My Image.png," Flare will import all three of those files. Furthermore, let's say that "My Little Topic.htm" contains a hyperlink to yet another topic called "My Medium Topic.htm" and a link to a snippet called "My First Snippet.flsnp." Therefore, Flare will also import those two files, and it will scan those files for further links that may need to be imported.

  • Files Without Condition Tags Included If you use the Import Conditions section to include and exclude files based on condition tags applied to them, but a few files do not have condition tags, those files will be included in the import. However, you have the option of removing the check mark from those files in the Accept Imported Documents dialog to exclude them from the import.
  • Memory in Accept Imported Documents Dialog After you perform an import the first time, all of the files in the Accept Imported Documents dialog will have check marks next to them, meaning they will be imported. However, you can deselect any specific files in that dialog if you decide not to import them. The next time you perform a reimport, those files will still show up in the Accept Imported Documents dialog, but they will remain unchecked because Flare remembers that you wanted to leave them out of a previous import. If you click the check boxes next to them to add check marks, those files will be imported.
  • New Files Contain Check Marks After you have performed an import, you might add new files to the source project. If you then perform a reimport, those new files will automatically have check marks next to them in the Accept Imported Documents dialog (unless you specify beforehand that they should be excluded).
  • Green=Source Newer, Red=Local Newer Let's say that you have imported several files from a source project, and then later you perform a reimport. If Flare recognizes that the same files in the two projects are not identical, it color-codes them in the Accept Imported Documents dialog. If the source file is newer than the file in the current (local) project, the file is shaded in green and a check mark appears next to it (indicating that it will be imported and therefore replace the local file). If the local file is newer than the file in the source project, the file is shaded in red in the Accept Imported Documents dialog, and a check mark does not appear next to it (indicating that the file will not be imported, replacing the local file, unless you manually add a check mark).