I know there is no OOTB capability to create OU container in AFX.
I'm planning to do it with JNDI, do we have any better option to handle the scenario?
What is the requirement to have an OU created from within G&L, instead of logging a request to service desk software for manual creation?
How many OUs will be created by this method?
How often will the ability be used?
Answers to these may lead to having an AD admin do it manually, so that it's an entirely controlled process. There are so many options to set and take into account when creating an AD structure, that the time taken to code a solution may outweigh having an admin do it manually.
From an auditing point of view, AD keeps logs of who creates objects, and service desk software can keep the request trail.
I have done something similar for a client that had this requirement. Within the workflow we make a call out to Java that does the OU creation for us, and then we go back into the workflow to create the object in the newly created OU. You could also do this using a PowerShell script that you call from the workflow using the PowerShell connector. We chose Java as the client already had some existing code doing it that we could re-use.
I have had this Use case before and it is fairly easy to build. What you need is a PowerShell connector (please do not go the java path it will take a lot more time to build) and a form to request the creation of a new OU.
The PowerShell code for creation of a new OU is very easy, google search.
You can add your own approval workflow to the form and even your own fulfillment workflow.
if you have trouble building it post a message here and we can help you build the form and connector.
Retrieving data ...