This functionality is only available for certain module packages. Info / Copyright

Tab Templates (Dialog Model views, Copper unfolds, Drilling views)

On this tab you create and edit templates for the automatic generation of model views, copper unfolds or 2D drilling views. The templates only contain specifications for the formatting of the model view to be generated, and for which basic items separate views are to be generated. Geometric information is not contained. The automatic generation of pages is carried out on the basis of templates in the dialog Model views – <Project name> on the Templates tab either by using the button (Generate report) or in the tree view by using the Generate report popup menu item.

Overview of the main dialog elements:

Project name:

The report templates contained in the project for model views, copper unfolds or 2D drilling views are displayed in the tree structure.

Toolbar:

The following buttons are available on the toolbar above the tree structure:

Button

Meaning

(Generate report)

Generates model views, 2D drilling views and copper unfolds on the basis of the settings carried out in the Templates tab.

(New)

Generates a new template whose name is incremented beginning with 1. The name can be modified subsequently in the properties table.

(Delete)

Removes the selected templates from the list.

(Import)

Opens the Import report templates dialog. This enables you to import a report template.

(Export)

Opens the Export report templates dialog. This enables you to export a report template.

Popup menu:

The popup menu of the tree view on the Templates tab contains the same menu items as the buttons on the toolbar.

Property name / value table:

The properties and values of the highlighted reports that can be set for the generation of templates are displayed in the columns of this table.

Property

Value

Name

Name of the template

Start page of report block

Start page for all pages that are generated automatically with this template. Click [...] to open the Start page dialog.

Filter setting

Filters the basic items for which one page each with a model view is to be generated automatically. The [...] button opens the Filter dialog.

If a selected basic item is not contained in the project, no model view is generated for it.

If no basic item is specified, a model view is generated for each layout space of the project.

Sort setting

This is used to set the sorting of the basic items with which the model views are generated. The [...] button opens the Sorting dialog.

Functions: Filter setting

Only for model views. This is used to set which functions of the basic items or which hierarchically subordinate items are displayed in the model view. The [...] button opens the Filter dialog.

Trade

The set trade is assigned to the generated page.

Manual view description

If the Automatic view description check box is deactivated, a view description can be entered here.

Automatic view description

If the check box is activated, the view description is generated automatically from the Format for automatic description property.

Format for automatic description

This is used to set the format for the automatic view and page description. The [...] button opens the Format: Property dialog.

Manual page description

If the Automatic page description check box is deactivated, a page description can be entered here.

Automatic page description

If the check box is activated, the page description is generated automatically from the Format for automatic description property.

Page sorting

The [...] button opens the Page sorting dialog. The meaning of the Page sorting setting is identical to the project-specific Reports > Output to pages setting of the same name.

Macro

The macro set here is used for the page output of a view. The [...] button opens the Select macro dialog. Window, symbol and page macros can be selected.

Note:

Macros are not stored in the project after being inserted. For the case that a project with report templates is copied or passed on to a different user, it has to be ensured that the macro set in the template also exists in the macro directory of the respective user.

See also: