Web Dispatch console Alert with status activity > = 307 queuded for device
Hi,
Is it possible in the Alerts (scheduling) to set alerts for activity status = 307 or 300 or 310 and to display them in the dispatch console. For example if you want to display an alert for activity with status 307 for 1H hour or more than 1 hour ?
In our tests, we can’t display alerts in the web dispatch console if the status is “affected” to a SA.
Thanks and Regards
anthony
Page 1 / 1
Hi Anthony,
You want to have alerts for:
SA Dispatched (300)
Queued for Device (307)
Received by Device (310)
Seems to me this is what you are looking for right?
I am not sure what you mean by: In our tests, we can’t display alerts in the web dispatch console if the status is “affected” to a SA.
HI @Phil Seifert
We saw your screenshot, but for example we set : Queued for Device and a number on the field below and we had no result displayed in the Dispatch Console.
It seems (?) that we can only display alerts before the assignation of an AM on a SV.
In our tests we can only display Alerts until the status “manual allocation”. To display = icon triangle
Regards
anthony
Hi Anthony,
This may be an issue that should be logged as a ticket. I can send the general question to R&D and see what they say but if it is an issue, it will have to go through support.
HI Anthony,
After discussion with R&D, there are two aspects of defining the alerts.
You need to provide the filter values to select the orders to apply the criteria. There must be at least one filter defined.
For example the priorities or the order from & to status. This will then only use the defined criteria against orders meeting this initial filter. Example below uses both priority and status ranges for the initial filter.
For each status you want to Alert, you need to create a line and define the individual status to trigger the alert.
For the alert in the above example, all the requested status trigger an alert with the color selected on each line.
This is how it is supposed to work. If you find that it still is not functioning, a ticket should be logged, a copy of the database provided and explain precisely why you feel it is wrong so it will be investigated. Perhaps you could also reproduce your issue on QAC to make it easier for them to investigate if it comes to this.