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

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