We are trying to troubleshoot an issue, and I think I have come to the root cause -
We have an app that keeps track of the number of shots the machine does while the operator is filling out a form (just a normal step, not a form step) so when we go back to the main app, the number of completed parts can be updated.
What we are seeing
Very often we are getting reports of the count being off after the form is completed.
What I think is going on
Tulip locks down triggers running while an input field is selected. Including the trigger that updates the variable tracking shots outside of the main app.
a maybe important note - we use the onscreen keyboard, not a physical one to enter these input fields
Why I think you do this
App logic that triggers transitions could be very confusing if it executed while the user was still inputting values. I dont know a good solution to support both of these usecases.
I don’t have any sort of bandaid for this issue. Any ideas?