If you are using event format to import, you can enable automatic mapping, i.e., all attributes of a system event are transferred to the specified object types in the assigned fragment definition.
Extension of the mapping configuration is configured using attributes of the automapping XML element.
XML attribute |
Description |
nodetype |
determines the object type for which this automapping is valid. |
graphid |
determines the fragment definition graph for whose objects this automapping is valid. The specified value corresponds to the id attribute of the graph XML element in the fragment definition. |
addmergeattributes |
For the object type PROCESS, determines whether the attributes are added to the merge configuration, which means that they will be retained as process attributes when merging instance fragments (value TRUE), or not (value FALSE). For the object types OT_FUNC and OT_EVT, this entry is ignored. For the object type PROCESS, you must specify addmergeattributes. |
If you have to specify automatic mapping extension for multiple object types or fragment definition graphs, you can specify a separate automapping XML element for each object type or fragment definition graph required. Automatic mapping takes account of the prefix specified in the attributeprefix XML element, e.g., AT_. If you have specified an explicit mapping for particular attributes, this overwrites the attributes previously transferred by automatic mapping.
Example
In the file extract below, automatic mapping extension is configured for functions of the fragment definition graph FRG_CATCH_ALL.
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE eventmapping SYSTEM "eventmapping.dtd">
<eventmapping>
<processfragmentmapping>
<!--FRG_CATCH_ALL-->
<processfragment graphid="FRG_CATCH_ALL">
...
</processfragment>
...
</processfragmentmapping>
<attributemapping>
...
<automapping
nodetype="OT_FUNC"
graphid="FRG_CATCH_ALL"
/>
<attributemapping>
</eventmapping>