Ideate Annotate>Tag for Revit requires the presence of project-defined rules in order to work. To manage the rules in your project, follow these steps.
Instructions for sharing rules any customized rules is also included within this help topic.
Default rules are shown in italics within the Tag window (#4). A default rule is created to correspond to each loaded tag family when there is not corresponding rule already loaded into the project. In the image above, for example, the Air Terminals : Default is created on the fly because there is no rule loaded in the project for Air Terminals. If a rule is created in the project then the default room will no longer display.
When Annotate is started for the first time, tag rules are loaded only when a corresponding tag family is already loaded into the project. For example, the sample rule called Walls-Exclude will not load unless there is at least one wall tag family loaded. These sample rules are loaded from the libary location as specified in Settings>Rule Library Path which can also be accessed from the cog (#1) and can be customized and deployed to all users. As long as at least one rule is already present in the project, Ideate Annotate will not attempt to load any sample rules.
To learn more about the purpose of each sample rule, refer to Sample Content.
Once a rule is loaded into a project, it will be saved within the project for future use. If a rule is modified within the project, the modified version is only saved within the project. Customized rules can be shared with other Revit projects through the process of Import, Export, Imbedding in a Template, or by forcing a Reload from the default location.
To share a new or modified rule from within a Project:
To import a rule from another Project:
It is not necessary to manage rules by embedding them in the template, simply because they can be easily managed via the method described within the Default Rules topic. If, however, you prefer to embed Rules within a template, this can also be done. Be aware that using this method will ensure that new Rules will never be loaded from the path specified under the Rule Library Path.
If the standard rules have been updated on the network or a local drive you can force an automatic update of all rules by deleting all project rules and ensuring that the Default Path points to the desired folder location.
Thank you for taking time to inform us about a bug or feature request.