The Best options for notifyng during JML processes

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hi,

Does someone know what is the best for send notifications JML basic process (joiner, leaver) ?

I think about the following two solutions :

  • Use “Lifecyclestate change” natif notifications and add multiple content with condition based lifecycle state.

  • Use workflows with identity attributes trigger and define diffente notifications based on lifecycle state.

2

In my point of view, I will say using the “LifecycleState change” notifications works fine. While having an OOTB email, why we should go to workflows? For this, you can make use of the below link.

Also, if you are going to notify “LifecycleState Change” and going to make a certification or something for the identity which underwent LCS change, you can go through the workflows.

Thanks!

1 Like
3

Thanks @GOKUL_ANANTH_M !

@MVKR7T any other idea ?

4

If you are looking for notifying not just the identity but its manager or certain set of identities or DL for certain reconciliation purpose.
Then I will suggest a Workflow where you can decide based on the LCS state what type of notification you need, who you want to be notified can also be customised based on Identity & its LCS and even take Dept or Region into consideration for more customization.
No doubt the WF will get longer but gives you a vast variety of custom emailing.

1 Like
5

Hi @baoussounda

I agree with @GOKUL_ANANTH_M, no need of Workflow when you have OOTB option.

Under IDP - Provisioning, choose the notification recipients.

image

image
image768×195 7.13 KB

But what is the business value for this, I mean do we really need this ?

Maybe for leaver is good usecase to notify the manager that to for contractors only.

You might be having a business requirement for this usecase, I have been thinking what it can be, but I didn’t get any.

You can add a DL email address as well under specific users, so I don’t recommend workflow.

Please note that, an email is sent for every user on respective LCS change which will be annoying to the manager or a team if there are more users.

Thanks
Krish

2 Likes
6

While workflows will give you a lot of flexibility to control sending email and to modify the content, There is a lot that you can do with the email notification for lifecycle states as @MVKR7T said. The process will fire for every user and every lifecycle state change. If you want to control if the message is sent and the specific context, you can also use velocity in the email template. For example,

#if($identityLifecycleState.name == "Inactive")
    <P>   This is a notification that $user.firstname $user.lastname has been 
              disabled.  Please follow the offboarding checklist to retrieve their laptop, 
               etc.</P>
...
#else
    <!-- No email will be sent for other LCS -->
#end
1 Like
7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.