3. Defining the Hierarchy Levels

the purpose of the sheet nodestructure is to define the hierarchy level names as well as their relation to each other the which columns are visible does depend on the selection made in the sheet nodeoptions no hierarchy levels in this example, the user has defined that they do not want hierarchy levels which will display no columns in the sheet nodestructure subsequently, the user can skip this sheet and go straight to the sheet items defined number of hierarchy levels in this example, the user has defined, that they want to have 2 hierarchy levels this will display 4 columns (2 columns used to define the hierarchy level name + 2 columns to provide an optional description for each hierarchy level) in the sheet nodestructure define the name of the first hierarchy level to define the hierarchy level structure, the user always starts with the highest hierarchy level the first hierarchy level is called level 1, as while items can be linked directly to the node name, this is considered hierarchy level 0 the name of a hierarchy level 1 is configured in the column labeled level1 name the configurator will verify the level name for invalid ascii characters to learn more about which ascii characters are allowed, review the section restrictions on ascii characters allowed to be used the configurator also validates the length of the string invalid ascii characters if an invalid character is found, a prompt is shown to the user invalid characters are marked in red as spaces are not a visible character, they can't be marked in red, so the user can make use of the comment added to the cell as well invalid string length to allow for the most efficient storage of the configuration as well as practicality when using a level name in a query, the maximum length of a level name can not exceed 50 characters if a level name is longer 50 characters, the user will be prompted note names of levels which exceed the 50 character limit, will by default be trimmed to 50 characters if no action is taken by the user define the name of subsequent hierarchy levels this is only required, if a hierarchy level has a sub sequent hierarchy level note not every hierarchy level needs to have a subsequent hierarchy level defined as shown by station c, which has no further hierarchy levels below it if the user has to define sub sequent hierarchy levels and allowed, shown by the respective columns being visible labeled level x name , the user continues the configuration by repeating the values entered in the column level 1 name into the next row important do not leave blank rows between entries a blank row will be seen as the end of the configuration and the configurator will not process any entry past the blank row tip users can copy & paste cell content as well as make use of the ms excel autocomplete feature, where it does try to recognize what the user may want to enter as a repeat the user then defines the name of the subsequent hierarchy level in the column labeled with the respective name in this example the column labeled level2 name is used to define the name of the subsequent hierarchy level the configurator will verify the level name for invalid ascii characters to learn more about which ascii characters are allowed, review the section restrictions on ascii characters allowed to be used this is repeated until all subsequent hierarchy levels are defined repeat for further subsequent hierarchy levels a data model used by litmus production record database can have up to five hierarchy levels to define such a model, the user does simply repeat the steps shown in the previous two sections but expanding it column by column the end result is a layout which looks like a step repeat for additional hierarchy levels if more than one hierarchy level name is to be defined, repeat the steps from the previous three sections until all hierarchy levels are and their relation are defined the number of repeats and hierarchy levels entirely depends on the complexity and how many hierarchy levels are required the sheet nodestructure provides an example of a five level deep hierarchy as shown in the example above, not every hierarchy level needs to have sub sequent hierarchy levels defined according to the max level it is entirely acceptable, that some hierarchy levels have no further or less sub sequent hierarchy levels as shown by the last row, where the hierarchy ends at hierarchy level 3 instead of hierarchy level 5 a final configuration could look like this level description (optional) users are able to provide a description for a hierarchy level to provide some context for colleagues about the purpose of the level and what it is used for the description only needs to be provided for the first instance of a hierarchy level name the configurator will verify the level description for invalid ascii characters to learn more about which ascii characters are allowed, review the section restrictions on ascii characters allowed to be used the configurator also validates the length of the string invalid ascii characters if an invalid character is found, a prompt is shown to the user invalid characters are marked in red invalid string length to allow for the most efficient storage the maximum length of a level description can not exceed 256 characters if a level description is longer 256 characters, the user will be prompted note descriptions for levels which exceed the 256 character limit, will by default be trimmed to 256 characters if no action is taken by the user