On a property dependency, you can define a condition that requires a local or remote property to have a certain value or be within a certain range for the package to be deployed.

While adding a property dependency, any combination of Property Name, Operator, and Property Value can be added, but you must make sure that the relationship is valid for deployment.

The following table shows which operator and property value types are compatible:

The package type (file-based or instruction-based) and property type (local or remote) used for the condition determine how the condition is evaluated at the start of a deployment. In most cases, the evaluation is performed locally, on the Software Content Management side, taking the property value from the asset's Thing. However, for instruction-based packages, the condition can be evaluated on the Axeda agent.

The following table describes how and where the conditions are evaluated depending on the package type and property type and whether the property exists on the Thing:

At the start of a deployment of a package to a delivery target, conditions are checked against the asset's actual property value. The asset’s property value and the Operator and Property Value specified for the property condition are checked.

For example, an asset has a temperature property with a value of 24 (so the asset's Property Value = 24). A dependency was created with the following values:

During the deployment, this condition is checked: 24 > 25.

As a result, the deployment fails, the delivery target state is Ineligible, and a status message explains the reason for failure.