Relationship class rules that are set to restrict related table records to only features of a certain subtype do not restrict features with invalid relationships from being created through editing the attribute table.

Workaround

One could make the argument that the feature layer should be separated into two layers, one for Valves and one for Hydrants. However, the user this bug was logged for had other considerations preventing this from being feasible, as this WaterDevices layer was a part of a utility network.

Steps to Reproduce