External loop Execution

Question

Using the web page I am trying to update a user and then using a business rule cause some properties to be change and then move them to a new ou.

I am getting errors while doing this.

See attached Word doc

Comments

Think I figured it out. I had created a Rule loop. I set actions to asynchronous and it worked.

---

Ok another question.

Will a scheduled task that updates a user trigger a business rule set to execute "after updating a User"?

Answer 1

Hello,

Yes, Business Rules are triggered every time an operation is performed via Adaxes service, no matter whether the operation is performed by an AD user or a Scheduled Task.

Also, returning to the loop issue, setting the action to execute asynchronously you just go rid of the warning message, but not of the reason that created the loop. To avoid creating loops, use conditions. For example, if a Business Rule is triggered after updating a user and updates the Department property, to avoid a loop, you can set a condition in front of the action to execute it only when Department is not modified.

By the way, didn't see the attached Word file. Can you post screenshots of your Rule here?

Comments

Here is my rule in attachment

Tell me something - I understand now that if I update a user or a scheduled task updates a user this may trigger a rule. But what about the property pattern? If a rule fires does the default property pattern for password cause the existing password value to be overwritten?

---

As to your Business Rule, it is quite clear why it creates a loop. In your Business Rule, you update the user's properties: you create a home directory for the user and map it to a drive, which involves setting the Home Directory and Home Directory Drive properties of the user account, then you modify the Notes, etc. Each such action involves updating the user's account. And since you Business Rule is set to be triggered after updating a user account, the Rule would keep triggering itself all the time if not for the built-in loop prevention in Adaxes Business Rules.

So, to prevent the Business Rule from being triggered by itself, you can, for example, check if one of the properties set by the Business Rule is empty. For instance, the Business Rule creates a home folder for the user, which probably means that the user does not have a home folder before the Rule is triggered. So, you can add a condition to check whether the Home Directory property is empty. To do this:

1. Launch Adaxes Administration Console.
2. Locate the Business Rule you need.
3. Select the set of actions and conditions of the Business Rule.
4. Press the Add Condition button.
   
5. Select the If <property> <relation> <value> condition.
6. Select If Home Directory is empty.
   
7. Click OK and save the Business Rule.

As to your question about Property Patterns, no, a Property Pattern will not cause overwriting any values. A Property Pattern can only contain some value generation templates and constraints that apply to a property. If a certain property has a default value, this is just a value that will be pre-generated on object creation to facilitate and speed up creation of an AD object and saving the necessity to fill in each field.