Use case:
We are working on a rule where one of the picklists grew a lot, and we have ~200 new values to add. The first issue is that you can’t export the existing 150 to validate which ones already exist in the dropdown. If the value exists in the dropdown but not in the object, we can’t identify them via rules engine.
Related idea:
Some manual effort combined with some workarounds, and we were able to update the dropdown list… So we got to issue #2: It did not update the mapping in the rule, we had to manually map all the missing values to maintain all the actions in one branch (I didn’t get a screenshot from the Horizon rule, so I’m using an old bionic one with the same field as an example, but the behaviour was the same in both)
The funny thing is that it will default correctly if creating a new branch in that same Horizon rule… So, can you please replicate this behaviour?
