Possible Bug - Published Apps can Navigate to Development Apps

Product Suggestions
1

Hi Tulip Team,

In our production environment, we allow only the use of published apps on the manufacturing line as connectors for published apps point to our production ERP environment and development version apps point to our UAT/Development ERP environments. This is intended and a useful Tulip feature we utilize for testing. However, to ensure our production line only uses the production environments, we assign station with the “Most Recently Published Apps” designation for our production apps.

However, today there was a scenario in which a published app, running on a station assigned to use only the “Most Recently Published Version” of that app was able to navigate to another app which had not yet been published, and thus defaulted to Development Version for that app. This caused the Development connector environment to be used, allowing the operator to use the Tulip app but with the absence of signals to our proper ERP environment.

Though it was a mistake on our part to add a trigger to allow navigation to an unpublished app, we would have expected an error to prevent a station tagged with only “Most Recently Published Version” to navigate to a development version app.

2

Hi @iamwout -

Thanks for bringing this up! This is actually the expected behavior at the moment. You can read more in this post: Upcoming Changes to Unassigned Player Device Behavior

I am going to send this request to our Support Team on your behalf. They can enable a feature that will get you the behavior that you desire. This feature will:

  • Prevent display devices from switching and running any arbitrary apps that do not conform to the station or station group app assignment through the app transition triggers.
  • The app is simply completed or cancelled but prevented from further navigating to the target app.
3

Hi Beth,
I ran into a similar problem today I found some stations that work on older versions.
When I assign an app to a station, I always put the “most recently released version”, never assign to a specific one.
This morning I got a message from the BI supervisor about incorrect data in a central table, I looked for the source of the data mismatch, and finally found that this station works 4 versions back.
So, I don’t know when your bug started but it was at least from mid August.
Thank you,
Amit