Apply Relationship Class Rules to Collector

Idea created by Ahjung.Kim_stantec on Oct 28, 2015
    I suggest enforcing relationship class rules to feature service and applying that to Collector. 

    "[...] HazMat landfill can be related to one or two deep wells or between two and seven shallow wells. However, if a sanitary landfill is related to a deep well, but no rule has been created between these two subtypes, the Validate Features command will consider the relationship to be invalid("

    In above scenario, it'd be ideal if user selects HazMat in the origin table, only deep wells and shallow wells show as available choices in the destination table drop-down. Also, if the number exceeds the maximum limit, show a warning message to user. I suppose this can be a challenge for offline data collection.