Fields are primarily used to display data from, and to write data to, user profiles. To carry this out, the fields displayed on, say, a Hosted Login form, are typically tied to user profile attributes. (Yes, there are a couple of exceptions -- most notably translatable strings -- but we won't worry about those for the moment.) For example, if you look at a field in an Identity Cloud flow, you can easily see the relationship between the field and the user profile; note the value of the schemaId attribute, which specifies the user profile attribute associated with the displayName field:
This simply tells you that, if you're looking at a displayName field, the data you see has been pulled from the user's display name. And if you save that form, the data shown in the displayName field will overwrite the data currently stored in the user profile; for example, if you change the on-screen version of the display name to Toni Ng then, as soon as the form is saved, the user's display name will be Toni Ng.
Note. Again, there are some exceptions to this rule. And, again, we won't worry about those exceptions right now.
- Text input
- Radio buttons
- Select menu
- Text area
- Date select
- Translatable string
Click the field of interest for more information about that field type, including a list of available field attributes and sample code for creating a new field of that type.