TAG | ATTRIBUTE(S) | DESCRIPTION |
<database> | Top-level required tag. | |
<mappings> | Second-level required tag | |
<cadPropertyMapping> | If you have multiple CAD systems and the mappings are the same for all of them, you can have a single <cadPropertyMapping> section with a <modelFilter> tag (see below) that specifies multiple "modelerTypes" attributes. For different mappings, use multiple <cadPropertyMapping> sections, each with its own <modelFilter> tag specifying the "modelerType" attribute for the specific CAD system. | |
<modelFilter> | modelType modelerTypes | Defines the kind of model and what CAD system produced it, as well as the path to the file (optional). Valid values are: ASSEMBLY PART Valid values can be any combination of space-separated: PROE CATIA NX SOLIDWORKS and/or STEP For example: <!-- may specify multiple modelers, model type and cadFileRegEx --> <modelFilter modelerTypes="PROE CATIA NX STEP" modelType=" PART ASSEMBLY"> |
<mapping> | Contains a source/target mapping pair. | |
<source> | name id | Each <source> tag much specify at least one named CAD property to be mapped. You can specify the name by attribute, or you can use the <name> tag (see below), particularly if you wish to map to multiple properties. If you specify multiple <name>tags, the first one to match takes precedence. If you specify both a name attribute and one or more <name> tags within a <source> specification, the attribute takes precedence. Note: For NX attributes that are defined under a category, use the vertical bar (“|”) to separate the category and attribute. For example: <source name="MyCategory|MyAttribute"/> The id attribute was added in 2018 R1 and is only needed if your <mapping> element needs to access the <source> via a CSL expression. See also the <expression> tag. |
<target> | name type | Name of the aPriori attribute to be mapped. Note: This is NOT the display name. The type of aPriori attribute to be mapped. Valid values are: uda system If not specified, "uda" is assumed. |
<name> | Same as the <source> "name" attribute (see above). If you use multiple <name> tags within a <source> tag (for mapping multiple properties to a single aPriori attribute), the first match takes precedence. If you specify both a name attribute and one or more <name> tags within a <source> specification, the attribute takes precedence. Therefore, the following statements are equivalent: <source name="Tooling Region"> <name>TOOLING_REGION</name> </source> <source> <name>Tooling Region</name> <name>TOOLING_REGION</name> </source> | |
<expression> <cslRule> <![CDATA[ CSL code ]] | These tags are used to support CSL expressions in the mapping file. This capability was introduced in aPriori Professional 2018 R1. See also the id attribute for the <source> tag. Note that "cslRule" can also be specified as an attribute to the expression tag (for example, "<expression cslRule="csl code…" ). However, for clarity aPriori recommends that you use individual <cslRule> tags rather than attributes. For more information and examples, see the sections starting at Using CSL Logic in Your Mappings. |