AnsweredAssumed Answered

Need sAMAccountName variable to be used from AD Fulfillment to application fulfillment WF

Question asked by Vijayabaskar Balakrishnan

on Jul 27, 2017
Latest reply on Aug 2, 2017 by Vijayabaskar Balakrishnan

Like • Show 0 Likes0
Comment • 4

I would like to know, how can we use the variable of sAMAccountname that has been configured in AD Fulfillment workflow to be used in Application fulfillment workflow to have an instant update in AD followed by another application provisioning.

Currently, I’m relying on Rule to initiate Application fulfillment workflow which will trigger based on the reconciled data from Active Directory, post successful Account Creation.

I’m sure this approach will not help the end users to have respective application access immediately as IGL would wait for Active Directory identity collection to get complete.

Any better approach to minimize the delay for the action on follow up system.

No one else has this question

Outcomes

4 Replies

Boris Lekumovich Jul 27, 2017 10:11 PM
Mark Correct
Correct Answer
If you are using an account template to calculate the value for samaccountname and not changing it in the workflow runtime, then you can use the same account template for the other application account creation.

If you are calculating the value (for samaccountname) in runtime, then you can store your calculated value in a custom user managed attribute and then retrieve it in fulfillment workflow of the other application
1 person found this helpful
Like • Show 1 Like1
Actions
- Vijayabaskar Balakrishnan @ Boris Lekumovich on Jul 27, 2017 11:56 PM
  Mark Correct
  Correct Answer
  Thanks Boris for your input.
  
  Yes, I'm incorporating the username logic in the AD Fulfillment Workflow. So using sql execute, we can update the managed attribute which can be used as mapping attribute in respective AFX connector. This will help the AFX handler to do the rest.
  
  Hope, My understanding is right?
  Like • Show 0 Likes0
  Actions
  - Boris Lekumovich @ Vijayabaskar Balakrishnan on Jul 31, 2017 12:22 AM
    Mark Correct
    Correct Answer
    That's the general idea.
    You need to take into consideration different cases in which the process can fail. For example:
    What will happen when the fulfillment workflow of the other application will run before the AD workflow?
    
    Depends on the requirements and the approach you choose to take, you need to cover all possible failures (or at least be aware to them and create a process to handle them)
    Like • Show 0 Likes0
    Actions
    - Vijayabaskar Balakrishnan @ Boris Lekumovich on Aug 2, 2017 5:52 AM
      Mark Correct
      Correct Answer
      Yes, true. However the workflow is not allowing us to update any AVDB attributes through SQL Execute.
      
      We are getting the below error which is restricting us to save the workflow.
      
      Like • Show 0 Likes0
      Actions

Need sAMAccountName variable to be used from AD Fulfillment to application fulfillment WF

Outcomes

Related Content

Recommended Content