User Interface - Recent Threads

RE: Reusable Components Appian

Mike Schmitt — Mon, 13 Jul 2026 17:46:26 GMT

A few of my favorites that I've come up with myself for my own use and use across my project:

a datetime field in a side-by-side with an icon that gives the user a 1-click target to fill with the current date (or datetime)
a file upload field that doubles as a read-only file preview field (predating the recent updates to the file upload field offering the "preview" pop-up) with a rich text icon saving the linked document ID into a local variable to show it within a preview field
a universal preview field which detects the file type (PDF or image file) then opens it in the relevant on-form viewer, if possible, and defaults to a download link if incompatible

Reusable Components Appian

khushim2428 — Mon, 13 Jul 2026 06:25:52 GMT

I'm planning to create some reusable components in Appian. I've already built several, including reusable forms, page headers, message banners, empty state (no data) screens, date and currency formatting utilities, and a few others.

Can anyone suggest additional reusable components, patterns, or expression rules that would be useful across most Appian applications?

AI Icon

aminw4267 — Fri, 10 Jul 2026 16:09:04 GMT

Would it be possible to add an sparkle or AI icon to the icon set in a future release? thanks

RE: AI Icon

khushim2428 — Mon, 13 Jul 2026 06:16:53 GMT

You can still add an AI icon in previous versions, for example:

RE: AI Icon

Stefan Helzle — Sat, 11 Jul 2026 09:33:10 GMT

I typically use the robot icon, or my own image creations.

RE: i want to highlight rows in editable grid with some colors

aminw4267 — Wed, 08 Jul 2026 22:31:04 GMT

Any plans on adding this? both proposed solutions here don't apply to our use case.

i want to highlight rows in editable grid with some colors

gaddam0981 — Wed, 04 Mar 2026 07:56:00 GMT

In our application we are displaying customers list in editable grid based on status we have to highlight the row for example of status = matched then row should be green not matched it should be yellow how can i do please help as per my knowledge we cant give color in editable is there any way .

How to configure custom validations, enable a readonly filed while editing in Grid plus component?

nikitar442261 — Mon, 29 Jun 2026 05:27:19 GMT

I am building POC using a grid plus component, i need help solving below two issues

1. when i try to add custom validations like preparerDueDate<RevieweDueDate it does not validate properly. Even if one row has the validation to true, the message shows on all row for that field.

2. I have a column that cannot be edited when once added, when creating a new record i need the column to be editable. how can i achieve this functionality?

Thanks in Advance.

RE: How to configure custom validations, enable a readonly filed while editing in Grid plus component?

kapilsharma — Tue, 30 Jun 2026 12:26:58 GMT

Hi nikitar442261 ,

I'm not sure this would work or not on Grid Plus
but instead of using this as validation message " fv!row.preparerDueDate < fv!row.reviewerDueDate "
we can utilise using the index when we are storing the values or implementations
local!records[fv!index].preparerDueDate

For the 2nd point, if existing records already have a primary key:

readOnly: not(isnull(fv!row.id))

Meaning:

New row → id = null → Editable
Existing row → id has value → Read Only

This is probably the simplest solution since IDs are assigned only after creation.

RE: How to configure custom validations, enable a readonly filed while editing in Grid plus component?

Zakary Melvin — Mon, 29 Jun 2026 19:05:31 GMT

Can you provide some sample code please?

RE: How to configure custom validations, enable a readonly filed while editing in Grid plus component?

Shubham Aware — Mon, 29 Jun 2026 07:32:25 GMT

In GridPlus, do cross-field validation row-by-row outside columnConfigs, because column-level validators can show the same error across all rows.

For editable-on-create and readonly-after-save, use id = null for new rows and id not null for saved rows, but per-row readonly may require a custom workaround because standard GridPlus column config does not natively support it

How to configure custom validations, enable a readonly filed while editing in Grid plus component?

nikitar442261 — Mon, 29 Jun 2026 05:20:52 GMT

I am building POC using a grid plus component, i need help solving below two issues

1. when i try to add custom validations like preparerDueDate<RevieweDueDate it does not validate properly. Even if one row has the validation to true, the message shows on all row for that field.

2. I have a column that cannot be edited when once added, when creating a new record i need the column to be editable. how can i achieve this functionality?

Thanks in Advance.

getting invalid user exception when there was two users selected in picker user and showing as read only in UI as text

dharanik2600 — Tue, 23 Jun 2026 11:48:07 GMT

In Ui there was user picker field if i choose more than one (max selection is 3 ) and submit request after that in read only the selected users we are showing in summary dashboard there user want first name and last name to be displayed instead user name

Below is the logic i am using to display selected user details in text field

