Editor Widget — Make read-only fields look different from editable fields

[Bud]

In an editor widget in Experience Builder:

I have fields that are editable and fields that are uneditable. The uneditable fields are defined that way in the web map form configuration. 

The editable and the uneditable fields look the same in Experience Builder. There's no way to tell what fields are uneditable except to click on the field to see if I get a cursor or not. From a colleague: "The field border even changes to blue when you click a read-only field, just like the editable fields, making it seem like you can edit the read-only field, which is misleading."

Could that functionality be changed so that it's more obvious that the fields are read-only? Such as greying the fields out, but still allowing the text to be selectable.

[JonathanMcD]

If the ExpB you've created is specifically for a task to edit/update fields, why not just hide the fields that are not required as part of your process - alternatively - give the field an alias to match its status.

Also, you could organise the order of fields too.

@Bud 

[ZachBodenner]

Another option would be to add it to the alias when configuring the form. So go into the actual map viewer, access the form, and then for uneditable fields just use the alias "Field Name (not editable". Inelegant, but it does the job.

[Bud]

Thanks for the ideas JonathanMcD and ZachBodenner.

Similar to what you mentioned, I used field groups with "editable" or "read-only" text in the group name.

[ZachBodenner]

Awesome! Also a suggestion I'll offer as a forum MVP:  I notice you've raised a lot of good questions lately that might help out some other users - you might want to submit them as questions first in case others are searching those boards for similar reasons. That way you can mark reply posts as Solutions to help out those searches. If they're not solvable, then the recommendation is to post an Idea and reference the Question post you previously created!