Why yes, yes indeed.  But not as a Workflow.

In User App/Identity Apps under Users, there is a + sign, that following the DAL for the User entry will allow those with permissions to create users.

This takes next to no work to configure but has next to no logic supported, except what the DAL lets you do. (Which is more than you might suspect... Can provide list of values for a drop down via DAL and more).

Thanks for the information Geoffrey, I am quite new to IDM, what I am trying to do is the following.
Create a workflow that allows me to create a user in EDirectory, the final objective is for this workflow to have some approvals and in some cases assignment of Roles.
But at this moment only those who take the first step by creating the form and when completing the information create the user in EDirectory, later I will be assigning the Roles 30 necessary to provision the account in AD.

Thanks!

You of course can do it multiple ways. The built in Create User form is meant to be simple solution.

Then they can use the built in Request Access workflows for Roles, which will honour Approvals and whatnot.

Assigning Roles is actually NOT a simple task.  In principle, the field collects the Role/Roles to assign, then the workflow loops over the collected info to do the Request Roles action.  Which then triggers approvals if set on the Roles.

Thus your call... 

Thanks Geoffrey, I am a little more clear at this time. I will advance to the solution!

Also, one has the "chicken and egg" issue of roles cannot be assigned to a user that doesn't exist yet.

Combining user creation and role assignment in one form (to rule them all) is asking for trouble in my opinion. 

One can do a lot with a workflow, but they rapidly get complex.

It can be an artform determining the correct balance between the customer's desire for keeping it simple (they always just want one form) and developing something that is generic enough to be maintained and used as a building block as the customer identifies new use cases.

I prefer to use the event based aspects of IDM more. Instead, have the creation of a user with specific attributes trigger the other approval / role assignment tasks.

Remember you can also assign a approval workflow to a role. Which will fire off an approval task to the relevant person(s) when the role is assigned (role is not fully provisioned on the user until the approval process is completed).

Simple approval workflows can also be created directly in the IDM Apps UI. These are surprisingly powerful considering they are so quick to set up.

The product also allows you to develop complex approval workflows in Designer. We have some relatively complex approval workflows at customers that handle scenarios that OpenText don't really support.