AnsweredAssumed Answered

Request forms for user onboarding

Question asked by Venkata Palakaveeti on Jul 19, 2016
Latest reply on Jul 27, 2016 by Kin Kiu Yiu

Like • Show 0 Likes0
Comment • 12

Hi All,

I have an use case where contractor users can be onbarded using VIA portal.

1. I have created a request form to accept user firstname, lastname, department and date of joining.

2. I have created a table in local database (AVDB) and a stored procedure to accept the parameters along with a sequence (for the user id attribute).

3. Now to provision the values entered in the form I am trying to create workflow that accepts the parameters given in the form and insert them to the table created in AVDB.

for example in the SQL EXECUTE node am trying to pass these parameters:

execute avuser.insertCONTRACTORS ('${avform.Lname}','${avform.Fname}', '${avform.Dept}', '${avform.DOJ}');

But the above is not working as the sql node giving error for the above execute command saying "INVALID SQL COMMAND".

May I know how to resolve this or is there any better way to achieve this?

(NOTE: My plan is after we insert the data into a table, I can create an Identity Collector to pull back the user and create an account in VIA)

Kin Kiu Yiu

Jul 26, 2016 2:36 PM

Correct Answer

This means there is no item int he CR to be processed. Is there a "Register User Command (Non-Visual)" control on the form? If so, then check the CR generated by running the form and make sure there is a item to create an account for the user. If that also checks out, then verify the "Create Account" capability is enabled on the Connector.

Hope this helps.

See the reply in context

No one else had this question

Outcomes

Boris Lekumovich

Jul 19, 2016 9:48 AM

Instead of execute, try using call

Actions

Boris Lekumovich

Jul 19, 2016 9:50 AM

Also, you can consider using the Register User type of form

Actions

Kin Kiu Yiu

Jul 19, 2016 7:22 PM

Just my opinion, but I'd rather using a AFX DB connector instead of the SQL node to add a new user to the local directory (which you'd probably have to create to associate with the IDC). Then, you can use a "Provisioning Command (Non-Visual)" control to invoke the connector capacity to do the database insert. Sure, this involves more moving parts and runs slower. But, it provides the flexibility in case you've to move the contract depot into a Active Directory somewhere down the road. You'd have to re-implement the whole solution again if using the SQL node, instead swapping out the connector.

On the other hand, "piggy backing" the AVUSER like this is risky. Migration could potentially wipe out any store procedures that you added, so there is a risk of things stop working after upgrading/patching. There is also risk of name conflict if we add new tables/store procedures/etc into the database. I'd strongly recommend NOT to do that.

Hope this helps.

Actions

Sanskriti Sanghvi

Jul 19, 2016 8:33 PM

Hi,

you can user

Form type: "Register user" and use the AFX DB connector mapped in register user command to provision the user in database.

This would be much easier, then you can collect these users using a database type collector.

Actions

Kin Kiu Yiu

@ Sanskriti Sanghvi on Jul 20, 2016 2:04 PM

Right. Just a reminder that the Register User Form creates a CR to invoke the "Create Account" capability specifically (i.e. that capability has to be enabled in the connector).

Actions

Venkata Palakaveeti Jul 21, 2016 12:34 AM

Hi,

Can you please me on how to invoke the "Create Account" capability?

Actions

Venkata Palakaveeti Jul 25, 2016 3:47 AM

Is it possible to attach a Naming Policy to Register User Form to create an account in Active Directory?

Else, what is the best method to generate a unique sAMAccountName?

Actions

Kin Kiu Yiu

@ Venkata Palakaveeti on Jul 26, 2016 2:25 PM

You can go to the menu item "Requests->Configuration", and define Naming Policies under the "Naming Policies" tab. Once it is defined, then you can map it to the Active Directory either on that policy's detail page or under the "Naming Policies" tab on that Active Directory's detail page.

If the samAccountName is a collected user attribute, then you can probably use the "Uniqueness" setting in the Naming Policy to generate an unique account name.

Actions

Venkata Palakaveeti Jul 25, 2016 10:56 AM

I have created a workflow using default afx work flow as shown in the below screenshot. I have included an sql execute node to call a stored procedure which takes user 1st and last names and calculate the unique samaccountname. I am trying to capture that in AFXCUSTOM_CUSTOM_ACCOUNTNAME attribute and pass it to AFX handler.

When I user the Register User form configuration as shown below and try to create a user in AD.

Unfortunately, my request is getting completed by directly going to Stop from Calculate Items to Work on. It skips all other nodes.

Actions

Kin Kiu Yiu

@ Venkata Palakaveeti on Jul 26, 2016 2:36 PM

Hope this helps.

Actions

Venkata Palakaveeti Jul 27, 2016 6:24 AM

hi Kin, it is working now, I have attached the Naming Policy that gets processed when a request is raised using Register User form for AD account.

