Creates or modifies an input communicator.
| For the option: | Do the following: |
|
Input Communicator Name |
If creating a communicator, enter a name for it. If modifying a communicator, enter its database name. |
|
Type |
Select one of the following:
If modifying a communicator, note that this text box is disabled, because you cannot change the type after the communicator is defined. |
| Matching Name(s) | Enter one or more identifiers for this input. One of these
identifiers must be identical to a matching name identifier for the corresponding
output communicator. If left blank, the matching name defaults to the
input communicator name.
When modifying a communicator, when you select an input communicator variable for the input communicator name, your template-based product automatically updates the Matching Name(s) text box with the corresponding value(s). |
| Entity |
Select an entity class for the input communicator. If modifying a communicator, note that this text box is disabled, because you cannot change the entity class to which the communicator refers after the communicator is defined. |
| From Minor Role | Specify the communicator minor role for this input, which should match the minor role of a corresponding output. The minor role any, matches to any output, regardless of its minor role. If minor role = inherit, your template-based product determines the minor role from the role of the subsystem owning the input. |
| If you set Minor Role to parameter integer or parameter real, your template-based product enables the following option: | |
| Initial Value |
Enter the initial value for the parameter input communicator. |
![]() |
Select to display a dialog box where you can add multi-line comments to any entity, to describe its purpose and function. Your template-based product displays different comments dialog boxes, depending on the entity type for which you want to record comments:
|
| List Outputs | Select to display a list of output communicators. This option is useful when you work on many templates simultaneously, because it allows you inspect the communicators on other open templates or subsystems. |