support this new feature

-KEE.S

required is to be mandatory regardless.

It will be helpful

agreed, I had same scenario and wanted this option.

One advantage of this additional configuration is REQUIRED field configuration should have same behavior throughout system, system should validate data even Administrator role user is editing forms. But same concept of allow override can be used with other custom field level-configurations.

If "Allow Override by Administrators" setting is unchecked, system should apply same validation for all users including Administrators.

Suggestion is to add new configuration during creation or defining new custom field under contacts or members "Allow Override by Administrators" as check box. When this is checked it means Administrators role users can override other custom field settings like "REQUIRED" etc.

Currently when a custom field is marked as "REQUIRED" system don't apply mandatory field validation when administrators are creating contact/member or editing their existing data.

This will help in adding more control in current system and ability to keep consistent data according to configured workflow.

Thanks

Suggestion- If there was a real demand by users to override required field inputs by Administrators, then Wild Apricot should have given additional configuration setting when defining custom field which should say "Allow Override by Administrators" with Required check.

This can dynamically handle both scenarios, concept of REQUIRED field and special cases where administrators want to override required field validation check.

REQUIRED field configuration should have same behavior throughout system, system should validate data even Administrator role user is editing forms.

Otherwise rename this field as "required for online-forms only" OR "conditionally required" as it is actually not mandatory field and data consistency compromises due to this issue, we have multiple administrators and have kept few custom fields required for each member form based on our organization workflow, but after few months what we found was various members were entered manually by Administrators with blank values in required field.

Globally in application systems the concept of "REQUIRED" means application will automatically validate data entry to make sure data is present in field/input marked as required.

Got it

Evgeny: This assumes that you have a large and frequently changing membership database where the administrator or bundle administrator is doing the changes and are thereby totally familiar with the system. Our system is very limited, so both I, the primary administrator, and at least one bundle administrator have failed to enter one of the most important fields in the record for us, primarily because it is a custom field and resides at the end of the primary contact info. I did make another suggestion to allow us to add Custom Fields that can be inherited from the bundle administrator as they are the same for every record in the bundle.

This was made on purpose and by request of our users. The idea is that user with admin privileges know what they do.