General advice re: ordering actions

Question

General question....

We have a scheduled job as shown below.

As you can see we set some attributes sequentially i.e. "Set Account Status" followed by "Set Review Status", rather than setting both as part of the same Action. We also set some (i.e. the 'If approved' actions) after an 'approval' breakpoint, rather than as part of it, which as far as I can tell should result in the same effect.

Is there any particular benefit\downside for doing this in this way? So far as I can see the main difference is how the action is logged, but I was wondering if there are any other considerations, such as processing cycles (and if the attributes being set as native AD, the number of LDAP queries/actions etc.)?

Not urgent, just of interest!

Answer 1

Hello,

When you combine several property modifications in a single action, Adaxes uses only one call to your DC in order to perform all the property modifications that need to be done. If you put property modifications in different actions, there will be several network calls, one call per an action.

So, generally speaking, when you combine several modifications in one action, you get a certain performance gain, however the amount of the gain largely depends on your environment.

Comments

Thanks - that makes sense.