Configure Ticket Classification using Neurons Platform

role administrators minimum version 2024 2 ivanti plans to retire the option to configure ticket classification using the neurons platform ui in an upcoming release of ivanti neurons for itsm, likely version 2025 4 starting with version 2025 3, ticket classification will be configured exclusively through the central itsm ai configuration hub docid\ drkkmsioksnp0l7l80d1d when you enable the ticket classification feature in , the application will automatically categorize the field recommendations from ivanti neurons for support tickets ticket classification functionality requires subscription to ivanti neurons for healing currently, this feature is available in the incident business object only you can configure the ticket classification feature on your tenant by raising a service request to the ivanti operations team enable the global constant log in to with the administrator user role select configure application to go to the configuration console select build > global constants to open the global constants window set the enableticketclassification value to true select save enable the layout to use ticket classification feature for a user role from the configuration console, select build > business objects > incident to open the incident business object select the layouts tab the application displays a list of layouts determine the layout to configure the ticket classification open the layout for example, select incidentlayout servicedesk for the role select formview or formedit to open the form view editor select enable ticket classification select edit ticket classification settings the application displays the configure ticket classification for incident "formview" layout dialog box modify the below field values for recommended field mapping triggered field input to neurons api to trigger the recommendations in 2021 3 release, we must configure only subject as the triggered field because the machine learning (ml) and artificial intelligence (ai) engine is trained based on the subject field source fields fields from ivanti neurons target fields (ivanti neurons for itsm) fields in to map the recommended field values you can map service , category and recommendedcategory fields for more information about target fields mapping, see mapping target fields docid 2psniuy3n sydmxflwwv1 to avail default mappings for incidentlayout servicedesk and incident layout 0 as shown in the above figure, raise a service request to the ivanti operations team select the add icon to add more fields select save mapping target fields consider the following points for mapping source fields to target fields if source fields " service and category " are mapped to target fields " category and service " and target fields " recommendedcategory and recommendedservice " are not mapped, then the application will automatically fill the recommendations in the form however, the application will not display the "ivanti neurons ai recommendations applied" label and the apply ivanti neurons ai recommendations button recommendedcategory and, recommendedservice fields mapping determines the visibility of the button and label if source fields " category and service " are mapped to target fields " recommendedcategory and recommendedservice " and not to target fields " category and service ", then you must select apply ivanti neurons ai recommendations to fill the recommendations in the form if source fields " category and service " are mapped to both target fields " category , service , recommendedcategory and recommendedservice ", the application will automatically fill the recommendations in the form and displays the label if you override the recommendations, then application will display the apply ivanti neurons ai recommendations button and you must select it to restore the recommendations you should map the source fields to target fields as follows service > service category > category subcategory > subcategory category > recommendedcategory service > recommendedservice subcategory > recommendedsubcategory model probability > accuracy any changes in the above mapping will result in a failure of the ticket classification feature for example, you should not map source fields " category " to target fields " service " or category to recommendedservice when mapping ensure to add service field first and then the category field since category is dependent on service generating the training data you can generate the training data as a csv file to train the ml and ai engine log in to open the incident workspace select more >form actions > export to export the csv file make sure to export the field values such as subject and at least one of the fields ( category and service ) to train the ml and ai engine if you provide only one type of field value (for example, only subject ) in the training data, then the ml and ai engine will only predict that field if a service / category field value in ivanti neurons is deprecated, updated, or no longer used, you must train and deploy a new model without it if you export actualservice and actualcategory fields, you must rename them to service and category to match the field prediction related topics javascript\ void(0);