Example standard header

This example describes a standard Business unit => Ticket category => Ticket type setup on helpdesk.

LISA setup

The inactive field on all the limetypes are optional, it's used as an example later in the Lime admin - Hierarchy Picker config part.

Business unit (businessunit)

Ticket category (helpdeskcategory)

Ticket type (helpdesktype)

Lime admin - Hierarchy Picker

The Ticket type (helpdesktype) is the bottom of the hierarchy in this setup, which means you put that in the "First child" field. After that you just put in Ticket types parent in the next hierarchy property and so on until you reach the top of your hierarchy.

In this example you can also see that we have added an Option Query. It's function is to only show limeobjects which have the inactive field set to false.

Option query example to copy

Please remember to change name and limetype to suit your solution.

{
    "op": "AND",
    "exp": [
        {
            "key": "helpdeskcategory.businessunit.inactive",
            "op": "=",
            "exp": false
        },
        {
            "key": "helpdeskcategory.inactive",
            "op": "=",
            "exp": false
        },
        {
            "key": "inactive",
            "op": "=",
            "exp": false
        }
    ]
}

Lime Admin - Helpdesk card view config

On the cardview for the Ticket (helpdesk) you need to configure the component. This can either be done by replacing a existing field inline or adding it to the header section of a card. In this example we are adding it to the card header.

Notice that the name property have to match the Unique name you entered in the previous step. The style part tells the component how many columns of space it will take up

Properties example to copy

{
    "style": {
        "grid-column": "span 2"
    },
    "name": "Categorize tickets",
    "label": "Categorize",
    "inheritIcon": false,
    "inheritColor": true
}

Result

The result of this config looks like this screenshot. Note that having the actual optionfields visible is completely optional, you don't need to have them in the view config.