Using Master Models

One way to work with the Host Emulator and Design Tool is to create a master model that contains all the screens that your applications will access, including error messages and multiple entities for different sets of data. You can then load this model into the Host Emulator, connect to it using the Design Tool, and create the actual models you will deploy in your applications from the master model.

When you replay any model in the Host Emulator, the Host Emulator can only display the entities the model contains. For example, if you have only one AcctProfile entity, you'll only be able to see the one set of data that entity contains. Because a master model contains multiple entities for different sets of data, it allows you to display multiple AcctProfile screens, each with different data.

Using a master model has these benefits:

After you create your master model, add it to your Host Emulator configuration so that the Design Tool can connect to it and allow you to create models from it.

 

Creating Master Models

Master models represent the host application and should simulate that application as closely as possible. Follow these guidelines when creating a master model:


 

 

  Attachmate