on Jun 29, 2016Can't we use the register user form type without using "register user command(non-visual)".
Because I need to create one simple form which has to be submitted for AD provisioning team for new user registration.
Without AFX, we can't create the parameters to set "register user command(non-visual)". There is no AFX - FYI.
Is there any other form type which would suffice this requirement. I tried all other types which has user selection page to start with the request.
Have you tried using a for of type global and then set the "changes apply to" to no users
then set the appropriate WF to have the information from the form mailed to the AD provisioning team
regards,
Edwin
Yes Edwin, I could able to create the form by importing the standard connectors and creating one AFX connector just to suffice this requirement.
How can I use the form variable in workflow.
I tried using ${jobUserData_PublicData_avform_FieldName} in sql select node. But it is not picking the submitted supervisor value.
Do you have any idea?
My requirement is to fetch the supervisor information from the form which has been configured with user picker Control Type.
The answer to your original question is no, a User Registration Form cannot/should not be used without the Register User Non-Visual Control (which is part of the end-to-end automation and the main purpose of the User Registration Form).
Does the AD provisioning team has access to Via G&L? If so, they could see the submitted form in the request details page. Would that be sufficient?
I agree, That's the reason why I imported all standard connectors and configured one dummy connector for Active Directory to customize the form with Register User Command.
Could you please let me know how to use the form variable in workflow.
My requirement is to fetch the supervisor information from the form which has been configured with user picker Control Type.
Hmm..., then I don't see why the Registry User form is being used at all in this case. A global form with a user picker field for the supervisor (and text/whatever-is-appropriate fields for the other parameters you need) should do the job and doesn't require the extra setup of the dummy connector and such, and doesn't tie up the business source with this dummy connector. What prompt the use of the Register User Form to being with?
Without register user command, you will not track the contractor onboarding in any of the logs. So I managed to sort it out with dummy connector in place.
Now all my concern is to call the form variable in approval workflow.
Title of the case is being modified. Hope it make sense now.
Hi Vijayabaskar,
while provisioning supervisor, you should have DN to provision in AD for manager.
when you select user from user picker you only have userid or id values .. not DN
to get the DN you should :
1) have a hidden text field : get default value as selected user in user picker
2) use webServices as dropdown option in form .. to get the DN value for the user selected in first step
3) pass this DN value in hidden text field : which variable you can try using in workflow if you are not using the RegisterUser command
Sanskriti Sanghvi Im not writing any values in AD here.
It is so simple, I just want to configure the supervisor approval workflow, the task of which should be assigned to the user(value of Supervisor Field - that has been assigned in the form).
I tried with sql node using ${jobUserData_PublicData_avform_Supervisor} to get the email address of the supervisor, but the approval task is not getting assigned to the user who has been assigned in the form.
Hope it is clear now.
can you post a screenshot of runtime variables?
PFB screenshots - Let me know if you need more details.
It seems that the screenshot is of a runtime for a specific SQL node.
Can you post a screenshot of the runtime for the entire approval workflow (in your running workflow, right click in an empty space and then choose properties) ?
Try using - ${jobUserData_PublicData_Vendor_Registration_Supervisor}
can you please try '${PublicData_Vendor_Registration_Supervisor}'
No, its not assigning to the picked user.
I have selected the full name option in the attached screenshot. Does it anything to do with?
How are you doing the assignment?
Can you share a screenshot of the approval node?
Assigning job variable of email address which has been extracted through sql query as mentioned above.
You need the user_id to assign it
I suggest the following:
Modify your user picker field so the value would be User Id
In your approval workflow, change the sql to:
select '${jobUserData_PublicData_Vendor_Registration_Supervisor}' as mySupervisor from dual
in the approval workflow, assign it in the following way:
Yes, it is getting assigned with the correct user.
Thanks a lot cheers!!!
You need the user_id to assign it
I suggest the following:
Modify your user picker field so the value would be User Id
In your approval workflow, change the sql to:
in the approval workflow, assign it in the following way: