Hi all -
We're Using Reactivate User to procedurally reactivate accounts for re-hired contractors - but we also need to reset their passwords, as they're all accounts that previously utilized SSO. In the past, the old accounts would have been left by the wayside and we would have just created them new ones (thus adding to the clutter-pile of disused accounts), but now we're able to change their username, which is a strong positive in general.
The problem: Our customer / stakeholders are STRONGLY against forcing users to undergo the multiple clicks necessary to do a manual "forgot password" request on the sign-in page, and to be fair, nothing was "forgotten" in this case. The days of having the "change password" smart service via plug-in are sadly long-gone, but we don't even have a way to procedurally kick off an automated password reset for a particular user. Why?
Edit: this issue is now satisfied thanks to the newer plug-in, Credential Management.
Discussion posts and replies are publicly visible
Hi Mike Schmitt ,
Good day!
I have a similar requirement in my project were I have to send users "reset password"(as I user creation) emails once reactivated. I would like to know incase if you had found any work around with your usecase?
Thanks
Yes, a few months ago I realized there's now a newer plug-in called "Credential Management" which contains a smart service called "set user password". This allows us to reactivate a user account and then generate a randomized password in-process, set it as the account's new temporary password, then send it to them via email.
Do you have to create the process for sending the new password or does Appian do that (like you reset a password from the Ops Console)?
I had a quick look at the source code. And, it does not send an email.
no, nor would we want it to, as it is not intended, advertised, or aimed to do any such thing. we 100% build the process ourselves which is what we want, since it allows us to actually control the timing, targetting, and format of the email, and we can verify to some extent that it actually went through and to the correct email address.
Chris.Gillespie said:or does Appian do that
I agree. I didn't want the user to receive two emails, one from Appian and another from the process. Reduce user confusion.