In other words, don’t think about the UI you want, but about the outcome you want to see.
When selecting field types, you have to pick the right one depending on your case:
- Data reference: Use this field when you need to select a record from a Data Object that is outside the Case. For example, in a Case Type for booking medical appointments, to reference the facility where the appointment is made.
- Case reference: Use this field when you want to reuse data from the selected Case. For example, A user selects from a list of service Cases from the Service Case Type.
- Query: Use this field for read-only access to information that is external to the Case. The Query Field Type allows parameters to query for specific data. For example, return the next appointment for a medical professional or the list of all appointments they have in a given time frame.
- Embedded Data: Use this field when you need to collect information from user into a Case. For example, capture information about the emergency contact for a patient, and then store the details about the contact in the patient record.
As far as Case Reference and Data Reference fields, using Autocomplete / Combo-box is ideal when users know the item they’re searching for by name and need quick, efficient selection from large datasets.
Use Tables where users need to view and compare multiple data points across records, or when working with complex datasets requiring analysis.
Use Simple Tables for small, straightforward lists (typically 5-6 items or fewer) where users don’t require search, filtering, or sorting capabilities.
Use Advanced Search and Select for scenarios involving sensitive data or when you need to minimize data exposure until specific search criteria are met.
Use Checkbox Group for multi-select scenarios with a limited number of options (7 or fewer) that users can quickly review and select.
Use Selectable Cards for visually rich data presentations where you have a limited number of options and want to provide an engaging, scannable interface. For example, customer-facing experiences where images can be displayed on cards.
Use Query and Reverse References for visually representing data that is related to the current object, however, there is no direct-stored reference.
When selecting a display option, consider these key factors:
- Data volume: How many items will users typically encounter?
- User knowledge: Do users know what they’re looking for by name?
- Context requirements: Do users need additional information to make decisions?
- Security considerations: Should data be hidden until specifically requested?
- Interaction patterns: Single-select vs. multi-select requirements?
- Users & device: Is it a customer-facing experience? Are they on mobile?
This framework should help guide decision-making when configuring Case Reference and Data Reference display options in Constellation applications.