Indeed. More generally, I think OXE should "disappear" behind Rainbow. For the user experience (and hence user adoption), a seamless integration between both worlds is crucial.
Hi Andreas, An update on this one: it seems this issue has been fixed. Very recently, though: I still encountered it in December. So version 1.67 must have brought the fix.
There is another use case for this dual usage. Some workers in our company need two different phone numbers: one is their personal number, while the second is functional (abstract) number used for ...
Definitely agree! This will also happen for instance when a user switches connexion type.