In every app-building journey, one common element is the basic information template associated with each field. This universal component is designed to collect standard details each field necessitates for an optimal build. Careful attention to detail is crucial when filling in this area. The information provided here lays the groundwork for the app, influencing future changes and modifications when referencing field in expressions, reports, exports, workflow ect. When completed with care, this process will greatly streamline any subsequent adjustments made by you or other app builders. Thorough and accurate input today will pave the way for easier updates and enhancements in the future, saving you time and ensuring consistency across your app-building endeavors.
- Label: The label effectively communicates to users what data is being represented in the Field or what data the user needs to enter into the field. This enhances usability by providing a clear context for the presented information.
- Identifier: This value should be consistent with the label. The identifier serves as a unique system ID for referencing a field. It must be distinct for each field, composed solely of alphanumeric characters and must commence with a letter. A minimum length of three characters is required for this identifier.
- Type: This refers to the field type you previously selected on the 'add field' screen. While this typically remains unchangeable, exceptions occur when field types share similar data structures, permitting alteration.
- Description: The description should depict the field's purpose. It might outline its application, intended users, or interaction with other fields. Particularly for expression-based fields, the description might explain the underlying formula. Thus, it serves as a comprehensive guide, enhancing clarity and utility.