The Coupling Type Contribution node (), which can be added as a subnode to any of the multiphysics coupling nodes, defines a physics interface context in which you can add variable declarations, variable definitions, equations, and so forth. The contributions behave as if they were added by a physics feature under the physics interface. All contributions that do not belong to any context use the multiphysics coupling as context. The context decides the default scope of variables and function names, for example. The Settings window contains the following section:

Choose the coupling type that the contributions should be restricted to using the Restrict to coupling type list.

You can let inputs in physics properties enable and disable user interface controls in a multiphysics coupling feature. To do so, the coupling feature needs to know that the physics property actually exists. You can define such properties by adding them in the Property Dependencies table. You need to support the name of the property and the input as well as the dimension of the input. If the Allow not defined check box is cleared, you will then get an error as soon as you try to build a model with this coupling feature and a physics that try to use this coupling but does not have the required property or a required parameter in the property. The value in the Value when not defined column is needed when the property or input is undefined. In that case, the coupling feature will act as if the input in the property will have this value.

When building a model, the properties required by the coupling feature will show in the Coupled Interfaces section in the coupling feature’s Settings window. The properties will be disabled, and you need to go to the physics node to change the value. There is a possibility to hide them by clicking the Show or Hide Physics Property Settings button.

To let a required input in a physics property activate an input in a coupling feature, use an Activation Condition where you specify the user input by name and set From to User input from this feature. Set the name of the user input in the activation condition to couplingType.propertyName.inputName (for example. heat.PhysicalModelProperty.HeatTransferInPorousMedia).