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; } } }

Organization settings to mandate certain questions in all forms?

mattkramer

Hello,

I have a few Survey123 form builders who publish forms to our Enterprise Portal, and I was wondering what tools are available to help us standardize some of the forms being built by these users. Specifically, I was hoping to mandate the inclusion of certain fields, such as project_number to help us track how forms are being used.

We could push out organization templates with this question already added in, but I am worried about our users removing it and not letting us know.

Encontre mais publicações marcadas com

Accepted answers

jcarlson

Unfortunately, there's no way to do that. Forms can be made that tie into any existing feature service, so you'd essentially be requiring a "project_number" field to be included on every layer in your organization, not just the forms.

I think it would be fine to set an organizational standard and create an audit process, but I don't think you're going to find a built-in setting to do this for you.

All comments

jcarlson

I think it would be fine to set an organizational standard and create an audit process, but I don't think you're going to find a built-in setting to do this for you.

dougbrowning

You can set up Organization templates that may work for you. See here https://community.esri.com/t5/arcgis-survey123-blog/understanding-survey123-organization-templates/ba-p/1237503

abureaux

Second vote for organizational templates.

You asked: "...what tools are available to help us standardize some of the forms being built...". The answer is 100% organizational templates. For example, I have multiple templates set up (e.g., with geopoint, without geopoint, etc.), and all with default/mandatory questions, formatting, and metadata calculations. This ensures a minimum quality of work, and that all forms fit nicely into my automation processes with almost zero configuration (aside from picking which survey triggers the flow, it's all standardized).

Furthermore, I would suggest you get a reviewer. "...a few Survey123 form builders who publish forms to our Enterprise Portal...". This sounds like a nightmare that will only get worse in time. Especially if they are forgetting to add something as fundamental as a project number. For example, I have mandated that all surveys need to be reviewed/published by a single service account rather than all "willy-nilly". You will catch a LOT of little mistakes this way.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.