Skip to main content

Basically the problem we have in our district is that devices going missing happens often, but it can be a short-lived occurrence. Our librarians are very good at setting the asset status to “Missing”, which triggers a device lock, but they tend not to create tickets because the devices are often found within hours or even minutes of being locked therefore they don’t want to deal with ticket hassle.

The problem this presents to us is we don’t have a good recorded history of how often any given student loses a device, which can be detrimental when discipline/remediation is required. I feel automating lost device ticket creation would be a win-win, librarians don’t have to do the extra work, but we’d still have a trail of who is losing what to support admins when needed. 

IIQ’s asset rules currently don’t allow for ticket creation based on device status for some reason. So I’m just wondering if anyone has found a workaround to this shortcoming, or what’s your approach. Thank you!

 

 

 

 

@Daniel P Thank you for submitting your question. 

You can create a rule: Asset / When Updated. You can have it update when the status is Missing or the status is changed to missing. Next you add who you want to email - whoever that may be. 

This would give you a paper trail! I know it is not perfect, however this would be my work around. 

 

@jax @TAnders @Cozmo03 @William Gibson @Jim.Sch @BrandonGHAPS 

Do y’all have any suggested work arounds for this?


@Kathryn Carter , thanks for the tip. That’s the way I’ve been doing it so far, the downside though is it keeps the records concealed under someone’s inbox, as opposed to be always accessible  for anyone needing to see (under the student’s profile). In a ticket, you can also add notes and subtasks to the case to build context, etc. 


Reply