4. Verifying the data model and uploading it

to upload a tag configuration to litmus production record database or, if in offline mode, create a sql file, the configurator will always verify the configuration done by the user first to make sure that on a technical level all values are correctly formatted note the configurator will not verify if the event monitoring configuration makes sense or configured correctly according to what the user wanted to define verifying the configuration the configurator will always verify the configuration first before publishing users can run the verification also as a stand alone operation without publishing the data model using the verify configuration button in online modus, the user can be prompted multiple times, throughout the verification, to provide the sql authenticated login user name and password verify the configuration in the sheet event and trigger definition the verification process for the event monitoring configurations is very complex and is conducted for each sheet individually the first sheet verified is the sheet event and trigger definition , as it is the basis for the sheet event item definition test if data model node names are defined the verification process will verify in the sheets event and trigger definition that data model node names are defined in the column labeled production record data model node name in the case that no data model node names are found, a prompt is shown to the user in case a specific row has no data model name set, a prompt is shown to the user as data model node names are required, the verification will be stopped test if event names are defined the verification process will verify in the sheets event and trigger definition that event names are defined in the column labeled event name in the case that no event names are found, a prompt is shown to the user in case a specific row has no event name set, a prompt is shown to the user as event names are required, the verification will be stopped test if trigger condition names are defined the verification process will verify in the sheets event and trigger definition that trigger condition names are defined in the column labeled trigger condition name in the case that no trigger condition names are found, a prompt is shown to the user in case a specific row has no trigger condition name set, a prompt is shown to the user as trigger condition names are required, the verification will be stopped test if trigger tags are defined the verification process will verify in the sheets event and trigger definition that trigger tags are defined in the column labeled trigger tag in the case that no trigger tags are found, a prompt is shown to the user in case a specific row has no trigger tag set, a prompt is shown to the user as trigger tags are required, the verification will be stopped test if trigger conditions are defined the verification process will verify in the sheets event and trigger definition that trigger conditions are defined in the column labeled trigger condition in the case that no trigger conditions are found, a prompt is shown to the user in case a specific row has no trigger condition set, a prompt is shown to the user as trigger conditions are required, the verification will be stopped test for duplicate combination of data model name, event name and trigger condition name the verification process will verify in the sheets event and trigger definition if combinations of data model name, event name and trigger condition name are unique while it is possible to reuse a trigger condition name for different events a specific trigger condition name has to be unique in its combination with a specific event name and data model node name if the configurator does detect, that a specific combination has already be used, the user is prompted as combinations of data model name, event name and trigger condition name have to be unique, the verification will be stopped the duplicate row will have the three columns production record data model node name , event name and trigger condition name be marked in red this allows the user to find the duplicate entry and correct it test for invalid ascii characters the verification process will verify in the sheets event and trigger definition if any entry has invalid ascii characters to learn more about which ascii characters are allowed, review the section restrictions on ascii characters allowed to be used in the case that invalid characters are found, a prompt is shown to the user to inform them about the fact and request from the user to select the next action users can either stop the verification using the no option or replace all invalid characters with and underscore " " note in offline mode, additional columns (trigger tag) are verified for invalid ascii characters if invalid characters are found in offline mode, the user will be inform them about the fact and request from the user to select the next action test for long strings the verification process will verify in the sheets event and trigger definition the length of specific strings if they exceed the allowed maximum length sheet string maximum length event and trigger definition event name 50 event and trigger definition event description 256 event and trigger definition trigger condition name 50 if a long string is found, the user is prompted the user can define if they want to auto trim the strings using the yes option or stop the verification using the no option verify the configuration in the sheet event item definition the verification process for the event monitoring configurations is very complex and is conducted for each sheet individually after the first sheet event and trigger definition has been verified with no errors, the sheet event item definition is verified test if trigger condition names are defined the verification process will verify in the sheets event item definition that trigger condition names are defined in the column labeled trigger condition name in the case that no trigger condition names are found, a prompt is shown to the user in case a specific row has no trigger condition name set, a prompt is shown to the user as trigger condition names are required, the verification will be stopped test if hierarchy level and items are defined the verification process will verify in the sheets event item definition that data model items and their hierarchy level are defined in the column labeled hierarchy level and item in the case that no data model items are found, a prompt is shown to the user in case a specific row has no data model item set, a prompt is shown to the user as data model items are required, the verification will be stopped test if sources for item values are defined the verification process will verify in the sheets event item definition that sources for the item values are defined in the column labeled source of item value in the case that no sources for item values are found, a prompt is shown to the user in case a specific row has no source for the item value set, a prompt is shown to the user as a source for the item value is required, the verification will be stopped test if items are set to be an identifier or not the verification process will verify in the sheets event item definition that each item has a setting for their identifier status in the column labeled isidentifier in the case that no item has a setting for its identifier status, a prompt is shown to the user in case a specific row has no setting for the identifier status, a prompt is shown to the user as it is required to define if an item is an identifier or not, the verification will be stopped test if items have a setting for when it is recorded the verification process will verify in the sheets event item definition that each item has a setting for when it will be collected in the column labeled is the item recorded for the newevent or the previousevent in the case that no setting for when an item is to be collected has been found, a prompt is shown to the user in case a specific row has no setting for when the item is to be collected, a prompt is shown to the user the user can define if they want to set the default value of newevent or in case it is a calculation previousvalue using the yes option or stop the verification using the no option test if an item has a value set if it is not the trigger time the verification process will verify in the sheets event item definition that each item has either a fixed value if the source is isconstant a tag item defined in litmus production record database if the source is valeufromtag or iscalcualtion in the column labeled item value / calculation in case a specific row has no value set, a prompt is shown to the user as it is required to know where the value is taken from for an item, the verification will be stopped test if an item set as calculation has a calculation type set the verification process will verify in the sheets event item definition that each item which has a source set as iscalcualtion has a calculation type set in the column labeled type of calculation in case a specific row for an item which is a calculation has no calculation type set, a prompt is shown to the user as it is required to have the type of the calculation set, the verification will be stopped test if an item set as calculation have a setting for which item is used to get the start time for the calculation duration the verification process will verify in the sheets event item definition that each item which has a source set as iscalcualtion has another item set which is used to get the start time of the duration required by the calculation set in the column labeled item which provides the start of the time frame for a calculation in case a specific row for an item which is a calculation has no setting for this column, a prompt is shown to the user as it is required to have an item set to provide the start time for the calculation set, the verification will be stopped test if an item set as calculation have a setting for which item is used to get the end time for the calculation duration the verification process will verify in the sheets event item definition that each item which has a source set as iscalcualtion has another item set which is used to get the end time of the duration required by the calculation set in the column labeled item which provides the end of the time frame for a calculation in case a specific row for an item which is a calculation has no setting for this column, a prompt is shown to the user as it is required to have an item set to provide the end time for the calculation set, the verification will be stopped test for invalid ascii characters the verification process will verify in the sheets event item definition if any entry has invalid ascii characters to learn more about which ascii characters are allowed, review the section restrictions on ascii characters allowed to be used in the case that invalid characters are found, a prompt is shown to the user to inform them about the fact and request from the user to select the next action users can either stop the verification using the no option or replace all invalid characters with and underscore " " note in offline mode, additional columns (hierarchy level and item, item which provides the start of the time frame for a calculation, item which provides the end of the time frame for a calculation) are verified for invalid ascii characters if invalid characters are found in offline mode, the user will be inform them about the fact and request from the user to select the next action test for long strings the verification process will verify in the sheets event item definition the length of specific strings if they exceed the allowed maximum length sheet string maximum length event item definition item value / calculation note only if the source is set to isconstant 256 if a long string is found, the user is prompted the user can define if they want to auto trim the strings using the yes option or stop the verification using the no option uploading the tag configuration to litmus production record database to upload the configuration for new internal event monitoring or update an existing event monitoring configuration, the user will need to have a connection to the sql server as well as the databases le productionrecord in place to upload the configuration, the user does press the button verify and upload in online modues, throughout the process, the user can be prompted multiple times, throughout the verification, to provide the sql authenticated login user name and password the configurator will first run the verification process which was explained in the previous section progress is shown by a progress bar only if the verification has found no errors or was stopped, will the configurator upload the configuration to litmus production record database up on completing the upload, the user will be shown a summary of the sql logs to be able to review if all items where correctly added to litmus production record database or if any errors occurred on the sql side this log extract can be saved as a file using the save output to file button the file will be stored in the same folder, where the file litmus production record internal event configurator v1 0 0 xlsm is located the name includes the name of the user as well as the date and time of the upload close sql out put window to finish the configuration creating a sql file in offline mode in offline mode, the user can create a sql file which can be later executed using applications like sql management studio to create a new internal event monitoring or update an existing event monitoring configuration in litmus production record database to create the sql file, the user does press the button verify and upload the configurator will first run the verification process which was explained in the previous section only if the verification has found no errors or was stopped, will the configurator create the content of the file the user is then prompted to select the path where the file is stored as well as being able to modify the file name before saving it the result is a file with the ending " sql " which can be executed using applications like sql server management studio