Configuring How Modules Are Imported From DesignSync

Create or open the text file for customized properties. For more information, see Editing Properties Using MQL.
To define how to connect a model to a product line during the import process, follow these steps:
1. Add or edit this line in the file used to import properties into a page object:
```
emxSemiTeamCollab.ProductLine.Option =
```
2. Set the value for this property depending on your business requirements:
  - (blank) = The import process does not connect new models to any product lines. This is the default.
  - parent = The import process checks to see if the parent product of the new model is connected to a product line, and if so, connects the new model to the same product line.
  - <Name of a product line> = The import process connects all new models to the specified product line if it exists. The import process will not create it if it does not already exist.
To define types that should be skipped (not used for matching DesignSync versions with Defect Management and Collaboration product revisions) when importing module versions from DesignSync, follow these steps:
Users import module versions using the Import Revisions from DesignSync action on the Properties page for the product (if the product is already connected to a DesignSync module).
1. Add or edit this line in the file used to import properties into a page object:
```
emxSemiTeamCollab.HDM.ProductRevisionMatch.ExcludeTypes=
```
2. Set the value for this property to a comma-separated list of symbolic types. For example:
```
emxSemiTeamCollab.HDM.ProductRevisionMatch.ExcludeTypes = type_TestProduct,type_MainVersion
```
  Any of the specified types, even if the name and revision match, will not be considered during the import module version process.
To enable or disable the ability to search for modules when importing module hierarchies based on a DSFA connection if the product revision does not have a DesignSync URL attribute, follow these steps:
1. Add or edit this line in the file used to import properties into a page object:
```
emxSemiTeamCollab.HDM.ProductRevision.MatchByDSFA
```
2. Set the value for this property depending on your business requirements:
  - yes = Enables the ability to search for modules when importing module hierarchies based on a DSFA connection if the product revision does not have a DesignSync URL attribute.
  - no = Disables the ability to search for modules when importing module hierarchies based on a DSFA connection if the product revision does not have a DesignSync URL attribute.
To define what the app should do if a matching product cannot be found while importing hierarchical modules, follow these steps:
1. Add or edit this line in the file used to import properties into a page object:
```
emxSemiTeamCollab.HDM.DefaultBehavior.NoMatchFound = create
```
2. Set the value for this property depending on your business requirements:
  - create = If a matching product revision cannot be found for the module being imported, create a product. This is the default.
  - ignore = If a matching product revision cannot be found, skip the module and any sub-modules and continue the import.
  - error = If a matching product revision cannot be found, halt the import and display an error. Any other modules being imported are also stopped. That is, if all modules being imported do not have a matching product, none of the modules will be imported.
If your system includes external modules that are shared among different DesignSync servers, disable the use of host and port values as part of the URL used to uniquely match products with modules.
If your system is configured with modules that are shared among multiple DesignSync servers, the import hierarchical module tool should not include the host and port values of the URL, which are used to ensure product uniqueness.
1. Add or edit this line in the file used to import properties into a page object:
```
emxSemiTeamCollab.HDM.ImportProductHierarchy.ConformExternalModules = true
```
2. Set the value for this property depending on your business requirements:
  - true = Host and port values for a module are used with the URL to determine uniqueness for a product. This is the default.
  - false = Host and port values are not used.
To specify custom pre- or post-processing programs for the import module versions or import hierarchical modules processes, follow these steps:
Users import modules using the Import Revisions from DesignSync action on the Properties page for the product (if the product is already connected to a DesignSync module).
Users import module hierarchies using the Import Module Hierarchy action on the Product Hierarchy page for the product.
1. Add or edit these lines in the file used to import properties into a page object:
```
emxSemiTeamCollab.HDM.ImportProductRevisions.PreProcess=<JPOName>:<MethodName>
emxSemiTeamCollab.HDM.ImportProductRevisions.PostProcess=<JPOName>:<MethodName>
emxSemiTeamCollab.HDM.ImportProductHierarchy.PreProcess=<JPOName>:<MethodName>
emxSemiTeamCollab.HDM.ImportProductHierarchy.PostProcess=<JPOName>:<MethodName>
```
  Note: You must also create the JPOs and methods.
2. Set the value for this property to the name of the JPO and method.
When you are finished updating the text file with all properties that you want to modify, use the text file to modify the emxSemiTeamCollab.properties page object. For more information, see Editing Properties Using MQL.