Riada Insight: Referenced CF result based on combination of two Insight fields

[Tomáš Vrabec]

Hi,

solving an issue for one of my customers.

We got a structure defined in Insight object.

LEVEL1 - Department

LEVEL2 - Category

LEVEL3 - Request Type

With Jira Service Desk, we are pre-filling value of Request Type

Current solution:

1) User is able to pick valid referenced Category based on valid reference to Request Type

2) User is able to pick valid Department based on valid reference to Category.

Target solution:

1) User is able to pick valid Department based on valid reference to Request type. (This is what I can achieve)

2) User can select only LEVEL2 Categories, which are valid for both of selected LEVEL3 Request Type AND LEVEL1 Department.

Is there a way how to achieve that with Insight or do I have to stay with current solution?

[Patrick Cartier]

HI @Tomáš Vrabec ,

Hope all is well!

If I am understanding this correctly, the user will make a choice based on two previous choices?

Their choice of request type is automatically populated, then they are choosing the level1 department.

Thus, level2 categories should be a cascading referenced field based on level1 and level 3 which are selected first (automatically or by the user).

If this is the case, maybe this documentation will help:

https://documentation.riada.io/display/ICV54/Referenced+Insight+Custom+Field

You might have to swap level2 and level3 in Insight (not 100% on this).

I think we had a similar scenario a few months ago.  If I'm off track please post here or PM me on slack, I'd like to understand more.

Patrick

[Tomáš Vrabec]

Hi @Patrick 22 ,

will keep posting in here, maybe someone will appreciate that.

Well I am of course familiar with Referenced CFs, but problem is that it doesn't respect "combinatoric" logic. 

I got kind of random matrix of L3 inR L2 and L2 inR L1

Flow is like that:

1. At JSD, user pick the type of the agreement (legal project). This is hidden by JSD portal settings and filled with appropriate value of L3.
2. Next, I would like to offer all departments (L1), which are applicable for selected L3 (easy)
3. And then, I need to offer selection of Categories (L2) which are applicable for combination of both of prefiled L3 and selected L1. (don't know how)

• If I am referencing L2 to L3 insight CF, I am getting always a list of all dependencies without cutting of not-valid combinations of selected L1.
• If I am referencing L2 to L1, I got list of all categories for that L1 without cutting combination not valid for preselected L3.

Is there any hack how to respect combination of L3 insight field and L1 referenced insight field in another L2 referenced insight field?

If I swap L2 and L1, it works fine, because first step will eliminate all non-valid options as well as second step. But I am forcing users to first select the category and then department ... just UX stuff, but pretty annoying :-/