If you change that setting to “Yes” for the desired attribute(s) then any changes to those values will be given priority and moved to the front of any queue that may be built up for that driver. Simply put, if you look at the driver’s filter and more specifically at the attribute(s) in the filter that you want to give priority to, you will find an option that says “Perform Out of Band Sync (Subscriber)” with two options “Yes” and “No” with “No” being the default value. Yes, you can, but it comes with a warning. However, what if there is certain data that you want to give priority to so that it jumps to the front of the line? If the drivers process data in a first-in-first-out manner can priority be given to such data? The person in the front of the line of checked out, then the person behind them, and so on and so on. Very much like people lining up in a line to checkout at a retail store. When working with NetIQ IDM drivers it is well understood that the typical driver events are processed in a “first-in-first-out” order meaning that the first transaction detected by the driver is the first transaction processed and any subsequent transactions are queued by the driver which are then processed in the order they appeared.
