• State Verified Answer
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 61 subscribers
  • Views 5610 views
  • Users 0 members are here
Options
Related

Create Workflow with input form for collecting input data

markus.sitta
over 4 years ago

Hello All,

I am relatively new to AR, and I have to create a worklow for new users. If the User is created, a multi admin workflow should start. Initialision of the workflow is clear for me. Now the challenge, where I did not know how to achieve this goal?

The workflow should forward an request to an admin, which provides a phone number for the new User (posssible solution an input form). After providing this, the workflow should go to another adimin, who also types in AD Attributes and so on. At the end of the workflow a final approver should check the input from the others, and if ok, the AD Attributes should be set after approval from last approver.

Now my question, how can I achieve this? Are there existing forms for this input data, and how are this attributes are saved in the forms during the running workflow? I searched OneIdentidy Support KB and also searched this forum, but could find an appropriate possible solution.

Does anybody have an idea how to solve this? Any help will be welcome!

Many Thanks in advance!

Markus

Parents
  • 0 over 4 years ago

    What I would do is:

    Create an AR Workflow that notifies the Admin to go to the new user's property page to put in the phone number.  You can embed the name of the new user in the notification easily as there is a "token" for the in-process user's details (name or any other property) available.

    In the Web UI, your admin would go to the user properties page of the newly created user as requested by the notification

    The entry of the phone number (actually the "Save" action) by the Admin would then trigger the next workflow to tell the next admin to go and edit the required attributes (the phone number modification is the workflow trigger / start condition).  To make the attribute update task easier for the next admin, using out of the box customization, I would create a new tab on the existing user properties dialog of the Web UI that contains the required attributes.

    You would once again use the setting of the attributes as a trigger / start condition for the last workflow that would request approval for the setting of the attributes from whomever you choose (by way of an Approval activity in the workflow inserted prior to the update attributes action).

  • 0 over 4 years ago in reply to JohnnyQuest

    Hey Johnny,

    many thanks for your help and suggestion, but I actually stuck in the starting of the workflow, it did not start! I created a sync workflow for creation of users from an HR System. The User will be created successfully in a dedicated OU.

    Now I would like to start the workflow, where dedicated User should provide information for these Users (e.g. phone number, mobile number, hardware ordering etc.). But I tried many things for "Conditions for starting the workflow", meaning creation of the user, or modifiing of the user etc, but nothing worked for me, the workflow did not start? Do not know if I make a logical error in thinking?

    Any idea what I do wrong?

  • 0 over 4 years ago in reply to markus.sitta

    You should be able to set a condition of the start where:

    Triggering event is the creation of the user

    Setup a further condition where the action is taken by your sync service account in your "new users" OU.

    Do you have a separate user account running your sync service jobs?

  • 0 over 4 years ago in reply to markus.sitta

    I take it that this initial workflow is just for sending a notification and not an approval workflow? There are essentially three items that can be configured to start a workflow. The Operation Conditions or action, which in this case should be set to Create User. The next items are Initiator Conditions or "who and where", this tells Active Roles to start the workflow if it was done by a certain set of users on a certain directory container. It defaults to Any User as the initiator and all of Active Directory for the container. The last items that can be configured are LDAP filtering conditions, but these are blank by default. Is this what you have configured?

Reply
  • 0 over 4 years ago in reply to markus.sitta

    I take it that this initial workflow is just for sending a notification and not an approval workflow? There are essentially three items that can be configured to start a workflow. The Operation Conditions or action, which in this case should be set to Create User. The next items are Initiator Conditions or "who and where", this tells Active Roles to start the workflow if it was done by a certain set of users on a certain directory container. It defaults to Any User as the initiator and all of Active Directory for the container. The last items that can be configured are LDAP filtering conditions, but these are blank by default. Is this what you have configured?

Children
No Data