• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 62 subscribers
  • Views 967 views
  • Users 0 members are here
Options
Related

Enable and Disable account through the sync workflow

Patrick, NL
over 1 year ago

Hello, 

We are disabling accounts when they are inactive. But now I need to re-enable the account through the workflow. 

I throught about pushing 512 to the useraccountcontrol, but that would also overwrite other account option flags. 

Currently I am writing just 1 or 0 to an extensionattribute, and then have a step handler to run a script to enable/disable accounts based on this attribute, but I don't think this is the optimal way to handle. 

Does anyone have any better solution? Best would be somethink like just writing "False" to "edsaAccountIsDisabled", which isn't possible because it's a calculated value. 

Thanks in advance for your answer. 

Parents
  • 0 over 1 year ago

    Actually you CAN set edsaAccountIsDisabled.  I do it all the time.  Just make sure your ARSS sync job is connecting to your target domain using an Active Roles Connector.

    The other option would be to have a Change Workflow in AR itself respond to your existing setting of the extension attribute and use a Set Object Property Activity to apply the value to edsaAccountIsDisabled.


Reply
  • 0 over 1 year ago

    Actually you CAN set edsaAccountIsDisabled.  I do it all the time.  Just make sure your ARSS sync job is connecting to your target domain using an Active Roles Connector.

    The other option would be to have a Change Workflow in AR itself respond to your existing setting of the extension attribute and use a Set Object Property Activity to apply the value to edsaAccountIsDisabled.


Children
No Data