Opening the Litmus Production Record Internal Event Configurator

To create an event monitoring configuration inside Litmus Production Record Database using the Litmus Production Record Internal Event Configurator, the user will create the event monitoring configuration inside the configurators sheets first before uploading it directly to the database.

As the solutions is designed to ideally publish the tag configuration directly to Litmus Production Record Database, it is recommended to make sure that access to the SQL Server running the LE_ProductionRecord database exists.

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.

For cases where users may not have direct connection to the SQL Server, the solution also has an offline mode. In the offline mode the solution will create a SQL file, which can be executed later through for example SQL Management Studio.

Note: The offline options is only recommended for experienced users. Why this is the case will be highlighted in the respective chapters of this guide.

When opening the file Litmus_Production_Record_Internal_Event_Configurator_V1.0.0..xlsm, the user is typically asked to enable VBA macros.

Some organizations do by default not trust any custom code for MS Excel. Therefore the solution might display.

In this case, close the solution and navigate to the files location and open its properties window. In the General tab check the Unblock checkbox and apply the change.

Now open the file again and it should allow the user to enable the use of macros.

The solution will start the user always in the Instructions sheet.

In case a SQL Server is defined in the sheet CONFIGURATIONS

the application can show a prompt

to request a SQL Authenticated Login user and password. To verify if the SQL Server is reachable and the database LE_ProductionRecord does exist.