Mappings are typically simple to specify; however, we do identify some special cases.
DOORS has internal attributes that are not natively available to map. However, we do expose these with special identifiers to map to DOORS Next attributes. For example if we want to map the DOORS URL to a DOORS Next Attribute named Source of type String would be mapped in the attributes as follows.
The available internal attributes are as follows.
__internalDNGMigrationId -> unique requirement object id using module id and absolute id (should always be a part of a migration) __uniqueId -> DOORS Object Absolute number or Module unique id __doorsClassicId -> Object Classic id PrefixAbsoluteNumber __url -> DOORS URL __createdBy -> String user id __createdOn -> String creation date __lastModifiedBy -> String modification user id __lastModifiedOn -> String modification date __prefix -> Module prefix __description -> Module description __shortText -> Object short text __objectNumber -> Object number (e.g 1.2-3) __objectLevel -> Object hierarchy level __createdThru -> Object creation method
A comma separated list can be used to enable multiple mappings for DOORS to a single DOORS Next mappings. This is useful with the type changes from Module to Module observed in DOORS.
Note the ini settings to map the comma to another character.
For accuracy of the DOORS9 element name we trim preceding and trailing white space to improve mapping accuracy. However, if there is an intention of a trailing or preceding whitespace you can use a "" label.
In this case all three labels would map the "Certain" label.
Many to One and Strict Formatting rules apply to all mappings.