Custom Administrator Role user permissions are very important need for organizations have multiple administrators or bundle administrators to manage membership data.
Permissions for each feature set would be ideal as in already present other applications, like
- Insert or Add new data
- Change Data or Edit
- Delete data
- View report
- View Audit Log of any entry
- Export Data
these permissions should be allowed to configured for each screen like Contacts, Members, Donation, Payment, Invoices, Membership Levels for through security access control mechanism.
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.
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.
How are you going to use QR codes on membership cards? Do you expect some additional functionality in WA, which will be able to read and process these codes?
44 votesTeam Payments responded
Due to priorities shift we had to put this issue on hold.
We’ll post any updates as we have them
Oleg, Product Owner @ Payments crew
113 votesEvgeny Zaritovskiy responded
Old design proposal, not working on it yet and can be changed if we start working on it – https://drive.google.com/file/d/0B0f9kMyQqlBsZ3FQOWRiMERRNkk/view?usp=sharing
After initial analysis we decided to remove this feature from 2017 plans. Right now we don’t have clear understanding when this feature will be taken into development.
I had to implement similar scenario where we we have to identify type of account donation has to be allocated to (for non-members). So I had created custom donation field of type list for this case.
Then later found that I'm unable to search or add saved-search criteria based on this custom donation field of type list.
Is there a way (except for exporting) I can get my custom donation fields to search, let me know.
thanks for help in advance