User Interface - Recent Threads

RE: Upload file component, edit name functionality issue

Shubham Aware — Thu, 28 May 2026 15:13:00 GMT

Use document() to read the edited name, not fv!files.name; with EDIT_NAME, the new name is saved on the document, while fv!files.name keeps the original.

[quote userid="94558" url="~/discussions/f/user-interface/40465/upload-file-component-edit-name-functionality-issue"]local!currentUploadNames: touniformstring(fv!files.name),[/quote]

local!currentUploadNames: touniformstring(
  a!forEach(
    items: local!uploadedDocuments,
    expression: tostring(document(fv!item, "name"))
  )
)

Upload file component, edit name functionality issue

kavyac0003 — Thu, 28 May 2026 15:05:07 GMT

Updating the file name in fileuploadfield() using parameter documentActions: "EDIT_NAME", unable to fetch new updated name in either local variable or fv!files.name and validation is failing.

a!fileUploadField(
label: "Documents",
documentActions: "EDIT_NAME",
labelPosition: "ABOVE",
value: local!uploadedDocuments,
saveInto: { local!uploadedDocuments },
validations: {

a!localVariables(
local!currentUploadNames: touniformstring(fv!files.name),
local!existingDocNames:local!existingDocs,

local!hasDuplicates: length(intersection(local!currentUploadNames, local!existingDocNames)) > 0,

local!hascurrentDuplicates: length(local!currentUploadNames) <> length(union(local!currentUploadNames, local!currentUploadNames)),

if(
or(
local!hasDuplicates,local!hascurrentDuplicates),
"Duplicate files detected in your selection. Please ensure all uploaded files have unique names.",

null

))

},
maxSelections: 10,

helpTooltip: "Supported file types: JPEG, PNG, SVG, PDF, Microsoft Excel, Microsoft Word, Microsoft PowerPoint, TXT, CSV, XML, ZIP"
)

Reset value in datetimefield

josemanuc746243 — Thu, 14 May 2026 08:15:41 GMT

Is there any way to reset the value to null when only the date or time is entered in a datetimefield?

Screenshots attached

1. Enter only the date in 'Fecha entrega en mano'

2. Click on CANCELAR and confirm

3. Click on EDITAR again

4. As can be seen in the screenshot, the previously entered value is displayed by default. Appian does not reset the value to null for datetimefields. However, for fields other than datetimefields, it does reset them and previously entered values do not appear.

RE: Reset value in datetimefield

Mike Schmitt — Tue, 19 May 2026 15:13:11 GMT

[quote userid="71145" url="~/discussions/f/user-interface/40429/reset-value-in-datetimefield/154637"]The problem arises when I enter only one of the values. It seems that, at the interface level, Appian does not reset the value correctly[/quote]

Your reading is correct, and we have zero control of this from the design side, unfortunately.

RE: Reset value in datetimefield

josemanuc746243 — Tue, 19 May 2026 09:11:41 GMT

The only issue with the datetimefield component is that it causes problems when I enter just the date or the time, even though the value of the local variable reverts to its previous value after clicking ‘Cancel’. It seems to be an Appian issue with that specific component, because we’re using a textfield that employs the same input rule to display the value as the datetimefield, and it displays correctly.

I attached screenshot in the reply to Harsha

RE: Reset value in datetimefield

josemanuc746243 — Tue, 19 May 2026 09:07:46 GMT

When I click on ‘Edit’ and enter the date and time, or clear both fields and then click the ‘Cancel’ button, the variable value resets correctly when I edit it again. The problem arises when I enter only one of the values. It seems that, at the interface level, Appian does not reset the value correctly for that specific datetime field because the read-only field is a text field; it does display the value correctly using the same local variable, but the local variable is updated correctly.

1. I delete the time

2. Value 'Fecha acuse' after deleting the time

3. Value 'Fecha acuse' after cancel

4. Textfield in mode read only

5. Datetimefield (We are using the same input rule to display the value in both the text field and the datetime field)

RE: Store Inbound Email as Document in Appian Without Pulgin

Shubham Aware — Mon, 18 May 2026 11:38:07 GMT

Cannot store the original received email as .eml/.msg natively. The inbound email process only exposes metadata (from, to, subject, body, attachments) as process variables. The raw email file is never made available. OOTB, the best you can do is reconstruct the email content into an .html or .txt document using the Write to Document smart service.

Store Inbound Email as Document in Appian Without Pulgin

ashwinir5622 — Mon, 18 May 2026 10:00:26 GMT

We have a process in our environment which gets triggered whenever it receives an email. We have a requirement from business where they want the whole outlook email or any email sent by them to Appian which triggers the process to be stored as some document inside Appian. Without any pulgin option is there any way to achieve this?

RE: Reset value in datetimefield

Harsha Sharma — Fri, 15 May 2026 09:40:05 GMT

datetime field stores the data entered in one of the fields internally, which we cannot reset. To clear it properly configure a!save(local!dateTimeValue,null) in the button that submits the form.

Additionally if cancel/submit button have any process flow that writes the data into record/data store entity, you can add and set datetime field value to null before that node as well so that if value is not proper it doesnt get saved.

