How can Hantera apps share the same business values across models?
System and named enum sources let apps reuse one keyed value set across different models, so customer types, return reasons, classifications, and similar concepts keep the same identity everywhere they appear.
Models can remain independent while using the same controlled values. A return reason, classification, customer type, or carrier service can be defined once and referenced wherever it belongs.
This avoids translation layers that grow when each domain keeps its own list for the same business concept.