For troubleshooting, it would be helpful to be able to view the current contents of variables and records directly in the player (similar to how it works in the browser test environment). If issues arise on the shop floor, this would make it easier to narrow down the root cause.
Hi @dmatzke,
Thank you for the feedback, I think this would be helpful for folks to have.
I’m curious about how you initially find out an issue has arisen on the shopfloor, and the process of getting flagged.
Sincerely,
Jake
Hi Jake,
Thank you very much for the quick reply!
We receive direct feedback from colleagues on the shop floor—for example, when an error message is displayed or when actions are not executed correctly. Smaller issues are reported via an app in Tulip and can then be processed there. However, if a process can no longer continue, we are contacted directly by phone and we try to resolve the issue on site.
This is where my suggestion comes into play: it would be helpful to be able to directly inspect the contents of variables and data records to check whether an incorrect value has been stored. This would make it easier to narrow down the root cause and resolve the issue more efficiently.
I hope this answers your question.
Kind regards,
Daniel
@jakerigos Can one see this in completions data? Or not until the session is completed? A live view of an in-progress completion would be a good way to check what the app is doing.
I think the Values you select could get logged somewhere in the Platform (similar to Node Red debug node).
However making them visible for the operator in the player is no option for me. This can also become a security issue.