RE: Reset value in datetimefield

Stefan Helzle — Fri, 15 May 2026 08:41:31 GMT

How do you manage the overall interface state? Is this the only information you might need to reset somehow?

In a dynamic interface where I switch between larger interface sections, I use additional saveInto statements in buttons to control the state of the data.

RE: Reset value in datetimefield

Shubham Aware — Fri, 15 May 2026 05:10:11 GMT

Use a!save(local!myDateTimeVar, null()) in the Cancel action to clear the value explicitly, because a!dateTimeField() itself may keep the partial value.

RE: Issue with Browser Tab Title Displaying Process Name

Mike Schmitt — Mon, 04 May 2026 19:48:48 GMT

Did configuring "task display name" change it at all for you?

Issue with Browser Tab Title Displaying Process Name

glaralandin — Fri, 01 May 2026 07:25:17 GMT

Hi team!

I’m running into an issue with how navigation names appear in the browser tab—the tab is currently displaying the process name.

Has anyone dealt with this before? I came across some older posts (3–4 years ago) describing the same issue, but I’m wondering if there have been any updates or new approaches since then.

Any pointers or examples would be greatly appreciated. Thanks!

RE: Issue with Browser Tab Title Displaying Process Name

glaralandin — Sun, 03 May 2026 23:20:36 GMT

Thanks!

RE: Issue with Browser Tab Title Displaying Process Name

glaralandin — Sun, 03 May 2026 23:20:18 GMT

I thought the same. Some of the posts I've read are from 4 yrs ago and older. My version is 26.3

RE: Issue with Browser Tab Title Displaying Process Name

Mike Schmitt — Fri, 01 May 2026 15:06:32 GMT

This is an old bug but I thought it'd been fixed by now. What version are you using?

RE: Issue with Browser Tab Title Displaying Process Name

Harsha Sharma — Fri, 01 May 2026 09:30:47 GMT

Configure the 'Process Display Name' and 'Task Display Name' so instead of process name expected title can be shown on the browser tab.

RE: a!booleanCheckboxField() – choiceLabel alignment issue

Mike Schmitt — Thu, 30 Apr 2026 13:42:00 GMT

Cool, thanks for verifying. Go ahead and give a "verify" to me and/or Shubham Aware though, we crave those Community Brownie Points 😅

a!booleanCheckboxField() – choiceLabel alignment issue

Patrick Ludewig — Thu, 30 Apr 2026 08:00:17 GMT

I’m quite new to Appian and noticed an alignment issue within one of my interfaces. I wanted to ask whether this can be fixed or if it’s a known issue with this function.

The alignment between the text and the checkbox seems a little off (I’m seeing the same issue with a!toggleField() as well), and I haven’t been able to fix it myself.

Does anyone know of a workaround for this, or is this a known bug?

RE: a!booleanCheckboxField() – choiceLabel alignment issue

Patrick Ludewig — Thu, 30 Apr 2026 13:30:29 GMT

The issue was caused by a custom font used in this environment. We changed the font to the standard “Open Sans,” and all text now aligns correctly. Thank you all for the help and input.

RE: a!booleanCheckboxField() – choiceLabel alignment issue

Patrick Ludewig — Thu, 30 Apr 2026 13:15:53 GMT

Mike Schmitt

Thank you for your input and comparison. I think we are using a custom font, as that is the only difference I could imagine between your setup and Shubham’s. I’ll check this internally and also compare it with other colleagues.

RE: a!booleanCheckboxField() – choiceLabel alignment issue

Mike Schmitt — Thu, 30 Apr 2026 13:06:52 GMT

this is Edge side-by-side with Chrome, both set to zoom at 100%, aligned so the components line up exactly, with a box drawn to allow easy comparison of the margins above/below the words in the checkbox choices relatve to the checkbox borders themselves.

Patrick Ludewig , does your site have any custom fonts configured, etc? That's the only thing I can think of (beyond browser-level settings that I don't really fathom) which could be having any effect on the rendering you're seeing.

RE: a!booleanCheckboxField() – choiceLabel alignment issue

Patrick Ludewig — Thu, 30 Apr 2026 12:59:50 GMT

Shubham Aware What OS and Browser are you using?

RE: a!booleanCheckboxField() – choiceLabel alignment issue

Mike Schmitt — Thu, 30 Apr 2026 12:59:46 GMT

Checking in with my confirmation that it seems to behave as we should expect:

(this is in Chrome / windows 11)

{
  a!booleanCheckboxField(
    choiceLabel: "Choice 1"
  ),
  a!booleanCheckboxField(
    choiceLabel: "Choice 2"
  ),
  a!booleanCheckboxField(
    choiceLabel: "Choice 3"
  ),
  a!booleanCheckboxField(
    choiceLabel: "Choice 4"
  ),
  a!booleanCheckboxField(
    choiceLabel: "Choice 5"
  )
}

RE: a!booleanCheckboxField() – choiceLabel alignment issue

Shubham Aware — Thu, 30 Apr 2026 10:26:35 GMT

This doesn’t seem to be expected behavior. It’s not reproducible on my end across any Appian 26.3 instances. I’d recommend raising a support ticket with Appian to get this investigated further.