Click HERE to see how Saviynt Intelligence is transforming the industry. |
05/24/2023 04:53 AM - edited 05/24/2023 04:54 AM
Use case is to send two emails on account creation: account creation email and temporary password.
Both email templates are built similarly, with "to" recipient identified with user.email. Account creation notification makes it fine but temporary password notification has a blank "to" field.
Templates definition:
Account creation email received
Temporary password email received:
Logs are fairly generous on this topic, we do see the to recipient was not populated but no idea as to why:
"ecm-worker","2023-05-24T11:39:49.007+00:00","2023-05-24T11:39:48.79955269Z stdout F 2023-05-24 11:39:48,799 [quartzScheduler_Worker-3] DEBUG services.ArsTaskService - Sending Email to - [], cc - [REDACTED], bcc - []"
I have no idea as to what I could possibly have messed up... Any insight would be much appreciated!
Thanks!
Francois
05/24/2023 05:41 AM
Does email is triggered ?
try ${user?.email}
05/24/2023 06:14 AM
${user.email} actually resolves fine. Email mechanisms insist on notifying recipients individually. Nothing to see here, have a nice day 😉
05/24/2023 06:37 AM
outlook issue?
05/24/2023 06:43 AM
I don't think so, the logs indicate Saviynt made a conscious decision to send to the "to" and "cc" recipients separately. In any event, our use case does not plan on cc'ing the password anywhere, this was used for testing demonstration. As long as the end user receives the password, I am ok.
05/31/2023 06:29 PM - edited 05/31/2023 06:29 PM
After a little investigation, it turns out Saviynt simply does not sent the password to everyone at once...
Beneficiary was getting the password all along
05/31/2023 07:02 PM
As long as user received password it should not be issue