Skip to main content

We are having an issue relating around the automation from site options for asset automation. We are using 3 of the 4 options available, When User is assigned asset, update asset to match owner location and owner’s room. We are also using When User location changes, update asset to match owner location.

The combination of those 3 solves most of our issues when staff/students move around, but it does present us with a large issue that I am hoping to address and get fixed. We have a process where some students are given an obsolete Chromebook after X years of use/district enrollment. Those Chromebooks are processed for surplus and removed from our District inventory, but they remain in IIQ for tracking who we gave them to. In IIQ they are set to our Surplus location and then retired.

The problem we are getting is 8th graders who leave the district with their Chromebook, then return later to our high school and the site options trigger their retired Chromebook to come back into service and be assigned to our high school. It is creating inventory problems for our site tech, is there any option to ignore site options if an asset is at a certain location? There is nothing that I could see off hand, and nothing in the rules engine.

If there is nothing that exists, then this needs to be an idea that can give us a filter similar to the Google Devices App, where we can set a filter to include/exclude devices based on all the available filters.

Hello ​@TAnders! Thank you for sharing such detailed context :) Right now, the Site Options are an "all or none" thing, and there isn’t a way to ignore specific devices based on location or other criteria.

 

Perhaps someone else in the Community might chime in with creative workaround ideas, but as it stands, I believe addressing this would likely require a feature enhancement to add filtering or exclusion options within the Site Options.

 

Thanks!

 

Best,

Ashley


Hey ​@TAnders,

I took a look at the example asset that you provided and it looks the Google Devices OU writeback logic kicked in based on the student’s location and the filter that you have set up per location. Have you tried excluding the /students/surplus OU assets from your Google Devices OU writeback?

 

Since your Google Devices shouldn’t automatically migrate to the owner’s location based on your configuration settings (Google Devices > Location Mappings), the Google OU writeback looks like the main factor in this occurrence.

 

Hopefully, this information helps!


Hey ​@TAnders,

I took a look at the example asset that you provided and it looks the Google Devices OU writeback logic kicked in based on the student’s location and the filter that you have set up per location. Have you tried excluding the /students/surplus OU assets from your Google Devices OU writeback?

 

Since your Google Devices shouldn’t automatically migrate to the owner’s location based on your configuration settings (Google Devices > Location Mappings), the Google OU writeback looks like the main factor in this occurrence.

 

Hopefully, this information helps!

We need the writeback to write to the surplus OU so that when we send them to surplus inside IIQ, it moves them all in bulk to the surplus OU in Google.


Reply