Steps to Reproduce:
Actual Results:
Value mapping is not correctly saved. If it is not being saved in backend, proper validation message should be visible in UI
Expected Results:
If value mapping is being saved in backend, on modifying, it should show the same saved advance value mapping.
The fix here is to stop the user from being able to save the automation pointing to * Null in the first place since that's not supposed to be a supported mapping
DE155843
DE155843 resolved in 3.7.0 and ported back in 3.6.0.1 patch