a!textField(
label: "Requested On Behalf:",
labelPosition: "ADJACENT",
value: a!forEach(
items: a!defaultValue(ri!MDSRequest.requestedonBehalf, {}),
expression: if(
a!isNullOrEmpty(fv!item),
{},
if(
a!isNullOrEmpty(touser(fv!item)),
{},
user(touser(fv!item), "firstName") & " " & user(touser(fv!item), "lastName")
)
)
),
readOnly: true,
showWhen: a!isNotNullOrEmpty(ri!MDSRequest.requestedonBehalf)
)
}
),

If i select two means more than one i am getting below error i selected valid users only still getting this error also before upgrade logic worked after version upgrade i am seeing this can any one suggest on this

Error Evaluating UI Expression Expression evaluation error [evaluation ID = ef19e:da996] in rule 'changerequestsection_display' (called by rule 'caserecorddashboard') at function a!forEach [line 137]: Error in a!forEach() expression during iteration 1: Expression evaluation error at function 'user' [line 145]: [InvalidUserException] (APNX-1-4198-000)

RE: getting invalid user exception when there was two users selected in picker user and showing as read only in UI as text

dharanik2600 — Sun, 28 Jun 2026 12:51:11 GMT

Thank you went through code found issue and fixed

RE: getting invalid user exception when there was two users selected in picker user and showing as read only in UI as text

Stefan Helzle — Sun, 28 Jun 2026 08:52:45 GMT

OK. I do not have enough information to continue guessing.

If you would be a junior, I would ask how you store the list of users, are all involved variables list types, what data type do you use, do you do any transformation steps, etc.

RE: getting invalid user exception when there was two users selected in picker user and showing as read only in UI as text

dharanik2600 — Sun, 28 Jun 2026 03:00:32 GMT

Yes I am system admin and other two users whom i added also admins only who were part of my team if i give signle user individually i am not getting this error if i add two users then i can see this error that too observed this after version upgrade only before that there was no issue

RE: getting invalid user exception when there was two users selected in picker user and showing as read only in UI as text

Stefan Helzle — Sat, 27 Jun 2026 05:41:44 GMT

Is your user account an admin account? Could it be that you do not have permission to see that other user?

RE: getting invalid user exception when there was two users selected in picker user and showing as read only in UI as text

dharanik2600 — Fri, 26 Jun 2026 14:12:29 GMT

tried this logic also and getting same error even though i gave valid users two users

RE: getting invalid user exception when there was two users selected in picker user and showing as read only in UI as text

dharanik2600 — Fri, 26 Jun 2026 13:57:14 GMT

two users i added me and other team members we both are active only if i added two users more than one i am getting that error

RE: getting invalid user exception when there was two users selected in picker user and showing as read only in UI as text

Stefan Helzle — Tue, 23 Jun 2026 13:28:49 GMT

Seems like there is an invalid username in your list.

RE: getting invalid user exception when there was two users selected in picker user and showing as read only in UI as text

Shubham Aware — Tue, 23 Jun 2026 12:23:34 GMT

for read-only display, richTextDisplayField is the better practice.

a!richTextDisplayField(
  label: "Requested On Behalf:",
  labelPosition: "ADJACENT",
  value: joinarray(
    a!forEach(
      items: a!defaultValue(ri!MDSRequest.requestedonBehalf, {}),
      expression: if(
        a!isNullOrEmpty(fv!item),
        {},
        user(fv!item, "firstName") & " " & user(fv!item, "lastName")
      )
    ),
    ", "
  ),
  showWhen: a!isNotNullOrEmpty(ri!MDSRequest.requestedonBehalf)
)

RE: Custom Error instead of Appian default Pink Box Error

Shubham Aware — Wed, 17 Jun 2026 13:03:11 GMT

No global way to replace the pink box, and SAIL has no try/catch.

Custom Error instead of Appian default Pink Box Error

thevarunbawa — Tue, 16 Jun 2026 13:58:40 GMT

Whenever a user encounters any error in the UI, Appian shows pink box error. I do not want to show the Appian default pink box error, I want to show a custom error to the user which has no technical details. How can I achieve that in Appian?

RE: Custom Error instead of Appian default Pink Box Error

Harsha Sharma — Wed, 17 Jun 2026 06:10:02 GMT

Replacing the pink box error with custom one is a use case we can't simply or directly implement. Workarounds involve design approaches that reduces the occurrence of such errors is the best and closest implementation we can do to handle these. The better the data and rule design the lower are chances for those pink box errors.

RE: Custom Error instead of Appian default Pink Box Error

Mike Schmitt — Tue, 16 Jun 2026 19:01:37 GMT

Well, there's already the common option (as of the last several years) wherein any error message a user sees will have all technical details replaced with a UUID they're told to report to their administrators, which you can then go and match with the matching error in the error logs. Do you have that enabled?

Otherwise, the only way to prevent pink box errors is... remove the error conditions that cause them. And (other than the above setting) there's no setting or override to show something "custom". I know it can be hard to weed out 100% in a sufficiently large system, but in most cases you should be able to keep them down to very few (and fix the ones that anyone encounters).