Versions Compared

Old Version 2

changes.mady.by.user Pio

Saved on

compared with

New Version Current

changes.mady.by.user Pio

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

You can create multiple data source definitions under the Data Sources tab.

Screenshot 2024-11-15 at 15.37.47.png

1- Click the Add Data Source button to add a new one.

Screenshot 2024-11-15 at 15.40.02.png

Give 2- Your data source definition should be given a unique name to your data source definition. .

3- Write your AQL query to filter the objects from your JSM Assets.

Info

Pro Tips:

  • If you don’t specify the Object Schema name (objectSchema) or the Object Schema ID (objectSchemaId), the query will run across the schemas. This is sometimes useful. On the other hand, if you have a very large number of objects, we recommend using the scheme schema name or ID in your query.

  • Filter as much as possible and enjoy the advanced features of AQL by using the objectType or objectTypeId keywords.

  • Two functions are currentUser() AQL function is helpful in case you want to filter according to the portal user.

Here are some example AQLs:

AQL

Description

"Jira User" = currentUser()

...

Here are some example AQLs:

Description

AQL

This AQL filters all the objects across all schemas which have an attribute called “Jira User” with a “User” type. In case the attribute value is set as the Jira User of the person who is viewing the Portal Profile page, the objects will be displayed.

4- Click the Save and check AQL button. You will get the statistics about the AQL result for number of objects and object types.

Screenshot 2024-11-19 at 13.40.25.pngImage Added
Info

In case there are no objects found the query may be incorrect. You need to review and update your query. If you are sure that the AQL is correct, that means the AQL doesn’t have a result for your user. You can create some objects as a test. You can move to the next step only if you have one or more objects in this test result.

5- There can be multiple object types in the query result. Commonly, every object type may have different attribute names. In that case, you can configure the list of attributes to be displayed for each object type. The screenshot below is an example where the results of the AQL are from 3 object types.

  • Managed Devices object type from Microsoft Intune object schema

  • Mobile Devices object type from Jamf object schema

  • Users object type from Micsoroft Entra ID object schema

You can select 4 attributes that will be displayed in the summary view. And more attributes to be displayed in the detailed view.

Screenshot 2024-11-19 at 13.40.57.pngImage Added

6—After selecting the attributes, you can decide whether to display the object's avatar. Enable/disable the “Show Avatars?” option as you like.

Screenshot 2024-11-19 at 13.41.24.pngImage Added

7- As the last item on this configuration page, you can select the JSM Servicedesks which this configuration will be available. This way, you can decide which AQLs are valid for which Servicedesk customers and organizations.

8- Click the Save button to save your configuration.

9- The Data Source record will be added to the table. By default, it will be in a disabled state. Click the toggle to enable it.

Screenshot 2024-11-19 at 13.41.48.pngImage Added

10- Add more data sources with different AQL queries.

11- Now, you can add Header and Footer via the Admin tab.

12- Test your results by viewing your Portal Profile page on the service desk portal.