Solutions
...
Litmus Companion Solutions for...
Litmus Production Record Tag C...

Creating a tag configuration using the Litmus Production Record Tag Configurator

7min

The solution Litmus Production Record Tag 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.

Document image


It also does provide a link to this documentation.

Document image


Factory Reset the Configurator

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

Document image


Reset an individual sheet

Most sheets have a dedicated Clear Sheet button

Document image


In Tool guides and help

The sheets Tags

Document image


and Items

Document image


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

Help Button

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

Document image


This button opens a help window with three tabs.

Document image


The first tab gives a high level How to guide

Document image


Restrictions on ASCII characters allowed to be used

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

Document image


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 an Item Descriptions or an Initial Value if it is has the Value Type isString.

Document image


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.