My organization has very specific requirements for data integrity, including the need to ensure that data is saved even when an app is cancelled. We’ve developed solutions to handle nearly every possibility–for example, our apps are configured to “rescue” data if a user closes the Player. One thing we haven’t been able to configure around is if an app uses the Tulip Player menu, which allows a user to switch apps–we’ve found that we can’t configure an app to recognize and save data when the Player menu switches apps, so that situation represents a risk to data.
Can we have a feature where the Tulip platform can be configured to disable the “Player Menu | Open Menu” trigger action? This would save us considerable work to centrally validate that apps are not using that action.
@thorsten.langner great suggestion, thanks for helping here. @mcconnell_luke have you tried using the “App cancelled trigger” yet? Some other approaches to solving your issue worth trying could be:
Because switching an app cancels the current running app, Add an App level trigger: App cancelled → Save data
Change the Player Menu trigger on the button from Open Menu → Pause.
Add a cancel App trigger instead when the user clicks on the Player Menu button.
Remove the Player menu trigger or button entirely.
Hope this helps. Let us know if you are still experiencing issues.
…Has the behavior of the Player menu changed since LTS 11? We have been using the “app cancelled” trigger condition to pause apps and I could swear that the actions in the Player menu bypassed anything that triggered on “app cancelled”.