AQL Object filers

[Steve Pace]

Hi,

I have a form which allows a user to request access to a business application ( like Scrive ) . I have created objects in Asset with application access roles linked to applications. The idea is that when a user chooses an application in the request form, only the access roles linked to that application appear in the drop-down. 

I have followed the instructions in another answer which suggest using the following 

Filter issue scope (AQL): Application = ${Application}

Yet this same filter does not work on the request in the portal. Is this by design or is there another way? 

Thank you 

Steve

[Riley Venable]

You can use the Filter Issue Scope (AQL) field to reference Assets object fields from within the issue. For example, if you wanted to create an Assets object field that only displays certain models of laptop based on the application you’ve selected in another custom field, you would create two separate Assets object fields. Create your first Assets object field and name it “Application”. Configure the field to show only “Application” objects retrieved from Assets by setting the Filter Scope (AQL) to objectType = “Application”. Now create the second Assets object field and name it “Access Role”. Configure the Filter Issue Scope (AQL) to show only the access roles from the application field in the issue by typing objectType = “Access Role” AND Application = ${customfield_xxxxx.label} where “xxxxx” is the custom field ID of the “Application” custom field. Now the “Access Role” field will show only the access roles that correspond to that application.