Skip to end of banner
Go to start of banner

Search functions

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

This feature is introduced at AIP v7.0.1.


We are happy to introduce search functions. First functions are to filter assets by referenced assets. More functions will be added later.

referenceAsset

referenceAsset function lets you to filter assets by referenced assets value. For example there is Computer asset which has Mouse reference asset. You can filter all Computers having Mouse that assigned to a user such as current, reporter, assignee or a specific user.

You can use this function at Basic Search of Asset Navigator for "Asset List" or "Asset List by Asset Type" type of attributes.

SyntaxreferenceAsset("FIELD NAME 1", "VALUE 1", "FIELD NAME 2", "VALUE 2", ..)
Supported fields"Asset List", "Asset List by Asset Type"
DescriptionField name and value pairs are expected. Number of parameters should be an even number.


Examples:

Field name to queryDescriptionExamples

Text Based System Fields:

  • Asset Tag = asset.assetTag
  • owner = asset.owner
  • Serial Number = asset.serialNumber
  • Invoice Number = asset.invoiceNumber


Text Based Attributes (User defined fields)

  • Text
  • Text Area
  • IP
  • IPv6
  • URL

Use exact field name for attributes. Field names are case sensitive


Query with 3 different type of field values at a time. First Name is a Text field, Jira User is a Jira Single User Select field and Cities is a checkbox field.

:

referenceAsset("First Name", "marla", "Jira User", "tyler", "Citites","Ada")

User based System Fields:

  • assigne = asset.assignee
  • owner = asset.owner
  • managed by = asset.managedBy
  • reserved for = asset.ReservedFor


User based Attributes (User defined fields)

  • Jira Single User Select
  • Jira Multiple Users Select

Use exact field name for attributes. Field names are case sensitive


Query with user name or user key.


Variables:

Following variables are available:

  • $currentUser: Current logged-in user
  • $reporter: Issue's reporter or current logged-in user when reporter not found. $reporter is the value of issue reporter field at issue edit/create screens (not linked asset-issues reporter.)
  • $assignee: Issue's assignee. Empty evaluated if not found. $assignee is the value of issue assignee field at issue edit/create screens (not linked asset-issues assignee.)
  • $assigneeOrCurrent: Issue's assignee or current logged-in user when assignee not found.  $assignee is the value of issue assignee field at issue edit/create screens (not linked asset-issues assignee.)

Query with user key:

  referenceAsset("asset.assignee", "JIRAUSER18101")

Query with user name:

  referenceAsset("asset.owner", "tyler")

Query "Jira Users" field contains "marla" and city is Ada.

  referenceAsset("Jira Users", "marla", "City", "Ada")


List based System Fields:

  • Belongs To Group = asset.belongsToGroup
  • Location = asset.location
  • Cost Currency = asset.costCurrency
  • Status = asset.status
  • Substatus = asset.substatus

List based Attributes (User defined fields): Use exact field name. Field names are case sensitive

  • Dropdown List
  • List Box
  • List Box - Multiple
  • Radio Button
  • Checkbox
Put 3 @ chars between keywords like "Ada@@@Sel"

Query Cities having Lima or İstanbul:

  referenceAsset("Cities", "Lima@@@İstanbul")















referenceAssetByType // COMING SOON

referenceAssetByType works just like referenceAsset with one more additional parameter which lets you to filter assets by asset type.

referenceAssetByType("ASSET TYPE NAME", "FIELD NAME", "VALUE")

Function signaturereferenceAssetByType("ASSET TYPE NAME 1", "FIELD NAME 1", "VALUE 1", "ASSET TYPE NAME 2", "FIELD NAME 2", "VALUE 2", ...)
DescriptionAsset type, field name and value parameters are expected. Number of parameters should 3 or multiples 3.
  • No labels