As an admin, it's not intuitive that fields which are configured within the cockpit details configuration page to be non-editable are completely hidden from within the “create CTA” action in rules engine.
It would be more intuitive to show all fields that have been added into the cockpit configuration page, but have those that are non-editable to be "greyed out". I understand this would only be developed going forward within Horizon rules.
For example, here is our configuration of the CTA Detail View Layout, where you can see a field named Parent Contract Number is configured, but marked to be non-editable:
However, when you are building a rule to create this type of CTA, you don’t have an option to map any value to this field since it’s been marked as non-editable:
Instead, it would be more intuitive to see the any field marked to be non-editable within the rule action, but greyed out, with a mention that this field has been configured within the cockpit detail view layout to be non-editable (bonus points if we can include a quick link to jump to that part of the system to allow a change if needed!)
The current system design presents two problems:
- Admins, who are often juggling between system issues/troubleshooting, configurations, user requests, and development work, can easily overlook this fact and forget why this value is not available to be mapped. “Is this CTA configured at a global, company, or relationship level and my rule is just looking at a different level? Is this a system bug? Am I forgetting something?” I’m not saying this has happened to me multiple times, but I’m also not not saying it
- Second, we cannot easily allow for situations where we might want to update a CTA value via a rule, but not allow for users to edit a field. This example I'm sharing is a case of that, where the field has dependencies on it and if the user changes the value it will break other system processes