Target Filter View 
¶
HOWTO video on Target Filter View
Figure 1
Note
The filters created in the Target Filter View can be applied in the Deployment and Rollout views as seen in Figure 2 and Figure 3 below:
Filters¶
Deployment View¶
Figure 2 - Deployment View - Custom Filter
Rollout View¶
Figure 3 - Rollout View -- Custom Target Filter
Add (Plus icon)¶
To create a custom filter in the Target Filter View, click the Plus icon on the top right of the screen.
Search¶
Clicking the Search icon will enable the user to query by any string inside the container.
Create Filter¶
Figure 4
You will need to define the Filter Name and also a query. In the example above we have:
Filter Name: Devices in New York
Query: tag=="office_columbus_ave"
In this case, a query for the tag "office_columbus_ave" will be applied. This means that any Target Device which has the tag "office_columbus_ave" associated to it will be a result.
Other Query Examples¶
| Query | Description |
|---|---|
updatestatus==error |
Displays all target devices in ‘error’ state |
controllerid!=192.160.10.24 |
Displays all targets that don’t have the controllerid 192.168.10.24 |
name==*nitro* |
Displays all targets which contain the term ‘nitro’ in their name. |
name==*nitro* or description==*nitro* |
Displays all targets that either have the term ‘nitro’ in their name or description. |
name==*warp* and description==*warp* |
Displays all targets that have the term ‘warp’ in their name and their description |
name==warp* and updatestatus==pending |
Displays all targets with their name starting with ‘warp’ which are in ‘pending’ state. |
(assignedds.name=='Web Content' and description==Plug) or updatestatus!=error |
Displays all targets which are either assigned to the ‘Web Content’ distribution and have description equals to ‘Plug’ or which are not in error status. |
(updatestatus!=In_sync or updatestatus!=error) and name==*warp* |
Displays all targets that don’t have the updatestatus In_sync or error and which also contain the term ‘warp’ in their name. |
(updatestatus!=error or updatestatus!=pending) and (name==*warp* or description==*warp*) |
Gives all targets that either have the term ‘warp’ in their name or their description and also either have the update status not in state error or pending. |
createdat=ge=1540523864398 |
Displays all targets which were created (in other words, first poll) on or after Wednesday, August 22, 2018, 00:38:08. The value is expressed as UTC in milliseconds. |
lastcontrollerrequestat=lt=${OVERDUE_TS} |
Displays all targets which are overdue (last poll occurred more than "Polling Overdue Time" ago) |
Android Client Query Examples¶
The UF Android Client Service provides by default several attributes regarding the client itself and the Android OS it runs on. In the Deployment View select a target and open the "Attributes" tab to see the all attributes provided by a device. Additional custom attributes can be specified using Third-party Integration APIs. Here's some example queries using the default attributes:
| Query | Description |
|---|---|
attribute.client=="Android" and attribute.client_version_code=ge=29 |
Displays all target devices running Android Client with version code 29 or greater (release v1.1.2 and later). Usage of client_version_code is recommended in place of client_version.Version codes can be obtained by looking up the version code in the UF Android Client Service releases page or by selecting a specific tag in the UF Android Client Service git repository and looking for the versionCode in uf-client-service/build.gradle |
attribute.android_version==12 and attribute.system_update_type==AB |
Displays all targets devices running on Android 12 and using AB double copy OTA updates |
attribute.android_build_type=="user" and attribute.android_keys=="release-keys" |
Displays all targets with Android build type "user" and signed with the release keys |
Supported Operators¶
- Equal:
== - Not Equal:
!= - Greater than or equal:
=ge= - Less than or equal:
=le= - Greater than:
=gt= - Less than:
=lt= - 'In' parameter:
=IN=(Example:name=IN=(target1,target2)) - Wildcard:
*
Auto Assignment¶
HOWTO video on Auto-assignment
The Auto Assignment is a feature that allows to apply a distribution to devices that match a target filter. The difference with rollouts is that Auto Assignment applies also to devices that are yet to poll for the first time (in other words, that are not yet among the registered Targets).
Figure 5
For example the createdat=ge= query from the Other Query Examples table can be used to trigger the application of a distribution to devices that poll for the first time on or after the defined UTC time.
Once you've defined a custom filter, navigate to the Auto assignment column under Target Filter View and click on the none link in your custom filter row (see Figure 5).
Figure 6
On the next popup window that appears, you will enable the auto assignment feature, select a distribution to apply in the list, and then choose save.