I want to know which rules trigger the beeps on the GO device.
You need to be logged in to reply to this post and participate in the Geotab Community discussions.
Hey @****-6175,
This is possible, but it's a little complicated. What you need to look at is the DistributionList object that associated with the Rule (so if you want that report, you should pull all rules and all associated DistributionLists). The DistributionList will have a recipients property that's an array of notifications. For this, 'recipientType' will be something like "BeepThreeTimes" or others like that (I don't have the full list, but you could set them all up and see what they come back as from the API). You could then just filter all rules that have a DistributionLIst that has one of the driver feedback recipientTypes and you'd have your report.
Let me know if that's what you're looking for or if you have any other questions!
Thanks,
Tucker
Hello @****-6175 ,
Thank you for asking your question in our community. I dont know of a way to do this in MyGeotab besides looking through al of the rules. You may be able to get this info from the API. Maybe @TuckerBA-1087 or @DarenPorter-1148 know of a way to do this they can share.
Let us know if you have any other questions. We are here to help.
Have a good one!
Eishi FUN
Hey @****-6175,
This is possible, but it's a little complicated. What you need to look at is the DistributionList object that associated with the Rule (so if you want that report, you should pull all rules and all associated DistributionLists). The DistributionList will have a recipients property that's an array of notifications. For this, 'recipientType' will be something like "BeepThreeTimes" or others like that (I don't have the full list, but you could set them all up and see what they come back as from the API). You could then just filter all rules that have a DistributionLIst that has one of the driver feedback recipientTypes and you'd have your report.
Let me know if that's what you're looking for or if you have any other questions!
Thanks,
Tucker