Export Filter

Export Mapping with Type Filtering

When creating export mapping rules, you can use special element type keywords to exclude certain element types or stereotype combinations, as well as setting up generic mapping rules for a type/stereotype combination.

How Type Filtering Works

For each mapping rule you can define conditions that determine which type of elements are exported. Instead of mapping an element just by type/stereotype combination, you can now setup generic type mappings and specifically include stereotypes. This is useful, if you have a stereotype, which is applied to multiple EA element types. In addition, you can also ignore certain EA element types be explicitly ignored.

For example, you might configure a rule to export all EA elements with the stereotype LemonTree Connect::suspected. Since the stereotype can be applied to multiple element types, you would have to setup individual mapping rules for each base type. With the #Any keyword in combination with the stereotype mapping you can define a generic mapping rule, which exports all element types with the stereotype LemonTree Connect::suspected.

Do not use #Any without a stereotype mapping

Using #Any without a stereotype mapping will export the entire package tree with all elements, properties and parameters. The keyword #Any will match all elements found in an export package in EA. If you do not combine this type match with a stereotype, the export will write ALL elements within the package to Jama.
If you use #Any as type mapping, make sure to at least provide one stereotype mapping to reduce the scope for export.

Example Type Filtering

The base matching rules for exporting SysML Blocks and Signals from a EA to a set in Jama Connect are for example:

<matchingRule>
    <externalProperty name='_objectType' value='SYSARCH' />
    <myumlProperty name='_objectType' value='Class' />
    <myumlProperty name='_stereotype' value='SysML1.4::block' />
</matchingRule>

<matchingRule>
    <externalProperty name='_objectType' value='SYSARCH' />
    <myumlProperty name='_objectType' value='Signal' />
</matchingRule>

If you have a stereotype, which applies to a generic type (like MyNamedElement), you would have to add this stereotype rule to each matching rule. With the keyword #Any, you can combine them into a single rule:

<matchingRule>
    <externalProperty name='_objectType' value='SYSARCH' />
    <myumlProperty name='_objectType' value='#Any' />
    <myumlProperty name='_stereotype' value='LemonTree Connect::suspected' />
</matchingRule>

To ignore all elements with this stereotype independent from the element type you can use the keyword #None for the Jama Connect type:

<matchingRule>
    <externalProperty name='_objectType' value='#None' />
    <myumlProperty name='_objectType' value='#Any' />
    <myumlProperty name='_stereotype' value='LemonTree Connect::suspected' />
</matchingRule>

Export Filter Keywords

There are two keywords available:

Keyword	Meaning	Example Usage	Result
#Any	Using this type will match all EA types. This can be used for elements, diagrams and connectors. It should always be combined with a stereotype mapping.	`<myumlProperty name='_objectType' value='#Any' />` `<myumlProperty name='_stereotype' value='LemonTree Connect::suspected' />`	All items with the stereotype `LemonTree Connect::suspected` are exported, regardless of the element type.
#None	Used for explicitly ignoring element types for export. The keyword has to be used with the Jama Connect (externalProperty) type.	`<externalProperty name='_objectType' value='#None' />` `<myumlProperty name='_objectType' value='#Any' />` `<myumlProperty name='_stereotype' value='ignore' />`	A custom stereotype ignore is used to exclude certain elements from the export.

Examples

Export all elements that have a custom stereotype

In EA, the following elements are given:

name = Element001, type = Class, stereotype = Stakeholder
name = Element002, type = Interface, stereotype = Stakeholder
name = Element003, type = Class
name = Element004, type = Interface

The following mapping rule is used:

<matchingRule>
    <externalProperty name='_objectType' value='SYSARCH' />
    <myumlProperty name='_objectType' value='#Any' />
    <myumlProperty name='_stereotype' value='Stakeholder' />
</matchingRule>

Result:
Element001 and Element002 are exported to Jama Connect.

Ignore specific elements, regardless of their type

In EA, the following elements are given:

name = Element001, type = Class
name = Element002, type = Interface
name = Element003, type = Activity
name = Element004, type = Interaction, stereotype = ignore
name = Element005, type = StateMachine, stereotype = ignore

The following mapping rule is used:

<matchingRule>
    <externalProperty name='_objectType' value='#None' />
    <myumlProperty name='_objectType' value='#Any' />
    <myumlProperty name='_stereotype' value='ignore' />
</matchingRule>

Result:
Element001, Element002 and Element003 are exported to Jama Connect.