Skip to main content

I’m reaching out regarding an automation rule we’ve set up in our IIQ instance that sends a notification to users when a device is assigned to them. The rule works as expected when we manually assign a device within IIQ, but it does not trigger when an integration (like Mosyle MDM) updates the asset owner.

We’d like to know:
    •    Is there a way to ensure that asset ownership changes made via integrations trigger automation rules?
    •    If not, is there a recommended workaround that would allow us to notify users when a device is assigned through external systems?

We’re trying to maintain consistency and ensure that users are notified regardless of how the assignment happens.

Thanks in advance for your support, we really appreciate any guidance you can offer!

What trigger are you using for the rule? Is it a checked out asset rule?

If so, that could be why the rule isn’t firing. The MDM assigning the owner would be an update.


@AGuzman There are two different rules you can create to notify the owner when a device is assigned to them - Checked Out or Updated Asset rules. If you want to encompass all asset owner updates regardless of it’s source, you will want to create an Asset Rule for when “Updated”. 

 

 

Here is the rule you can create that will cover all your bases of assigning devices. You can use various supported variable data points such as asset tag as I highlighted in the body of the email.

 

 

This is an example of the email that will be sent to the newly assigned user no matter what path was taken to assign the device to the user.

 

 


What trigger are you using for the rule? Is it a checked out asset rule?

If so, that could be why the rule isn’t firing. The MDM assigning the owner would be an update.

I am using the “Asset updated” rule to trigger the updated owner.


@AGuzman There are two different rules you can create to notify the owner when a device is assigned to them - Checked Out or Updated Asset rules. If you want to encompass all asset owner updates regardless of it’s source, you will want to create an Asset Rule for when “Updated”. 

 

 

Here is the rule you can create that will cover all your bases of assigning devices. You can use various supported variable data points such as asset tag as I highlighted in the body of the email.

 

 

This is an example of the email that will be sent to the newly assigned user no matter what path was taken to assign the device to the user.

 

 

TThanks for sharing. I did set up this rule, but I still don’t receive an email when I push out changes from Mosyle when the owner is updated, but if I manually make changes to the owner in IIQ, the rule fires off.

Here are images of my rule setup

 


@AGuzman Thanks for clarifying! Unfortunately I do not have an MDM integration on my demo site to recreate and test, however I am wondering if the Mosyle application filter for Username as a filter for when updated would trigger that change. 

Is your MDM assigning assets based off of the Username in the MDM?

 


@AGuzman Thanks for clarifying! Unfortunately I do not have an MDM integration on my demo site to recreate and test, however I am wondering if the Mosyle application filter for Username as a filter for when updated would trigger that change. 

Is your MDM assigning assets based off of the Username in the MDM?

 

I just tested the Username option and still did not work.

The MDM assigns assets based on the userid in the MDM. 

 


Reply