Property patterns are not updating mid script.

Question

Hello,

I am trying to create a custom command that handles the process of converting a user account for a temp to a FTE. This needs to:

1. move the user to a new OU.
2. change properties of the user.

My problem is that the source OU and destination OU's have different User property patterns. The command moves the user fine, but when it tries to rename the user or change other properties, it errors out on the property patterns as if the user was still in the source OU.

How do I get Adaxes to use the property patterns of the new OU instead of the old?

Custom command:
Set 1:
If user is located under "expiring accounts" OU
--Move the user to "xxx" OU

Set 2:
Always
--Modify the user: set employee type to...... etc.

Answer 1

Hello,

This is a bug in Adaxes that we'll fix in the next release. Thanks for the bugreport!

For now, we can suggest updating user properties using a PowerShell script. For example, in your Custom Command, you can use the Run a program or PowerShell script action instead of the Modify the User action to perform all the property modifications. To do this:

1. Launch Adaxes Administration Console.

2. Locate and select the Custom Command that you use for transferring users from temp to FTE.

3. Double-click the Modify the User action that you currently use to update user properties.
   

4. Select the Run a program or PowerShell script action.

5. In the Script field, type a script that will update the properties that you need.
   
   For example, the following script sets Employee Type to 'FTE' and Office to 'NY Department'

    $Context.TargetObject.Put("employeeType", "FTE")
    $Context.TargetObject.Put("physicalDeliveryOfficeName", "NY Department")
    $context.TargetObject.SetInfo()
   

   For more information on how to update user properties with scripts, see Modifying User Accounts.

6. When done with the script, enter a short description for it, click OK and save the Custom Command.

Comments

Hello,

Yesterday, we released Adaxes 2013.2 that contains a fix for the issue. Now, if an AD object is moved in a Business Rule, Custom Command or Scheduled Task, the object location is properly updated. You can download Adaxes 2013.2 here.

Upgrade Instructions.

For a complete list of new features and improvements, see What's New.