Everything works fine as long as the tulip-player is open, but if the tulip-player was closed and opens via the player link its not opening the app from the link and “stays” on the previous one.
So this is very dangerous, because in some cases the operator running the wrong work instruction.
This behavior was reproduced on a windows player.
Goal: Even if the player is closed and is started via the player link, the correct app should be opened.
Thanks for this feedback! @shep is the Product Manager responsible for this feature, but he is currently out of office. That being said, he has been working on the “clickable URL” request from the thread @thorsten.langner brought up here, but the issue @Jeremy points out is a slightly different one.
I will have him take a look at this once he is back and he will follow up here as well!
Sorry @beth, I didn’t want to mix things up. I only wanted to show that this issue (not opening the correct app if the player is closed) was also mentioned there, because @shep could have this on his radar already
Hey all! Thanks for bringing this issue to our attention. I agree, the expected behavior should be to navigate to the new app in the link regardless if the player is opened or closed. I’ve noted this bug in our system and we will see what we can do!
Have the team already analyzed the bug ticket and can you say whether it can be solved in the short term or will be a long runner?
As already described above, this bug is very dangerous, as it sometimes causes the wrong work instruction to be processed.
Hey @Jeremy, I can’t give a timeline just yet, but will follow up in the next week or so. This behavior has nothing to do with the link feature itself, rather it’s with the Tulip Player behavior. I will raise this to our teams and get back to you on what we can do about it.
