A case database enables you to store values. Those values can later be reused by modules or displayed – in parts or as a whole – in data views. Values can be written into case databases by modules or uploaded from a Microsoft Excel sheet.
Case databases as part of applications and environments
Case databases are part of applications. Therefore, you can only connect action nodes, data views, and case databases that are within the same application.
Also, case databases keep environments separate, like the Test and the Live environment. This means that modules only read from and write to a case database within their environments. For example, you can test your whole application in the Test environment without impacting the Live version of your case database (or versions in customer environments).
💡 When moving a case database to another application, only its configuration is moved. Records are application-specific. As such, they are not moved.
Related topics
- Set up a case database, either by creating a blank one, or by uploading an Excel file.
- Read from a case database: Read into a module either single values, or multiple values as a collection.
- Write to a case database from a module.
- Set up a Data View to display some or all of the data in your case database.
- Delete a case database or move it to another application.