Profiles Email Address

RE: Profiles Email Address

sagarl511 — Tue, 28 Feb 2017 20:12:57 GMT

@balakrishnanm - Update user smart service has firstname and last name as other fields. You can then use user() function to populate same values for first name and last name of each user.

RE: Profiles Email Address

darrynj — Tue, 28 Feb 2017 19:19:20 GMT

In our project the user profiles were also stored in the database. so for the lower environments we could just run a simple update query to change all the emails. Also we had a primary business email box that was stored in a constant. so this constant would get appended to all of the addresses that were going to get sent out in our Process Model. In the lower environments we just set that constant to someone on our team's email. In production it was the actual value. Not sure if this is helpful to you.

RE: Profiles Email Address

Mike Schmitt — Tue, 28 Feb 2017 14:00:44 GMT

@balakrishnanm - in my first comment I stepped through a scenario where the update user smart service could be used in an automated fashion to set dummy e-mails for all users in a specified subset. Do you need any further details as to how this would be done?

RE: Profiles Email Address

balakrishnanm1 — Tue, 28 Feb 2017 09:52:38 GMT

@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

RE: Profiles Email Address

balakrishnanm1 — Tue, 28 Feb 2017 09:40:59 GMT

@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?

RE: Profiles Email Address

PhilB — Tue, 28 Feb 2017 08:50:03 GMT

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.

RE: Profiles Email Address

PhilB — Tue, 28 Feb 2017 08:22:51 GMT

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.

RE: Profiles Email Address

harshav — Tue, 28 Feb 2017 08:03:25 GMT

you can also try for Update User profile smart service.

RE: Profiles Email Address

sagarl511 — Mon, 27 Feb 2017 22:42:12 GMT

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.

RE: Profiles Email Address

vineeta6579 — Mon, 27 Feb 2017 21:18:45 GMT

@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.

RE: Profiles Email Address

erwini1 — Mon, 27 Feb 2017 19:09:40 GMT

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

RE: Profiles Email Address

Paul Mayeur — Mon, 27 Feb 2017 18:56:24 GMT

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

RE: Profiles Email Address

Mike Schmitt — Mon, 27 Feb 2017 18:04:07 GMT

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).