Hi there,

We recently deployed Okta Lifecycle with Workday as our identity master. We have a few items in our on-premise active directory that are not capable of being handled within the account lifecycle update process, and so we have a few lean custom powershell scripts to handle. For new accounts, this is very easy -- we push a "1" to a custom attribute on "create only" to flag the account and new and in need of process. The script then removes the 1 so the next iteration doesn't re-process the account.

is there some way that we can similarly "mark" an account any time a change is propagated from Workday to Universal Directory down to Active Directory? For example, if we set that same value to "2" for create and update....and say, the user's department changed and pushed down to active directory, would only the department update, or would all attributes be re-pushed? i think that would