In Data Designer, and the Rules Engine when building Horizon Rules, I wish the Display Name displayed the entire Lookup path of the selected field rather than only the Field Name itself.
By keeping the entire Lookup path of any selected field, the Admin is able to work more quickly and with less ambiguity than having the Display Name take on only the Field Name.
These two screenshots compare Bionic Rules with the Horizon Rules / Data Designer experience.
- In the Bionic experience, it’s easy to differentiate the GSID and Name fields, especially because the Output Field Label carries the entire path into any subsequent Tasks within the rule.
- In the Horizon experience, the GSID and Name are harder to differentiate, requiring a manual edit of the Display Name field.
- Side note: Given the UI, you cannot even use the details on-screen to differentiate. One must hover over the Aggregation column and view the tooltip to disambiguate the fields.
I have a very long-time best practice to always rename a GSID or a Name field (to Company GSID or Company CSM Name, as examples) whenever its path is ambiguous. This reduces the opportunity for confusion or ambiguity when rule building. That step of manually editing a field Display Name is much less necessary in the Bionic UI than in the Horizon / DD UI.
Given you cannot save a Horizon Rule / DD fetch when there are duplicate Display Names, the Admin has to stop and make an edit that wasn’t required in the Bionic Rules environment.
