I’m tinkering with the Forms feature within ISC & was wondering if there is any way to show the submitter info about the user they’ve selected as a validation piece.
Currently, I have to rely on Employee ID as the select user option as it’s a unique immutable attribute for somebody to select.
Is there any way when an Employee ID is selected, the submitter can get a popup of associated attributes for this identity? Or, if possible, for these attributes to be revealed after they’ve clicked ‘submit’, even a message to say "you have just submitted a request for Employee ID 4000000 - Sean Krieger-Will - sean.kriegerwill@" etc…
I have considered a workaround: Create a new Identity Attribute with a transform applied to concat the employee ID & other info. Then I use that attribute as my user selection as part of the form… But this seems like a very workaround-fix for something that should come inherently with basic form functionality.
Hi @SeanK-W There’s a more easier workaround.
Create a new form and add a description field there. Make sure that the new form, accepts input. So now what you can do is craft a template in the description with whatever values you want to display. Example attached below
So the process will be:
You submit the first form → Workflow will read the data and get the identity information using get Identity (Action) → Then you pass the required information into the next form, using workflow → And you can see the data like you are validating.
Thanks Neeraj, appreciate the effort writing this up. And yes that’s exactly the sort of thing I’m after (as an end result). Admittedly this workaround sounds overly complicated for what should just be a simple display upon user selection…
However, as far as user experience goes - users want a 1 stop shop for forms. The solution you proposed, will this automatically load up a 2nd form for the user to fill ? Or does it require users to back out of 1 form and load up another?
I ask because I don’t think I’m going to be able to get this solution approved if it isn’t self-contained in 1 interface.
Its more of like once they fill the information on 1st form the workflow automatically triggers the second form so it is like on a single page it will appear just that the information will be only showed once they submit the previous form. And it is not something like they will have to move back and forth. So once they submit the the identity, they will see the user info just below that 1st form.
ISC Forms currently lack native support for dynamic user attribute preview based on a selected value like Employee ID. One workaround, as you mentioned, is creating a custom identity attribute using a Transform to concatenate name, email, and ID, then display that in the selection dropdown. However, this approach doesn’t allow real-time popups or validation messages during form filling. There’s no built-in functionality to show user details dynamically before submission or immediately after submission. A more dynamic user experience would require product enhancement, as current capabilities are mostly static and display-only.
Thanks Neeraj, ok that’s great, glad to hear it all sits in one interface from a user experience perspective.
So from a high level view, to allow a submitter to select 1 user from a dropdown and validate their selection, I’ll need the following setup:
Workflow 1 to allow user to utilise launchpad for Form 1 → Workflow 2 Trigger when Form 1 has been submitted to read the data and get the identity information using Get Identity (Action) → pass required information to Form 2 → See data user is validating and allow them to submit this form → Workflow 3 triggers when Form 2 has been submitted and action accordingly based on input from Form 2.
Total of: 2 Forms & 3 workflows.
Alternatively, create a new identity attribute & add a transform which concats some user details and utilise this attribute for the dropdown. Although, that does then cause issues when I try to utilise variables down the line as part of the information being passed from the form.
Wow, that seems like a lot of config & maintenance for a simple user selection. Not to mention this eats up workflow limits too… But I guess based on what Manvitha mentioned, the forms are quite primitive so I guess this would be the only way… Alright this gives me something to work from, thank you!
A little correction it would be 1 workflow 2 forms.
Workflow would be something like:
Trigger-> Form 1 → Get Identity> Form 2(pass the data as well which is required to show) > again do your workflow operations on what you wanted to achieve…
