E-mail Based on Repositories

[Former Member]

Hi all,

We are using IDM 7.2 SP7, and the standard notification framework.

We are currently creating e-mails for creation of a user id for all repositories that we are linked to, but we only want to create e-mails for one repository out of all of them.

Is there a repository constant or notification constant available that we can use to stop the sending of the emails, or do we need to do what we have currently done, which is to set up a switch task and look at the incoming repository name and make the decision about whether to send the e-mail or not based on that?

Thanks in advance

Simon

[Former Member · Accepted solution]

Hi Simon,

There will be a repository constant called ENABLED_FOR .

set the value to NULL for the repositories to which email notification are not required.

For the repository you want to have notifications, for the ENABLED_FOR maintain the required values like

PASSWORD_CHANGED;CREATE_USER;MODIFY_USER;DELETE_USER;ASSIGN_USER;REVOKE_USER;ENABLE_USER;DISABLE_USER;ROLE_ASSIGNED;ROLE_REVOKED;FAILURE

All the best !!

~ Krishna.

[Former Member · Accepted solution]

Hi Krishna

Thanks for the suggestion.  We have assigned the repository constant called ENABLED_FOR in the repository that we do not want emails to be sent from, and in the VALUE field we have

1. Left the value field empty
2. typed the word NULL in it

On both occasions the emails were sent.

Any other ideas?

regards

Simon

[Former Member · Accepted solution]

Hi Simon,

From what I know of the notification framework, what you have done with the switch task is the best way to go. The only question is whether other repositories will be added for notifications. If in the future that is going to happen, I would suggest that you add a constant in the repository. Like a boolean value. When the notification is triggered in the Trigger Notification task, write a script to check whether the constant is defined for that repository. If it is, then send the notification. If not, then skip the entry.

Let me know if you have any questions!

Anu

[Former Member · Accepted solution]

Hi Simon,

You are doing it correctly. But not sure why the emails are still getting triggered !!. Can you stop the dispatcher and re-start them. I also recommend to regenerate the dispatcher scripts before restarting them to see if it can fix the issue.

But to make it more clear for you, below is the explanation on how it works.

In the provisioning framework, either it is provisioning/de-provisioning/modify, after successful completion of the task, there is a notification task triggered. Please refer to the below task for provisioning.

So, that notification pass will check against the repository constant ENABLED_FOR of the repository and verifies that is the notification enabled for the trigger ? using the script sap_core_check Notification.

If the notification is enabled for the corresponding task, then the script sap_triggernotification will set the attribute MX_TRIGGER_NOTIFICATION with the trigger . In this case ' Create User " followed by which the notification will be triggered.

~ Krishna.

[Former Member · Accepted solution]

Hi Krishna

Perfect, thanks alot.

The only thing we needed to do was in the Tasks in the Notification framework, as a standard the Repository is set to NOTIFICATION, we needed to set it to -- None/Inherited --, otherwise it picks up the ENABLED_FOR values from the Notification repository,

regards

Simon

[Former Member · Accepted solution]

Great that you identified what is causing the issue and able to fix it.

Thanks for sharing the solution on the space.

~ Krishna.