Macros contain a sequence of instructions or declarations under a certain name, in order to execute these with one simple command (instead of the single commands).

See Section 2.2.12.2, “ Block [Macros]”.

Explanations on categories can be found under Section 2.2.1.1, “ What are categories? ”.

Example:

is2d

The expression is valid, if the document is a 2D element.

Object is a catalog

Object is a project

Document is a 2D element

Document is a 3D element

Document is a native part

Document is a 3D assembly

Document is a 3D part

Document is a INCH part

Document is a MM part

Document is not a top level element

Document is a top level element

Document is a sub-assembly

Document is a sub-part

valid for a negativ part

For fasteners such as screws, nuts, rings, pins, etc., cutting can be excluded in the 2D view.

Note

The block is disabled or not existing by default. With V11, the required parts are classified accordingly in the project itself. See Section 5.12.4, “ Add projects to classification (context menu) ” in eCATALOG 3Dfindit -> Classification (CNS) -> Fasteners such as screws, nuts, rings, pins, etc.. In exceptional cases interaction via configuration file by consulting is possible. See Section 2.2.12.6, “ Block [NoSection] ”.

Semi finished products can be declared as such.

Note

The block is disabled or not existing by default. With V11, the required parts are classified accordingly in the project itself. See Section 5.12.4, “ Add projects to classification (context menu) ” in eCATALOG 3Dfindit -> Classification (CNS) -> Semi-finished products. In exceptional cases interaction via configuration file by consulting is possible. See Section 2.2.12.7, “ Block [RAWMATERIALS] ”.

Default callbacks. You can customize the callbacks here (or overwrite them in the specific interface configuration).

For examples see help entries in config itself.

Design of PARTsolutions interface menu and toolbar

Details on this can be found under Section 2.2.2, “Configuring PARTsolutions interface menu and toolbar ”.

Mostly path to resources

Also see Section 2.2.12.4, “Block [Placement]”.

Mappings 1 to 7 create the mapping for the material

First choice is the "MAT_NAME" column in the characteristic attribute table (used with ERP integration). Second choice is the "virtual" column "CNSMAT" (without ERP integration).

See also Section 2.2.12.5, “ Block [ClassMapping]”and Section 2.2.9, “Material mapping ”.

Part extensions

The CAD extensions should be administrated here (used e.g. by plm interfaces)

Assembly extensions

The CAD extensions should be administrated here (used e.g. by plm interfaces)