Elements of an existing model can be imported into other models. Developers can work simultaneously on the same model; importing the different elements to create a new model. You can also reuse parts of a model; streamlining your work and letting multiple developers work efficiently.
Settings and properties are not inherited from the source model. You can reconfigure them in the destination model if you want to keep the existing settings and properties.
The destination model is the model that you will be importing to. It is a good idea to always backup your model before beginning the import process.
The Import Model Elements dialog box display.
The left pane displays a tree representation of the source model, including all entities, tables, and variables.
Model elements are those items that may be imported and comprise entities, attributes, operations, recordsets, recordset fields, tables, table columns, procedures and compound procedures, and model variables.
When an operation containing a WaitForMultipleEvents command is imported, the referenced Host Events are also imported.
Patterns and events cannot be imported separately from their entity.
By default, the destination model with all imported model elements is validated using the Host Integrator Validator.
If you are importing a model that contains an event handler, a reference to it is imported along with the parent element. However, you must manually copy the Java code from the model source Scripts sub-directory to the corresponding sub-directory in the destination model.
This icon... Indicates this... Table Compound Procedure Entity Attribute Variables Operation Field (in recordset) Recordset Column (in table) Indicates that the model element has not changed. The element will be overlayed with the existing one. The yellow asterisk indicates a new model element. This is an element that you might want to import. Procedure