The auto-filled data is retained in text field but its throwing the required validation

a!localVariables(
  local!items: { a!map(name: "", email: "") },
  a!cardLayout(
    showBorder: false,
    contents: {
      a!gridLayout(
        headerCells: {
          a!gridLayoutHeaderCell(label: "Name"),
          a!gridLayoutHeaderCell(label: "Email")
        },
        rows: a!forEach(
          items: local!items,
          expression: a!gridRowLayout(
            contents: {
              a!textField(
                label: "Name",
                value: fv!item.name,
                saveInto: fv!item.name,
                /*inputPurpose: "NAME",*/
                required: true
              ),
              a!textField(
                label: "Email",
                value: fv!item.email,
                saveInto: fv!item.email,
                /*inputPurpose: "EMAIL",*/
                required: true
              )
            }
          )
        )
      ),
      a!buttonArrayLayout(
        buttons: a!buttonWidget(label: "Submit", validate: true)
      )
    }
  )
)

This works fine for me with or without the inputPurpose attribute that is specified.

- Which version of Appian are you on?

- Which browser?

Hi, it's not the Appian function issue, it's the auto fill (which we use data from browser wallet) feature which we use it in browser in that I'm facing the issue.

I fear Appian will not be very supportive of browser auto-fill functionality, at least when it comes to certain corner cases like you've described here.  If you believe the behavior is reproducible and counter to what a user might EVER reasonably expect, however, you might raise a support case with Appian (being sure to describe the exact reproduction conditions) and make them aware at least, in case a minor adjustment to the back-end behavior of the field would improve things.

If this is impacting all customers who have upgraded to 25.1, who has it as an issue in production?  We're being told since it is not a prod issue, can't be more than a sev3.  Any other customers impacted?

My team upgraded to the 25.1 platform and is encountering a similar issue. I look forward to connecting to discuss possible workarounds and collaborating to prioritize a resolution from Appian. Linked profile

If it's easily reproducible in 25.1 then I'd suggest anyone being impacted by it should open a support case with Appian.  I don't use the "input purpose" feature much (or at all) in my app so I haven't seen it one way or another yet.  And it doesn't seem to work in Interface Designer.

That's interesting, Mike. What alternatives do you prefer to use instead of the "input purpose" feature? 

It's not required, and the times I've tried it, users complain that it makes the form confusing to fill out.  This may partly be because it only has the option for "name", while most of the forms in my system would have separate "first name" and "last name" fields.  To be fair though, I haven't tried messing with it in a while.  But the real answer is, since it's not required, I "prefer" just not using it at all.

Hey Mike, can we have an offline discussion about this? I believe your knowledge can really be a breakthrough for my team. Even a 15-minute session should suffice for us to learn some workarounds.

I look forward to your response at aksat.parekh@globalexcel.com. I appreciate your help!

I'm always happy to chat with other devs to lend some expertise, but if it's specifically on the "input purpose" parameter of text fields, then beyond the fact that it's never really required, I must underscore that I am not all that familiar with how it actually works in normal usage for those who use it regularly (since i have used it very little and abandoned any old attempts I may have made in the past), so my insights into this specific feature will be really limited.

I'm always happy to chat with other devs to lend some expertise, but if it's specifically on the "input purpose" parameter of text fields, then beyond the fact that it's never really required, I must underscore that I am not all that familiar with how it actually works in normal usage for those who use it regularly (since i have used it very little and abandoned any old attempts I may have made in the past), so my insights into this specific feature will be really limited.