Thanks a lot for your time.

Actions

Kin Kiu Yiu

Jul 27, 2016 10:47 AM

You're welcome and glad to hear it is working.

Have a good day.

Actions

12 Replies

Boris Lekumovich Jul 19, 2016 9:48 AM
Mark Correct
Correct Answer
Instead of execute, try using call
Like • Show 0 Likes0
Actions
Boris Lekumovich Jul 19, 2016 9:50 AM
Mark Correct
Correct Answer
Also, you can consider using the Register User type of form
Like • Show 1 Like1
Actions
Kin Kiu Yiu Jul 19, 2016 7:22 PM
Mark Correct
Correct Answer
Just my opinion, but I'd rather using a AFX DB connector instead of the SQL node to add a new user to the local directory (which you'd probably have to create to associate with the IDC). Then, you can use a "Provisioning Command (Non-Visual)" control to invoke the connector capacity to do the database insert. Sure, this involves more moving parts and runs slower. But, it provides the flexibility in case you've to move the contract depot into a Active Directory somewhere down the road. You'd have to re-implement the whole solution again if using the SQL node, instead swapping out the connector.

On the other hand, "piggy backing" the AVUSER like this is risky. Migration could potentially wipe out any store procedures that you added, so there is a risk of things stop working after upgrading/patching. There is also risk of name conflict if we add new tables/store procedures/etc into the database. I'd strongly recommend NOT to do that.

Hope this helps.
Like • Show 1 Like1
Actions
Sanskriti Sanghvi Jul 19, 2016 8:33 PM
Mark Correct
Correct Answer
Hi,

you can user
Form type: "Register user" and use the AFX DB connector mapped in register user command to provision the user in database.
This would be much easier, then you can collect these users using a database type collector.
Like • Show 0 Likes0
Actions
- Kin Kiu Yiu @ Sanskriti Sanghvi on Jul 20, 2016 2:04 PM
  Mark Correct
  Correct Answer
  Right. Just a reminder that the Register User Form creates a CR to invoke the "Create Account" capability specifically (i.e. that capability has to be enabled in the connector).
  Like • Show 0 Likes0
  Actions
Venkata Palakaveeti Jul 21, 2016 12:34 AM
Mark Correct
Correct Answer
Hi,

Can you please me on how to invoke the "Create Account" capability?
Like • Show 0 Likes0
Actions
Venkata Palakaveeti Jul 25, 2016 3:47 AM
Mark Correct
Correct Answer
Is it possible to attach a Naming Policy to Register User Form to create an account in Active Directory?
Else, what is the best method to generate a unique sAMAccountName?
Like • Show 0 Likes0
Actions
- Kin Kiu Yiu @ Venkata Palakaveeti on Jul 26, 2016 2:25 PM
  Mark Correct
  Correct Answer
  You can go to the menu item "Requests->Configuration", and define Naming Policies under the "Naming Policies" tab. Once it is defined, then you can map it to the Active Directory either on that policy's detail page or under the "Naming Policies" tab on that Active Directory's detail page.
  
  If the samAccountName is a collected user attribute, then you can probably use the "Uniqueness" setting in the Naming Policy to generate an unique account name.
  Like • Show 0 Likes0
  Actions
Venkata Palakaveeti Jul 25, 2016 10:56 AM
Mark Correct
Correct Answer
I have created a workflow using default afx work flow as shown in the below screenshot. I have included an sql execute node to call a stored procedure which takes user 1st and last names and calculate the unique samaccountname. I am trying to capture that in AFXCUSTOM_CUSTOM_ACCOUNTNAME attribute and pass it to AFX handler.

When I user the Register User form configuration as shown below and try to create a user in AD.
Unfortunately, my request is getting completed by directly going to Stop from Calculate Items to Work on. It skips all other nodes.
Like • Show 0 Likes0
Actions
- Kin Kiu Yiu @ Venkata Palakaveeti on Jul 26, 2016 2:36 PM
  Unmark Correct
  Correct Answer
  This means there is no item int he CR to be processed. Is there a "Register User Command (Non-Visual)" control on the form? If so, then check the CR generated by running the form and make sure there is a item to create an account for the user. If that also checks out, then verify the "Create Account" capability is enabled on the Connector.
  
  Hope this helps.
  Like • Show 2 Likes2
  Actions
Venkata Palakaveeti Jul 27, 2016 6:24 AM
Mark Correct
Correct Answer
hi Kin, it is working now, I have attached the Naming Policy that gets processed when a request is raised using Register User form for AD account.
Thanks a lot for your time.
Like • Show 0 Likes0
Actions
Kin Kiu Yiu Jul 27, 2016 10:47 AM
Mark Correct
Correct Answer
You're welcome and glad to hear it is working.

Have a good day.
Like • Show 0 Likes0
Actions

Request forms for user onboarding

Outcomes

Related Content

Recommended Content