Database View provides greater flexibility to make fields mandatory based on an organization's data-entry requirements. RE NXT needs this same level of configurable control.

Every organization has different business rules and data standards. RE NXT administrators should be able to select from a broad range of fields and determine which ones users must complete. For example, one organization may require Fund ID, Appeal ID, Campaign ID, or GL Post Date, while another may have entirely different requirements.

This is particularly important from a data governance and data quality perspective. If information is required by an organization's processes, users should not be able to complete or save the gift without providing it.

Ideally, RE NXT would provide a centralized configuration where administrators can make fields:

Required
Optional
Required under specific conditions or for certain gift types

Giving organizations this flexibility would help prevent incomplete data, enforce consistent data-entry standards, and provide the controls we need as more workflows move from Database View to RE NXT.