We have begun upgrading our large enterprise environment from Unity 9.1 to 10.5. We have a number of applications developed in-house utilizing the vmrest API. One of them allows end users to update the SmtpAddress of their SMTP Notification Device. End users can enter multiple addresses in our application, which takes care of validation itself on the back end and then concatenates the addresses joined by a comma. In effect this enables email notification of voice messages to multiple parties and worked wonderfully under 8.5 and 9.1.
Now, however, we noticed our 10.5 boxes broke this functionality. We get the following error when submitting comma-separated multiple addresses:
<message>Enter Vaild Relay Email Address</message> [sic]
Obviously the commas are breaking the validation that PREVIOUSLY DID NOT OCCUR. Multiple-party notification still works fine when input manually via CUC Admin but this breaks our end user-facing tool. Is there any way I can turn off validation at the API level?
welcome to the club. I think they introduced the breakage in 10.0, but it should be fixed in 10.5.2.. so if you can, try upgrading.
We went with 9.1 for one customer (10 was already out), and 10.5.2 for another to bypass this issue.
Unfortunately, it's not the only db layer validation they keep changing and that keeps messing with the rest api. Another is changing name/alias when ldap integration is active. in the gui, you can temporarily disable ad integration, change, and re-enable. In the api. there's an additional check that prevents this, introduced in 10.5.2 to fix 10.5.1's not blocking any change even with active ldap integraration.
Just goes to make the case that if there's an api, the maker should be its first user..
Bug CSCuv46838 has been created for this:
A fix will be included in an upcoming ES release.