Profiles Email Address

I'm guessing you could create a process model which first loads the usernames of all users in a specified group (and by that i mean you'd feed in a group containing all users you want to update), then iterates through them one by one and uses the update user info smart service node to set the email address to whatever you like - it could either be the same thing for all, or something dynamic based on their username or user details, pretty easily. It would even work for 45,000 users though you'd have to batch up your MNI calls so that none of them exceed 1,000 (divide into subprocesses, etc).

What is your use case? Are you getting unnecessary emails? Why not disable the email server instead?

We would like to avoid emails being sent to bussines email addresses although disabling email server doesn't seem to be an appropiate option in this case since we (as support team) would need to get some error notification emails for troubleshooting

@erwini you can enable or disable the ability for Appian to send email from admin console, error notification also gets listed under alerts (designer) based on process model alert setting.

I too faced similar issue in one of the project , where we added rules at SMTP relay server to allow emails only to customer domain for e.g. - *@appian.com. All other emails were blocked. Cons of this was that email nodes were blocked but we ised limited set of users for Testing.

you can also try for Update User profile smart service.

Out of interest, how did you end up with "real" users in a test or dev environment? I would have thought LDAP sync or equivalent wouldn't be enabled for that environment for exactly the reasons you describe. Normally we'd have manually-created users (or rather, some users created using import users from csv) so that we're in control of the email addresses.

One other option is to add a prefix to each email subject - eg TEST - <subject> - so that, if you have to have emails going to real users, they are able to tell the difference between test and live emails. This should be relatively simple as long as your email sending is done by a generic, reusable process, and can be done using an expression rule that uses the environment URL so that it's handled dynamically regardless of environment.

@harshav - The update user smart service looks for other fields apart from email address as mandatory fields and we don't want to enter the information for all the 45K+ profiles. Is there a way, we can feed the dummy email address alone rather than the other 2 fields?

@philb - It looks like a web service was invoked from a source system that had the legitimate email address and thereby the user profiles were updated