The emxRequirements.properties file contains definitions the parent/child relationships to check for each Type (Requirement, Chapter, Comment, Decision, Requirement Specification) before deleting. This section shows the default settings for each Type, which can be modified.
emxRequirements.type_SoftwareRequirementSpecification.CheckParentRels=
emxRequirements.type_SoftwareRequirementSpecification.CheckChildRels=relationship_SpecificationStructure
emxRequirements.type_Requirement.CheckParentRels=relationship_SpecificationStructure
emxRequirements.type_Requirement.CheckChildRels=relationship_RequirementBreakdown,relationship_DerivedRequirement
emxRequirements.type_Chapter.CheckParentRels=relationship_SpecificationStructure
emxRequirements.type_Chapter.CheckChildRels=relationship_SpecificationStructure
emxRequirements.type_Comment.CheckParentRels=relationship_SpecificationStructure
emxRequirements.type_Comment.CheckChildRels=
emxRequirements.type_Decision.CheckParentRels=relationship_RequirementDecision
emxRequirements.type_Decision.CheckChildRels=
As an example, let's use these two settings:
emxRequirements.type_Requirement.CheckParentRels
AND
emxRequirements.type_Requirement.CheckChildRels
The following is a setting that checks parent relationships:
emxRequirements.type_Requirement.CheckParentRels=relationship_SpecificationStructure
The above setting indicates that a Requirement can only be deleted when it has no parents pointing to it in a relationship_SpecificationStructure relationship (excluding its current parent displayed from the current UI).
For example, for a requirement that has a parent Chapter, this requirement cannot be deleted from the Requirements list view. However, it can be deleted from the Specification Structure Browser view because in the Specification Structure Browser view its parent in relationship_SpecificationStructure is explicitly displayed, thus this parent is ignored in the parent check. While in the Requirement list view, this parent check needs to be conducted and would fail. However, if this requirement has more than one parent Chapter, the parent check would still fail even in the Specification Structure Browser view unless its other parent Chapters are also selected for deletion (using the action "Delete > Selected Objects") or its other parents fall into the same branch selected for deletion (using the action "Delete > Selected Object and Children")
Here is another example:
emxRequirements.type_Requirement.CheckChildRels=