As introduced in the Flight Plans Concepts topic, Flight Plans Tags are essentially labels applied to each member in the Flight Plan that can be used to help organize and sort members into meaningful categories. Flight Plans uses curly brackets ({TagName}) as a syntax to indicate the value for a particular tag, i.e. {YourTag} would get the value for YourTag of the selected member. This topic covers the built in tag-categories as well as the various fields of the Tag Values Frame.

Tag Values Frame

The Tag Values frame (which takes up most of the Flight Plan window) shows each tag in the current Flight Plan as it applies to the selected member or members. Tag Name is shown in the column on the left and the Value of each tag on the right.

Clicking on a tag title will select it, and the tag's description will appear in a box toward the bottom-right of the dialog. Double-clicking on any tag value that isn't greyed out will allow the user to change it, either by typing in a new value or by selecting from a dropdown list. All values that are changed from their defaults will appear in bold.

Clicking on the "minus" button () to the left of the Tag Value will restore it to its defaults.

Clicking the Alphabetical button at the top of the dialog will remove the categories and sort the tags alphabetically. Clicking the Categorized button at the upper left will restore the default categorical view.

Checking the Apply new tag Values to Matching source checkbox, unchecked by default, will copy any changes made to the tag values to the tags of any "matches" associated with the selected member or members.

Tag Categories

By default, tags are divided into six categories:

  • Origin - Machine-defined tags applied by Wings as soon as a file is indexed by Flight Plans. These are the only type of tags that cannot be altered by the user.
  • User - Entirely user-defined tags used to give files meaningful, easily-readable attributes and sort them into customized groups that aren't detected by default (team, color, department, et'c).
  • Import – Tags related to the import process of the file. Automatically defined by Wings, but can be altered at user discretion.
  • Export – Tags related to the export process of the file. Automatically defined by Wings, but can be changed at user discretion.
  • Handler – Tags related to the modernization process and the F-Spec Handler keyword. Automatically defined by Wings, but can be changed at user discretion.
  • Options – Tags that define how and where the files are shown in the Flight Plan window.

Key Modernization Tags

There are eight tags that are absolutely critical to the modernization process; it's strongly recommended that users check these tags to make certain they're in line with the modernization plan before converting any files. The fastest and simplest way is to set their defaults in the Edit Tags dialog before making any other changes.

By category, the key tags are:

  • Import
    • DefaultTemplateFolder - Location of Monarch Cocoon's Templates.
    • Language - Specifies the code-behind programming language. Defaults to C#, can be set to VB.NET or AVR via dropdown.
    • LibraryList - Specifies the library list used for resolving field references. Defaults to {Library}, can be set to any valid library.
    • Namespace - Namespace used in the generated code. Defaults to {Library}, can be set to any valid namespace.
    • TargetPath - Specifies the path to the folder the .aspx file will be placed in. Tags can be used with the format {tagName}. Defaults to C:\{Library}\{File} but can be set to any valid filepath.
  • Export
    • DDSLocation - The library and file where the generated DDS will be saved. Defaults to {Library}X/QDDSWINGS.
    • DisplayFileLocation - The library and file where the Display File will be saved. Defaults to {Library}X/{Member}.
  • Handler
    • TargetQualifiedMember - Library/File/Member names to be used for members with the Handler keyword injected. Defaults to {Library}/QRPGWINGS/{Member}, but can be set to any valid path.