0 votes

Hi There,

Im looking to combine multiple built in commands to create a process. I would like to make one command that when clicked will enable an account, walk you through the Change OU prompt, prompt you to add the user to group, and at the end fire off a custom email. The OU and groups will change from user to user, so i would like the Change OU and Add to Group built in commands to be used, since they will ask you where and what to add the user to.

Thanks,
Chirs

by (270 points)

1 Answer

0 votes
by (294k points)
selected by
Best answer

The scenario will include a Home page Action and a Business Rule triggering After Updating a User.

The Home Page Action will allow users to select the OU and the group for the new user. The Business Rule will add the user to the specified group and then move to the desired OU.

i. Creating the Home Page Action

  1. Launch Adaxes Web Interface Customization Tool.
  2. Select the interface type and click Configure Home Page Actions on the General tab.
  3. Click Add and select Modify User.
  4. On step 2 of the wizard, define the conditions for selecting the user to be modified and click Next.
  5. Select Use customized form and click Customize Form.
  6. Delete all the sections except for one (e.g. General).
  7. Delete all the properties from the section and click Add below Section fields.

    Now, you need to add the properties that allow users to select an OU and a group. For users to be able to pick an OU and a group, you need to use DN syntax properties (e.g. Assistant and See Also). To add the properties to the form:
  8. Double-click the Assistant property.
  9. Select Show only the following object types.
  10. De-select Users and Contacts and click More object types.
  11. Select Organizational-Unit and click OK twice.
  12. Click Add below Section fields again and double-click the seeAlso property.
  13. Select Show only the following object types.
  14. Select only Groups and click OK.
  15. Finish creating the Home Page Action.

ii. Creating the Business Rule triggering After Updating a user

  1. Launch Adaxes Administration Console.

  2. Right-click your Adaxes service node, navigate to New and click Business Rule.

  3. On step 2 of the Create Business Rule wizard, select User Object type.

  4. Select After Updating a User and click Next.

  5. Click Add Action.

  6. Select Add the User to a group and click Select Group.

  7. Activate the Template tab and paste the following into the Template field: %seeAlso%.

  8. Click OK twice.

  9. Right-click the action you have created and click Add New Action in the context menu.

  10. Select Move the User and click Select Location.

  11. Activate the Template tab and paste the following into the Template field: %assistant%.

  12. Click OK twice.

  13. Right-click the action again and click Add Condition in the context menu

  14. Select If PowerShell script returns true.

  15. Paste the script below into the Script field.

     $groupDnAttribute = "seeAlso"  # TODO: modify me
     $ouDnAttribute = "assistant" # TODO: modify me
    
     $Context.ConditionIsMet = $False
     if ($Context.IsPropertyModified($ouDnAttribute) -or $Context.IsPropertyModified($groupDnAttribute))
     {
         $Context.ConditionIsMet = $True
     }
  16. Enter a short description and click OK.

  17. Right-click the action you have created and click Add New Action again.

  18. Select Enable/Disable the User account.

  19. Select Enable the User account and click OK.

  20. Finish creating the Business Rule.

You should have something like the following:

0

That worked great! The only issue i have now is that when using the task the fields show up as Assistant and See Also, is there any way to make the label show up as Group and Organizational Unit"? Also instead of setting the OU via the business rule and grabbing it from the Assistant field, why cant the OU just be selected as an Object property so it is changed during the Home Page task?

Thanks,
Chris

0

Hello,

The only issue i have now is that when using the task the fields show up as Assistant and See Also, is there any way to make the label show up as Group and Organizational Unit"?

For information on how to specify custom display names for properties, have a look at the following help article: http://www.adaxes.com/help/?HowDoI.Mana ... Names.html.

Also instead of setting the OU via the business rule and grabbing it from the Assistant field, why cant the OU just be selected as an Object property so it is changed during the Home Page task?

There is no such possibility. To change the location of a user account you need to perform a move action.

0

That did it, thanks so much for your awesome support!

Related questions

0 votes
1 answer

With a new user, the groups are added (see picture). Since some groups are managed by other teams, I want them to accept the addition as well. However, I can only confirm ... is added to the following groups and that they accept this in one step? Thanks a lot

asked May 31, 2023 by DRiVSSi (320 points)
+1 vote
1 answer

Hello, Is there a way I can make the Desktop Adaxes Admin Console Dark Themed? I know how to on the Web Interface, but wondered for the full console. Thanks!

asked Nov 19, 2023 by Edogstraus00 (490 points)
0 votes
1 answer

Our Help Desk currently 'mirrors' the group membership of a new user based on another existing user in our AD. I'd like to be able to automate this so that the initiator ... and 'paste' it on the new user being created. Any help on this would be appreciated!

asked Apr 21, 2020 by RayBilyk (240 points)
0 votes
1 answer

Hi there, i've a custom command with multiple powershell scripts (for clearance reasons). If for example the frist script produces an error i Write an Error but the next ... tried with an simple exit 1; I only Write-Errors on issues. Kind regards, Constantin

asked Jul 23, 2021 by Constey (190 points)
0 votes
1 answer

I am trying to make a custom report that is basically the "Members of Groups" default report but instead of selecting Directory Objects, I want to select groups. The Members of ... will not work in Adaxes 2023 and later. I am running 2023.2 -- Suggestions?

asked Aug 13 by AvenuesRecovery (20 points)
3,588 questions
3,277 answers
8,303 comments
548,100 users