Configuring the Where Used Functionality

You can configure the Where Used functionality to display objects from contract requirements.

See Also
Configuring Properties
  1. Create or open the text file to contain customized properties. For more information, see Editing Properties Using MQL.
  2. To define the types displayed from the Where Used category for contract requirements, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      AnDPMA.WhereUsed.ContractRequirement.ExpandTypes = type_Model,type_Issue,type_SoftwareRequirementSpecification,type_Products,type_ProjectSpace,type_RequirementBaseline,type_RequirementGroup,type_Builds,type_HardwareBuild,type_SoftwareBuild,type_Features,type_Requirement,type_ProductLine,type_ContractSection

    2. Set the value for this property depending on your business requirements.
  3. To define the relationships displayed from the Where Used category for contract requirements, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      AnDPMA.WhereUsed.ContractRequirement.ExpandRelationships = relationship_CandidateItem,relationship_CommittedItem,relationship_Issue,relationship_OriginatingUserRequirement,relationship_ProductRequirement,relationship_ProjectRequirement,relationship_RequirementSatisfiedBy,relationship_ResolvedTo,relationship_RequirementBreakdown,relationship_ProductLineModels,relationship_Products,relationship_SpecificationStructure,relationship_ContractRequirement

    2. Set the value for this property depending on your business requirements.
  4. To define the types displayed from the Where Used category for requirements, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      AnDCDRLRequirements.WhereUsed.Requirement.ExpandTypes = type_Model,type_Issue,type_SoftwareRequirementSpecification,type_Products,type_ProjectSpace,type_RequirementBaseline,type_RequirementGroup,type_Builds,type_HardwareBuild,type_SoftwareBuild,type_ConfigurationFeature,type_LogicalFeature,type_ManufacturingFeature,type_Requirement,type_ProductLine,type_SIMULATIONS

    2. Set the value for this property depending on your business requirements.
  5. To define the relationships displayed from the Where Used category for requirements, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      AnDCDRLRequirements.WhereUsed.Requirement.ExpandRelationships = relationship_CandidateItem,relationship_CommittedItem,relationship_Issue,relationship_OriginatingUserRequirement,relationship_ProductRequirement,relationship_ProjectRequirement,relationship_RequirementSatisfiedBy,relationship_ResolvedTo,relationship_RequirementBreakdown,relationship_ProductLineModels,relationship_Products,relationship_SpecificationStructure,relationship_SimulationContent_Referenced,relationship_SimulationCategory

    2. Set the value for this property depending on your business requirements.
  6. To define the types displayed from the Where Used category for regulations, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      AnDPMA.WhereUsed.Regulation.ExpandTypes = type_Model,type_Issue,type_SoftwareRequirementSpecification,type_Products,type_ProjectSpace,type_RequirementBaseline,type_RequirementGroup,type_Builds,type_HardwareBuild,type_SoftwareBuild,type_Features,type_Requirement,type_ProductLine,type_ContractSection

    2. Set the value for this property depending on your business requirements.
  7. To define the relationships displayed from the Where Used category for regulations, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      AnDPMA.WhereUsed.Regulation.ExpandRelationships = relationship_CandidateItem,relationship_CommittedItem,relationship_Issue,relationship_OriginatingUserRequirement,relationship_ProductRequirement,relationship_ProjectRequirement,relationship_RequirementSatisfiedBy,relationship_ResolvedTo,relationship_RequirementBreakdown,relationship_ProductLineModels,relationship_Products,relationship_SpecificationStructure,relationship_ContractRequirement,relationship_ProductFeatureRegulation

    2. Set the value for this property depending on your business requirements.
  8. When finished updating the text file with all properties you want to modify, including the ones shown here, use the text file to modify the emxAnDPMAccelerator.properties page object. For more information, see Editing Properties Using MQL.