Classifications

classifications are used to classify/categorise any record in servicely including tickets (i e work extended tables) such as ones in the itsm processes the capability supports multi level classification/categorisation level and is used through a field with type of “classification” with its option configured in the “classification” table usage in the out of box configuration, there is a field named “classification” with type of “classification”, available on the work table this means that the work table or any of the work extended tables such as incident or hr case, can already make use of the classification capability without needing a custom field for it you can however make other fields of field type of “classification”, that can use separate records for each table few things to note usually done as part of a first phase servicely implementation and then as part of continual improvement activities, the classification options will need to be configured (refer to section below) first before you can make use of them in the respective classification fields classifications allow for theoretically unlimited levels with its parent and child hierarchy for example, you can configure “hardware” top level classification and then a second level (its child) as “failure” and then something else as “failure”'s third level, and so on any of the classification options can be made either selectable or non selectable this means, if you have “hardware” top level classification and its second level “failure” both made available, you will be able to select any of them in the classification field note that selecting “hardware > failure” in this example means you are selecting “failure” classification option if you make a parent, such as “hardware” not selectable, the child “failure” will still be available we strongly recommend that whenever possible, that you do not overcomplicate with too many options and too many level of classifications, as it will reduce usability/user friendliness with your agents that need to use this capability configuration add/update classification option navigate to organization > classification > classifications there you’ll see a list of classifications that have been configured you can then either go to an existing one to edit it, or create a new one by clicking on the new button on a classification form, the following are the fields to populate/be aware of, with examples true left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type screenshot below shows an example of such classification record if the parent hardware classification had been set to be selectable, then the options in the incident table’s classification field can look like the below continuing with the example above, you may decide that it makes sense for the agents working on incidents to always pick the lowest level classification in that case, you can set hardware’s classification to not be selectable that will result in the classification field looking like the below instead we recommend that you do not delete classification records that you do not need anymore making them non selectable instead will keep the data reference to the old classification intact as well as maintain your data report integrity role required roles available for classifications administration true left unhandled content type left unhandled content type left unhandled content type left unhandled content type