RevisionID Mapping
- Last UpdatedMay 12, 2025
- 1 minute read
RevisionID Mapping can be used to derive the revision of a document. Each mapping entry in the configuration is examined in sequence and the first mapping entry to match is used to generate the object’s context ID.
The simplest form of RevisionID mapping entry to derive Revision or an object is shown below:
<Object>
...
<Conditions>
<Attribute name="object_class" pattern="Door" />
</Conditions>
<Revision value="[object_name]" />
...
</Object>
Note: Conditions may hold multiple attribute elements. All conditions must be met for the mapping to be applied.
Use Lookups and transforms to modify the Revision value.
<Object>
...
<Conditions>
<Attribute name="object_class" pattern="Door" />
</Conditions>
<Revision value="[object_name]">
<Transforms>
<Replace pattern="^[a-z]{3}" value="OBJ" />
</Transforms>
</Revision>
...
</Object>
<Object>
...
<Conditions>
<Attribute name="object_class" pattern="Door" />
</Conditions>
<Revision value="[object_name]">
<Lookup id="ExcelLookup" >
<FailAction action = "DiscardElement" />
</Lookup>
</Revision>
...
</Object>
Attributes from associated objects can also be used, as shown below:
<Object>
...
<IncludeAssociatedObjectAttributes type ="^FillsVoids$" refID="[Tag]" >
<Conditions>
<Attribute name = "ClassName" pattern = "^OPENINGELEMENT" />
<Attribute name = "Name" pattern = "^element1$" />
</Conditions>
</IncludeAssociatedObjectAttributes>
<ObjectName value="[Tag]_[associated:Tag]" />
...
</Object>
In this case above, the value of the Tag attribute along with the value of Tag of the first associated object matching the condition is used in deriving RevisionID. The prefix "associated:" is used when referring to the associated object's attribute.
If an object does not match any of the mapping entries, it is not assigned any RevisionID.