Creating a data model using the Litmus Production Record Data Model Configurator

The solution Litmus Production Record Data Model Configurator is designed to provide a guided experience to assist the user with where to start and where to go.

The sheet Instructions provides a basic workflow, showing which sheets to go first and how to progress.

It also does provide a link to this documentation.

Users can factory reset the Configurator tool, for example if you want to create a new data model on a different SQL-Server, with the Reset Configurator button in the sheet Instructions.

Most sheets have a dedicated Clear Sheet button

The sheets NodeStructure

and Items

both have a section designed to provide in-sheet assistance and also show examples to help users to fill in the sheet.

The sheet NodeOptions shows some examples of what the hierarchy concept means with regards to a Litmus Production Record data model.

This can be used together with the chapter Core Concept behind recording production record data via data model to define the base structure of your data model.

Most sheets provide a help ? button in the right upper corner of the sheet.

This button opens a help window with three tabs.

The first tab gives a high level How to guide

The second tab shows which Characters are allowed (green) and not allowed (red) when setting up a Node name, Level name or Item name

This is necessary, as certain ASCII characters can cause the Transact-SQL used by the Litmus Production Record Database to not work correctly, especially when retrieving data.

The third tab shows which Characters are allowed (green) and not allowed (red) when setting up a Node Descriptions, Level Descriptions or Item Descriptions.

This is necessary, as certain ASCII characters can cause the Transact-SQL used by the Litmus Production Record Database to not work correctly. As descriptions are only contextual data and only stored in the configuration section of the database and not the live data, they are not available to be specifically queried against and are therefore allowing some additional ASCII characters to be used.