A few days ago we announced the GA of Active Directory Plug-in for VCO. Now we want to show you an example how this plugin can be used.
Suppose you are an Active Directory administrator and you have to create a lot of new accounts for a newly created department of your company with a lot of employees. If just using the UI that your Windows 2008 server has for working with AD objects, you have to do a lot of annoying and repeating steps, but you have the VCO and the AD plug-in on your side
Let’s see how to do this job with the help of Active Directory Plug-in 1.0.0 for VCO 4.1
As the configuration of the AD plugin is not a topic of this blog post I'll skip it.
So… What is the criteria that we will observe to see if our exemplary Workflow has finished successfully?
- We will expect that after a successful run of our custom Workflow there will be a new object for the department – object of type Organizational Unit
- We will expect to have a User Group object that all newly crated User Accounts belong to, thus making it easy for the admins to grant permissions to all the users in this group
- We will expect to have one or more exemplary User Account created
Now when we have the goal and the criteria lets see how we can achieve it with custom Workflow that uses the Basic Building Blocks of the Active Directory Plug-in 1.0.0 for VCO 4.1
Here is an example of steps that our Workflow should repeat in order to fulfill the above requirements:
Step 1- Creation of Organizational Unit entity
- Check if there is an Organizational Unit entity already created for the new department of your organization
- If not it will be crated
Step 2 – Creation of User Group and associating it with newly created OU
- Check If the User Group already exist and use it
- If there is no such User Group then we should create it
Step 3 – Creation of user and associating it with newly created OU
- New user account is created
- Newly created user account is associated with the Organizational Unit created on Step 1
Step 4 – Add the user to the User Group
The following screenshot shows a possible implementation of the above steps
Lets now start this example and see what will be the result
First lets check how does the inventory tree look like before the run
Now it is time to start the Workflow and observe it during run-time
Filling the Input Parameters…
Workflow during run time…
…And the successful Finish …
Now it is the time to look at the results…
This is it…
There is an Organizational Unit called "Workflow Development" with two objects inside. One of it is the User Account "johnsmith" and the other one is the User Group "Workflow Developers"
… so we can conclude that we meet our success criteria