We are currently troubleshooting an issue related to the New Account Provisioned Email Template, which is already configured to notify an identity’s manager.
We have the following accountCreateNotification configuration defined on one of our sources, where the account manager is notified when a new account is provisioned:
We are trying to determine whether this functionality is still supported, as it does not appear to be working for us.
Additionally, while reviewing the following community article, I noticed that the accountCreateNotification payload uses a slightly different set of parameters:
Could someone please clarify the difference between the parameters shown in the community article and those currently returned by the API? Has the configuration changed over time, or are both formats/params still supported? also on steps how to troubleshoot on when above stopped working?
Hello Lalitha, the parameter difference is because that Compass article uses the old /cc/api/emailTemplate/setAccountCreateNotificationOptions API, which accepts params like emailAccountManager, emailAccountOwner, accountNotificationList. That API is deprecated.
The current supported method is the Update Source (Partial) API, where the config lives under connectorAttributes.accountCreateNotification using notifyAccountManager, notifyAccountOwner, notifyList, etc. Your current field names are correct, so I wouldn’t swap them to emailAccountManager or the other old parameter names.
Since the source configuration looks fine, pick one recent new hire and confirm the account was created through an ISC provisioning action, not discovered through aggregation. Then verify the manager is correctly resolved in ISC and has a valid email address.
I would verify the identity’s manager is properly resolved in ISC and has a valid email. Also check Admin > Global > Email Templates > Settings and confirm it is set to Intended Recipients. If it is set to Test Address, all notifications are redirected there. Check that the New Account Provisioned template subject does not start with no_send or Stop. After that, search the audit events around that provisioning time for Send Email Passed or Send Email Failed to see if ISC even attempted the send.