Problem Looping Email on Approval Request

Question

Hello,

I have a problem regarding approval, the case is I will send approval to the admin if there are additional users.

The process has been successful and the approval link has been successfully sent to the admin email, the problem is that the email sends several approval links.

In my case, here I have several OUs, there are system engineers and there are sales & marketing. here I want to add a user to the sales & marketing OU and the approval link was sent successfully but the link that was sent was not only for user A in the sales & marketing OU but also sent to user A on the OU system engineer even though I didn't add user A to the OU system engineer .

as a note:

I made "send approval" in "custom command" and then executed it in "business rule" before creating user.

Comments

Hello,

Sorry for the confusion, but we are not sure about the entire workflow. As we can see the custom command is executed by the RunHris scheduled task. Could you, please, post here or send us (support@adaxes.com) screenshots of the task and the command? Also, what is the triggering operation of the business rule in the first screenshot? Is it Before creating a user?

---

This is the workflow approval of my case.

First: If there is a new user added in HRIS then adaxes will run "RunHris" on the Scheduled Task.

Second: After the Scheduled Task is executed, it will automatically run the Business Rule (Before creating a user) which in the Business Rule will execute a custom command containing "Send Approval"

Answer 1

Hello,

Thank you for the provided details. There is no loop. It looks like the Before Buat User business rule triggered twice because there were two users with the same name created in two different OUs. The OUs are wandavision.net\PrimaSys\Branch Subaya and wandavision.net\PrimaSys\Chief. If you do not want the business rule to trigger for users created in either of the OUs, adjust the rule scope accordingly. For details, have a look at step 6 of the following tutorial: https://www.adaxes.com/tutorials_DelegatingPermissions_RequestApprovalForUserCreation.htm.

Comments

Hello,

Thanks for the previous answer, apparently that's not where the problem is but

After analyzing it, it turns out that the problem is not that there are two users who are the same but in the process of creating a user, is there a solution before the user is created, the user is first entered into the OU and then the approval process is carried out?

In the process of creating a user I use the script in the link below:

https://www.adaxes.com/script-repository/import-user-information-from-sql-database-s249.htm

---

Hello,

Sorry for the confusion, but we are not sure what exactly you mean. The script you referenced creates users in the OU the script is executed for. If there are multiple OUs in the scope (e.g. if executed in a scheduled task), the script will be executed separately for each OU and create/update users in all the OUs.