Hello Developer Community!! I just spend a great deal of time tracking down an issue reported to my by several users. This seems to have started after we upgraded to 8.3p2, but I can’t say 100% 8.3p2 is the cause, but I have been able to reproduce the issue in lower environments.
The issue is in relationship to sending e-mail messages in workflows in IIQ using the sendEmail workflow step. I’ll try my best to describe the situation below.
-
Create a correlated identity using a system of record, i.e. HR system. This correlated identity will need to have an e-mail address (i.e. [email protected])
-
Aggregate an application which will cause an uncorrelated identity to be created, the uncorrelated identity should be created with a user name that matches the e-mail address of the correlated identity created in step #1 above. In this case the uncorrelated identity will have an identity name of [email protected]. No other attributes on the uncorrelated identity will be set.
-
Trigger a workflow that leverages the sendEmail workflow step, in the e-mail arguments sent to the template, either to “to” or “cc” argument will contain a single e-mail address, or even a list of email addresses, which will contain [email protected].
-
the e-mail will NOT be sent at all, not to [email protected], nor to any additional e-mails contained in the to/from arguments of the e-mail.
-
for further testing, edit the UNCORRELATED identity created in step #2 and add a distinctive e-mail address, such as [email protected]. RE-trigger the workflow to send the mail message from step #3, the e-mail will be sent, however IIQ will convert the mail address [email protected] to [email protected].
Bottom line, if you have any uncorrelated identities with an identity name, that matches the e-mail address provided in either the to/cc list of emailArguments sent to a sendEmail step in a workflow, the e-mail may either not be sent at all, or go to the incorrect recipient.