HP SM 9.40 | customizing Affected Services, Category, Sub-Category and Area



In interaction and incident logging template, i am planning to use the following scenario, I require help in knowing the steps to be followed in doing so. I want Remap & rename the existing HP SM 9.40 fields as following



Existing                                               New


Affected services                            Category

Category                                             Type

Sub-category                                    Item

Area                                                      Summary



once above changes are done, i am also trying to co-relate all the four, i.e. affected services, category, sub-category and area in such way that if we select one of the option inside "affected services", the rest of the fields are appropriately populated, i.e. for example, inside "affected service", if we select one option say "applications", accordingly "category" will get options related to Applications only, and same is for "Sub-Category" and "Area"



hope the above requirements are understood well, please look into and suggest.



thanks and regards

hemant vaswani

  • Hi Hemant,


    This sounds pretty much like the behavior of Category>Subcategory>Area links behavior.


    If i understand your requirement well, you will fill the Affected Service (Category), then, when filling Type, you will get the results depending on the Category selected and the same with the other fields depending on the previous data.


    Requirements for the customization:

    1. The four tables with the Category, Type, Item and Summary information.

    2. four lines in the probsummary link record referencing the four new fields (Category, Type, Item and Summary)


    The configuration may be as follow:

    1. In the format:

    2. In the link:

    a. Four lines for each field in the format:

    b. for Category line:

    c. for type field:

    d. for item field:

    e. for Summary field:


    So, based on those links, my table structure may be as:


    The steps above show a general idea of how to do queries in links to bring information based on data filled in the format, so $query variable will contain the criteria for the select in the "File (To/Target)" table.


    For instance, if the user fill the category field with "Category1" and press the fill button in Type, the query ran in Types table will be:

    Select Name from Types where Category="Category1"

    When the Type field is filled, if users press fill in Items, the query ran will be:

    Select Name from Items where Category="Category1" and Type="Type1"

    When the user fills the Summaries field, the query will be:

    Select Name from Summaries where Category="Category1" and Type="Type1" and Item="Item1"


    What i would not suggest is to change the fields dbdict mapping but to create new fields. This is because probably this kind of OOB fields are used for integrations and may cause problems in the future if they are not present.


    I hope this information helps you to make the customization, use it also with the OOB link record for more details.



  • hi,


    appreciate the efforts taken to respond, i will chekc the details and revert to you with queries.



    Thanks and Regards

    Hemant Vaswani

Reply Children
No Data