Creating an event monitoring configuration using the Litmus Production Record Internal Event Configurator

the solution litmus production record internal event 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 to be able to work, it is required that both the data model for which events are to be monitored as well as the tags which are to be used have both been created in litmus production record database it is recommended to do define them first, as the configurator will be able to retrieve them to assist with the configuration this requirement is also stated in the sheet instructions factory reset the configurator users can factory reset the configurator tool, for example if you want to create a new event configuration on a different sql server, with the reset configurator button in the sheet instructions reset an individual sheet most sheets have a dedicated clear sheet button in tool guides and help the sheets event and trigger definition and event item definition both have a section designed to provide in sheet assistance help button 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 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 event name, node name, level name, device name, tag 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) for descriptions this is necessary, as certain ascii characters can cause the transact sql used by the litmus production record database to not work correctly further are some characters used by applications which use topics such as mqtt or nats for example as wildcards