Handling of Deleted Elements during Export to Polarion
Deletion of EA Elements
During export to Polarion, LemonTree.Connect is capable of detecting elements which were deleted in EA. However, this is not done by default and an additional configuration in the export project has to be done.
If a package is exported to Polarion and elements were deleted in EA, LemonTree.Connect does not automatically delete these elements in Polarion.
Currently, two things will happen with deleted elements:
- Deleted elements will be relocated to a work item called Obsolete Items. This element has to exist in the export project.
- Deleted elements will have a prefix [OBSOLETE] added to their name.
Relocation to "Obsolete Items"
If you want elements to be detected as deleted, a work item called Obsolete Items has to be created in the export tracker. For this work item, the field
my_uml_type has to be set to a value, which is used in the export mapping. For example, if you are exporting classes, the
my_uml_type of the Obsolete Items item can be set to Class.
Mandatory 'Obsolete Items' item
Without the work item called Obsolete Items and a proper my_uml_type set, the deletion detection does not work!
Type of 'Obsolete Items' item
You can use any custom work item type for the Obsolete Items work item. However, this must align with the Mapping Configuration that you use during the export.
For example, if you only use one single mapping to export an EA Component to a custom type Component, the Obsolete Items item must also have the custom type EA Component.
This also has to be considered in the custom field
my_uml_type. For the example given above the
my_uml_type has to be set to Component.
Deletion of EA Connectors
If EA connectors are mapped to work item link roles, deletion of EA connectors is also considered during export. Compared to deleted elements, work item link roles are automatically deleted in Polarion and are not flagged as deleted.