nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Add Smart Capabilities/Arcade Filters and Form Layout

RPGIS

For some reason it seems to always get skipped over or is incorporated as part of a future release is the smart capabilities of fields. Currently, the smart editor in Web App Builder allows for certain fields to display/toggle editability based on a filter criteria. This capability, in regards to displaying fields, exists in Survey123 and Field Maps Forms. It would be a huge improvement if the ability to intelligently set certain fields to display/toggle editing, either using a SQL expression or Arcade to modify the attribute form behavior. You could also have it set so that there is a single arcade expression that can dictate the form behavior for its entirety.

In addition to that the ability to modify the layout of the attribute form would also be a huge improvement. Modifications such as side by side field, window width, etc.

Vind meer berichten getagd met

Needs Clarification

Status: Needs Clarification

Reacties

DavidSolari

The Field Maps form spec is what Experience Builder and the new JavaScript SDK uses for their editor widgets so I think you're covered there. But it would be great to have more customization over how the forms display in the web clients.

cgillgrass

@RPGIS Web Editor uses the same form that Field Maps uses, so if the capability you're looking for exists in Field Maps, the Web Editor will take advantage of it.

It might be best to break this idea out into a new one focused on improved control over how forms are displayed to web clients, e.g. ability to modify the layout. As it is, that request is going to get lost in this idea.

RPGIS

I probably should have looked up the documentation for that before posting this idea. I had explored and played around with Web Editor but failed to properly understand how the form behavior is setup. I typically see the form behavior configured within the application itself, so this workflow caught me off guard.

The behavior I was also thinking about is having it setup in such a way that a single arcade expression could dictate the behavior of the entire form rather than modifying the behavior every field input.

In regard to the layout of the form itself, it would be nice to be able to configure the field inputs similar to that of PowerApps given that the real estate on various monitors allows for more flexibility.

Regarding this workflow then I think this idea ought to be moved to field maps or perhaps split so that the other idea for the layout itself can persist here.

Doe mee aan het gesprek

Meld je aan om te posten, content te volgen en meer. Nieuw hier? Registreer gratis.