Understanding our org's use case is atypical, we use "Department" to capture a broad "Division" of our sites. For example, we have 10 sites that do "Construction" work, 4 Sites that are "Corporate" staff, etc. Being able to classify these sites into larger buckets helps with backend reporting. To that end, limiting the Department dropdown based on site would prevent misclassifications. We currently employ automation rules to correct these errors, but a direct dependency would be nice. Outside of our use case, this could be useful in an org that has many departments, but only a few are applicable per site. For example, If only two sites employ building access control, limiting the "Security Team" department to only appear for those sites would be beneficial. It would also aid in easier ticket routing for those departments via process or automation rules. No longer would you need to have a "condition set" for every site/department combination, only those that are allowed via the field dependency.
