Leveraging Intelligent Recommendations for Operational Transformation. AMS Partners click HERE | EMEA/APJ Partners click HERE |
02/14/2024 12:39 PM
Hi,
We have a user update rule which used to work perfectly fine in v5.5. After migrating to 23.12 somehow it is not working. It supposed to generate user mail based on some condition, which is not happening.
Can someone suggest how can this be fixed?
Regards,
Indranil
Solved! Go to Solution.
02/14/2024 07:33 PM
What is you Email Generation Rule at global config ?
did you turn off /uncheck Reuse same email for user config in global configurations?
02/14/2024 08:07 PM - edited 02/14/2024 10:30 PM
(##a.customproperty60 isupdated## and a.customproperty60 is not null) and a.email is null
02/16/2024 12:41 PM
Hi @rushikeshvartak , I checked with migration team. They confirmed that is migrated properly and they have given screenshots also. The parenthesis I yet to test. Strange thing is new hire email generation, system user generation is happening properly as per stored procedure, only the rehire case is affecting this.
Regards,
Indra
02/16/2024 12:35 PM
Another solution is turning off the "Reuse same email for user" in global configuration.
https://forums.saviynt.com/t5/identity-governance/generate-user-email/td-p/44712
02/16/2024 12:42 PM
I tried it once and got the same result.
Regards,
Indra
02/16/2024 01:46 PM
Share logs. I have validated in 24.1 and its working
03/05/2024 10:22 PM
Hi @rushikeshvartak actually this worked. We had some other problem also, but this was one of the main reason why the email didn't regenerate.
Regards,
Indranil
03/04/2024 05:12 AM - edited 03/04/2024 05:13 AM
@rushikeshvartak sorry for hijacking this thread, but is this planned that the preference for "Reuse same email for user" is working in the intended way.
Based on documentation and the description text below, you should check this field, if you want to reuse an already existing mail address.
Example:
User is inactive and has set john.doe@company.com on the user. If the mentioned preference is checked and you have a rejoiner action, the result is, that the user will keep the same mail and now new mail will be generated (even if this is configured on the import job).
If I now uncheck ""Reuse same email for user", the assumption would be, that the user will get a new mail address, because the reuse is unchecked. For example john2.doe@company.com
So based on the description in the docu and also on the attribute, it is unclear how this flag works and if it works at all in the intended way.
Can you provide maybe a sufficient explanation, when to use this flag and when not and possible at this to the documentation.
03/04/2024 10:02 PM
@Alex I had a similar case and ended up logging ticket with Saviynt. I am yet to get the response from Saviynt support.
03/19/2024 12:48 AM
@Manu269 Have you received a response from Saviynt regarding this topic?. Thanks!
03/19/2024 01:00 AM
Response is still awaited.
They are checking with engineering team.
03/05/2024 07:32 PM
Please use feedback option on documentation
03/04/2024 11:16 PM
@Manu269 sounds good, can you please keep up posted about the outcome?
Thanks
Alex