nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cannot get AQL Placeholders working

Samuel Stephens_k2dx2s

Hi all,

I have tried to death this guide on limited selection using AQL Placeholders for Create/Edit objects and it works in some cases but when I try to expand this to anything outside of a very basic CRM it breaks and does not want to cooperate.

https://confluence.atlassian.com/servicemanagementserver/advanced-placeholders-1044784599.html

This is infuriating as I have many use cases for such a simple function however it's proving extremely difficult to set up. I just want to limit selection on object creation.

For example:

Create Object > Select Org A
I should only see team selections for teams in Org A.

The video does not explain this very well at all and there is little to no documentation on this capability. If you have done this or made it work in an easy repeatable way please let me know

Accepted answers

PD Sheehan

I set up a sample schema with 3 object types: Org, Team and Object

Team contains an attribute called "Org For Team" that is a type "Object" and points to the Org object Type.

Object contains both an "Org For Object" attribute (same as above, type object and points to Org) and a "Team for Object" attribute (type object and point to Team).

The "Team for Object" has the following IQL in the configuration "Filter Objects"

"Org for Team"=${Org for Object}

The ${Org for Object} refers to the item selected while creating the new object. This is then compared to the "Team" attribute "Org for Team" and the filter renders just those teams.

2023-02-14 19_29_04-Window.png

Which you can see is a subset of the Teams:

2023-02-14 19_30_12-Window.png

All comments

PD Sheehan

I set up a sample schema with 3 object types: Org, Team and Object

Team contains an attribute called "Org For Team" that is a type "Object" and points to the Org object Type.

Object contains both an "Org For Object" attribute (same as above, type object and points to Org) and a "Team for Object" attribute (type object and point to Team).

The "Team for Object" has the following IQL in the configuration "Filter Objects"

"Org for Team"=${Org for Object}

The ${Org for Object} refers to the item selected while creating the new object. This is then compared to the "Team" attribute "Org for Team" and the filter renders just those teams.

2023-02-14 19_29_04-Window.png

Which you can see is a subset of the Teams:

2023-02-14 19_30_12-Window.png

Samuel Stephens_k2dx2s

Hi @PD Sheehan

This is the same model I've followed for my current CRM implementation as you've shown. I'm just trying to understand in a simple way how they relate.

Would you mind sharing the detailed attribute configuration for this example?

I'm keen to discover which attributes and values directly relate to which object type and how,

For example, does the 'additional value' (reference) play a part at all?
By 'points to' do you mean 'has Type Value'?

I think i'm 70% there and I believe this would be quite powerful in other applied theories so very keen to understand.

Also, does it require at least three object types? I haven't seen any way to do this between 2 object types as yet.

PD Sheehan

Sorry, I no longer have that example. The environment where I created it was refreshed.

By point to, I meant that the attribute configuration is set Type=Object and Type Value is the object type I said it points to.

In this example, the "Additional Value" (link type) doesn't matter. But later, when you have several such attributes with type=Object it might become necessary to limit results based on the link type.

I don't think there is any minimum or limit for how many object type this can work with. I only used 3 to try to match the described example.

The point is, any attribute of type=Object can have an IQL filter that will limit the list of objects retrieved based on the value of other attributes

Samuel Stephens_k2dx2s

Thanks @PD Sheehan

We actually managed to get this working yesterday based on your example.
We were able to do this across object schema also which is quite cool.

Unfortunately I just don't think this is that well officially documented.
The latest I was able to find was a really old YouTube video from Mindville.

Thanks for your help!

Sam

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

insight

object

iql

assets

mindville

assets-query-language

insight-object