We are delighted to share our new EIC Delivery Methodology for efficiently managing Saviynt Implementations and delivering quick time to value. CLICK HERE.

Trigger User Update rules when Email attribute is Updated

ssrnitish
New Contributor III
New Contributor III

Hi All,

We are re-generating Email when users firstname / lastname and certain other user attributes are updated using User Update rule config : Generate User Email

ssrnitish_0-1701432758564.png

Only after email is regenerated, we want to trigger New Account/Update Account tasks. we have configured user update rules with all below actions, but none of the rules are getting triggered even after email is changed.

Trigger Actions when :

User is updated from API calls

User is updated from Import

User is updated from UI.

 

Can anyone suggest if user update rule will be triggered when Email is updated using the "Generate User Email" option within the user update rule.

11 REPLIES 11

SumathiSomala
All-Star
All-Star

@ssrnitish Please share the rule configs screenshot and check user history tab whether the rule is triggered or not once email is updated for the user

Trigger Actions when :

User is updated from UI.

 

Regards,
Sumathi Somala
If this reply answered your question, please Accept As Solution and give Kudos.

alex1
New Contributor III
New Contributor III

@SumathiSomala 

Hi,

See screenshot below. Keep in mind that we have an exact copy for all different events, import UI and API updates, but with the same result.

alex1_0-1701435609658.png

alex1_1-1701435641320.png

So basically, only checking if the email attribute is updated. 

If we update the user email attribute manually (from UI) it works without any problems, however, when the email is updated via the email-generation rule (after the generation has been triggered by another user update rule, so not during creation) nothing happens. 

For the users, we can see that the users email got updated by our first update rule that generated a new email, but then nothing happens and no tasks are being created.

 

alex1
New Contributor III
New Contributor III

Technical rule can be found here:

alex1_0-1701436289052.png

 

Hi @alex1 

Thanks for reaching out. We are reviewing your query and will keep you posted on the same.

Regards,

Dhruv Sharma

Hi @ssrnitish @alex1 

I have replicated the issue in latest environment and behavior is as below.

User update rule will not be triggered when Email is updated using the "Generate User Email" option within the user update rule.

When a user update rule is created, there are below options. Since the user update rule/system is updating the email here. Hence none of the below options are applicable.

Dhruv_Sharma_0-1701936267797.png

Regards,
Dhruv Sharma
If the response is helpful, please click Accept as Solution and kudos it.

 

 

 

alex1
New Contributor III
New Contributor III

In our scenario, we cannot immediately generate a new email address for all users, instead we need to do it only for a specific user group (not separated by attribute, but rather if they are rehire or not), so we cannot use the email-generation in our user import. This is why we have to trigger the email-generation in an user update rule. In this case, if we would want to trigger other actions (such as creates/updates) how would we do that? It doesn't make sense that an attribute is updated, but we cannot trigger actions based of it? This cannot be the expected outcome right?

Hi@alex1

You can try the below approaches.

User update rule1-> Generating Email based on some conditions (firstname/lastname update etc)
User update rule2-> Generating certains tasks if Email updated (Currently not working as Email is getting updated by user update rule/system not by UI/API)

Approach1 (Recommended)
You can combine the User update rule2 actions in user update rule1 actions itself. So that it will generate the email and create the tasks which you want to create in rule2 as a result of email update.

Approach2 
You can make the rule2 as retrofit and run the detective job.
Detective job should trigger user update rule irrespective of the user email updated through UI/API or generate email action of user update rule.

Regards,
Dhruv Sharma

@alex1 : Out of the approaches @Dhruv_Sharma suggested I would suggest Approach1 which to combine both rules in one rule.


Regards,
Saathvik
If this reply answered your question, please Accept As Solution and give Kudos to help others facing similar issue.

ssrnitish
New Contributor III
New Contributor III

Hi @sk , @Dhruv_Sharma ,

We have already implemented our solution using Approach 1 as our work around  before posting the issue in Forums.

But we mainly wanted to understand why the rules are not getting triggered when email is getting generated/updated using User update rules? I assume, when email is updated using user update rule, it might internally get updated via SQL Query which is neither from API/UI/Import updates due to which the rules are not getting evaluated upon email update.

Thanks for your replies.

 

Regards,

Nitish

Currently that how design is implemented , task can be completed anytime hence adding both in same rule will not work.

You can submit idea ticket referencing this forum link


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

alex1
New Contributor III
New Contributor III

Created idea yesterday here: EIC-I-5314