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; } } }

Assests Filter assign scope

Martin Svensson_q82m9z

I'm trying to pre populate a customfeild with an employee that has the approver role.

I need to be able to add or remove users from the approver customfeild directly in the customer portal.

The choices will then be affectuated with the postfunction to add or remove the users from the system approver asset object.

But when i run this the approver will not populate the portal field, i have tried several diffrent takes on the aql.

Any ideas?

Skärmklippc.PNG

Accepted answers

PD Sheehan

Assuming that customfield_11300 is another insight objects custom field, you then want to compare that against the Key attribute

object HAVING inR(objectType=Systems and Key=${customerield_11300}, reftype in ("Approver"))

If that doesn't work, try the following:

object HAVING inR(objectType=Systems and Key in(${customerield_11300${0}}), reftype in ("Approver"))

All comments

PD Sheehan

Assuming that customfield_11300 is another insight objects custom field, you then want to compare that against the Key attribute

object HAVING inR(objectType=Systems and Key=${customerield_11300}, reftype in ("Approver"))

If that doesn't work, try the following:

object HAVING inR(objectType=Systems and Key in(${customerield_11300${0}}), reftype in ("Approver"))

Martin Svensson_q82m9z

Hi Peter Thanx for the quick followup.

I couldnt get the Key variable to work it didnt return any value, what does key value do compared to Name or label?

Skärmklippcdcd.PNG

I tried this one but with no luck, still nothing pre populated. only if i add the choosen value as default will it show up on the customfeild in the portal.

Martin Svensson_q82m9z

Yes, CF11300 is configured to show the systems available and cf11301 can present the choosen approvers

PD Sheehan

Key refers to the Key attribute (created by default for all object types along with Name, Created, and Updated).

Issues only store the key of your object as a reference to the object.

IQL placeholder, the value of an insight custom field returned by ${customfield_xxxx} will be the key of the selected object. So if you want to find objects linked directly to the selected object, you need to match use the key of the selected object.

You should be able to use the IQL Search page to confirm this works:

Combine the filter scope IQL and filter assign scope IQL as:

objecttype=Userad and object having inR(Key=<enter a key for a selected system>, reftype in ("Approver"))

If you are getting the expected approver, then the auto-assign should work.

Be sure you delete the default/automatic value both in the custom field config and in the request type.
You'll also want to hide that field from the portal. The insight assign function is run via listeners, it doesn't show live on screen.

Martin Svensson_q82m9z

Hi Peter

I figured that i was beggin for a miracle.

But i still wonder why the automatic choice in the cf is for backend use only?

Why would you use that? You can easy do the same with postf.

I can see a whole lot of usecases were a live cf update would be lifesaver.

Do you have any ideas how i can get the same results within the potal?

Welcome!

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

Quick Links

Find more posts tagged with

server

insight

jira-service-management

jira-service-management-server