Jetstream API
Jetstream Workflow Guides

Configuring a Handheld: Aliases

8min
aliases are a jetstream feature used by the rfid handheld reader to add additional information to inventory scans via the included inventory app an alias is essentially a tag, or descriptor, that can be made available to any number of rfid handheld devices (many to many), so that the user of the device may select one from the list of assigned aliases to submit along with an rfid inventory scan aliases can be selected by the device user to add context to an inventory scan, such as a specific account, location, or even a status related to the scan for example, you may have several rooms in a certain facility each with rfid tagged inventory without aliases, you would need to have a separate device for each room in order to keep the inventory scans distinct for each room with aliases, if you create an alias for each room, then assign these aliases to each rfid handheld device at the facility, users of the handheld devices can select the alias matching the room they are scanning, so when the scan is submitted, your integration will know not just which device scanned the inventory, but where the device was scanning so once you configure the aliases and devices in jetstream, how will the handheld user actually specify what location they are physically at? when a handheld device user wishes to take an inventory scan, they will power on their reader and phone, connect to wi fi, bluetooth connect the reader and phone, and open the terso inventory app select "inventory" from the main menu select an available alias from a searchable, scrollable list take their inventory scan as usual submit the inventory scan with the rfid tag epcs scanned, the scanning device name, and the selected alias name now that you know the end result, let's see the steps required to create an alias that can be used by a device create aliases create devices (can also be done before aliases) verify that the handhelds can utilize the aliases you tied to them modify devices or aliases as needed creating aliases use the create an alias docid\ cstsab cv6ogqwmtuaql endpoint, specifying the alias name, region, and optionally the list of devices you want to be allowed to select that alias (if your handhelds are already added to jetstream) creating devices use the create a device docid\ p7nz8balv5 rd8s82wh5d endpoint, specifying the device name, serial number, device definition, region, and optionally the list of aliases you want the device to be able to select from (if your aliases are already added to jetstream) reviewing aliases in jetstream you have created aliases and devices and created relationships between them you can review the current state of aliases in jetstream and on the physical device using different endpoints there is currently no method for viewing all aliases relationships with all devices, as this result would be excessively large (some applications have tens of thousands of aliases related to thousands of handhelds) review a specific device's current aliases in jetstream using the get a device docid\ zpamtaaf4vcd4eamucpfc endpoint review a specific aliases' current devices in jetstream using the get an alias docid\ mm2q6kdqrkq87e9hd8z4 endpoint changing device alias relationships if you wish to change which devices can display which aliases, you have multiple options, depending on your goal modify a device's aliases this option is best when you want to change the alias list for a specific device overwrite the device's existing alias relationships in jetstream using the modify a device docid\ ucpbzffrcws0h zjf4ovp endpoint to replace the current alias list with a new alias list modify an aliases' devices this option is best when you want to change the device list for a specific alias overwrite the device's existing device relationships in jetstream using the modify an alias docid\ nl75i4z2qkopklpmdra2e endpoint to replace the current device list with a new device list deleting aliases or devices deleting an alias or device record will immediately remove all relationships between that record and other records if you re create the alias or device in the future, the relationships between that alias or device will need to be re created