To learn more about best practices when building Case Databases and Data Views, download the attached complete Module building: Best practices guide (please scroll to the bottom of this article) or read through selected best practices below.
Case Databases and Data Views
Setup
| Case Databases initial setup | Consider creating the Module first to ensure all values can be correctly mapped into fields of the case database. |
| Clearly indicate if a Case Database Action Node is reading out of a Database or writing values into the Database in the Node’s title. | |
| Use an idiomatic name for your Case Databases. If you are collecting information on clients, title your Case Database “Client Details”. | |
| Data Views initial setup | Use an idiomatic name for your Data Views, especially if you create several Data Views intended for different audiences to clearly distinguish between them. |
Configuration
| Case Databases configuration | Ensure that all or almost all values are clearly defined and have distinct field names. This will also help in selecting the correct type for values. |
| Use emojis in field names and short field names if the Service contains Data Views. Emojis and field names can be added or edited after your initial configuration. | |
| If you are using Data Views to display the status of records in your Case Database add the Status as one of the first fields in the Case Database. | |
| Collect end-user emails if the Service includes a Data View that needs to be filtered according to the end-user accessing the Data View. | |
| Data Views configuration | Only select the fields that are required in a Data View and deselect system values like “Last update” or “ID” that are not required. |