Hi guys,
Is there any way to get pre populated attribute values of a user In form?
For Example:
If I select a user from User dropdown list, The user’s email, Manager Name and Manager email should be visible as a read only field in the same for.
I’m working on a workflow and need to get the details. Currently what I’m doing is.
I’m submitting the form which contains user’s name and created a 2nd form and used the second form to populate the values.
Will Appreciate your inputs
Thanks!!
Hello,
It`s possible!
All the attributes are provided as input parameters. In the workflow, the first form collects the username or user ID from the user. Then, the workflow automatically retrieves the corresponding user data (such as name, email, roles, or other relevant details) based on that username/user ID. Finally, this retrieved data is passed as input to the second form, allowing it to pre-populate.
Let`s say that you want to display the userName
1 - create an field called “UserName“
2 - Create a input called “UserName”"
3 - Create a Condition to this field:
If UserName Is Not Empty
If All rules are met
Set Default Value In UserName
Disable **UserName
input:**
condition:
Hi @YanCoelho ,
This is what my current approach. I want to know if there’s any other way to do it without using 2 forms. I need to populate the user values Before Submitting the 1st form
Hi @selvasanthosh,
I don’t believe we can populate values in a form in real time. You should continue with the same approach you’re using now.
ISC forms don’t support real-time “on change” population (no lookup/binding triggered when you select an identity). A form can only be prefilled from workflow inputs at render time, so values can’t update in the same step before submit.
The most supportable pattern is: Form 1 = select identity → workflow fetches identity + manager attributes → Form 2 = prefilled read-only review/confirmation. If you want it to feel like one screen, make Form 2 a “Review” page with the same layout and only a Confirm/Submit button.
From an adoption standpoint, this is a common enterprise UX need — it would be great to have a native “dynamic field binding / lookup on selection” capability for Forms.
