I am currently working on building an interactive form to all HR to be able to submit Emergency Terminations. The challenge I am facing listed below.
Can not display Employee Number in the Search (No option to select)
I currently have the form to select Display Name (with names like John Smith how is HR to know they grabbed the correct ID)
I can not figure out how to grab information from the Select Search Field and use it to populated more information on the user so that HR will know they have the correct user.
I can get this information to display from the workflow however at that time it is to late to confirm that the user is correct. At a high level either in the form or workflow I need to be able to show HR that they selected the correct user before they submit the form for processing any ideas?
Not sure why, but it does not seem like an option.
I also noticed that the value returned to Workflow from the form is the text from the dropdown to pick an identity. If I remember right, the id of the identity used to be available to the workflow. Is this right, or am I missing something?
If you mean the termination request is submitted by any eligible user and then it needs to be confirmed by HR, then you can have a second form in your workflow for HR to confirm the termination before actually processing the request
When you create a form it gives option of Predefined Values (Identities) it will only display display name of use , best option would be you can create another form which will display all the attribute of the user including employee number , this form values can be populated by modifying the workflow .
In workflow you can add additional step to get all the required identity attribute of the user based on the identity selected in previous form and then additional step to get the new form poulated with the values you wanted to discuss.
Form should have capability to display the attributes for the object it supports , but right now it’s not available .
@mpotti I had a similar circumstance before and ended up creating the form as a catalog item in ServiceNow. Since we wanted to tie additional tasks to it like equipment reclaim, it made more sense for it to live there.
I had the same issue, but the workaround i did was:
Once the HR selects the User i display another form and using workflow send the respective information. & at the end i have a dropdown button to ask the HR, are you sure to terminate the user (yes/no)?
the confirmation dropdown is marked as mandatory so the HR will have to select yes/no
And then using workflow i perform rest of the operation.
But the catch is that if they do select the wrong user, (they will have to relaunch the form) & i configured using predefined search (so they were able to search using display name and email)
..
Linking the thread for more information if you want to display the information.
To ensure the correct information is captured, I had the form transition over to another form (via workflows) and pre-fill the selected user’s identity attributes, including their unique identifier.
The problem with this, in addition to being a very poor user experience is that end users of your form can’t go back and be like “Oh actually.. it was not this user but someone else”, because workflows only flow in one direction. You basically need to terminate the whole flow and re-submit again.
Eventually, we ended up offloading the form functionality to a custom solution outside of ISC.
