Hi,
I've had a vary vague incident ticket for a children auto populate list not showing up correctly, with the comment that one child vdx was over another one, so then they triggered a button on it to run a user interactive automation script, the wrong one was run.
If there an information that can be gathered from the client after the fact, to try and identify what was going on?
Hi Michiel,
We have the information events that show what was actioned.
The information I have fed back from ops so far is “DataMiner was freaking out and was overlaying another source, so when they routed another channel (ran the automation script from the visual overview) it changed the wrong route.”
I’ll be on site next week to try and get more coherent information from the operators.
Hi Philip,
You can rely on the information events to understand more about what actions/sets were triggered at the moment of the event.
Based on your input I would assume that you have a vdx page in your visual overview that will load another visual overview based on a property, session variable, ... I would investigate how that vdx page can/should change to understand what went wrong. If your tooling is inside of the vdx page and the property or session variable was for one or other reason not updated correctly, then you could end up using the wrong tools. I'm not quite sure what exactly you have in your use case, but maybe it could already be more clear for the operators if you provide them with extra information or confirmation boxes?
Hi Michiel,
The main view containing services has the children vdx, with a summary vdx from each service displayed in the child shape. This in turn opens a popup when pressed for the controls, which is probably where the issue lies, as they more than likely didn’t close the popup from another service.
The user interactive automation script that pops up with confirmation information in states what the script is about to do, including the service that they just triggered it from.
I’m probably going to have to remove the popup part and combine the summary and control tabs of the service vdx, though it was done this was in the first place to show the services in the same layout as the operator has on their multiviewer.
Hi Michiel,
I’ve got to the bottom of this, it wasn’t a vdx page popup that was the issue, it was an automation script they’d started, then started a new one, and got confused on which was which, casing the wrong thing being set.
Hi Philip,
Could you clarify maybe your question a bit more?
If you want to know what (interactive) script was triggered at the push of the button, you could look into your information events around the time it was pushed.